Error on Report based on Analysis Services

I've got most of my first stab at using Reporting Services. I am using the
Report Viewer control in VS 2005. When I point it at a report based on
standard TSQL it runs. My next query is based on Analysis Services. It runs
via the URL when I login as an Administrator but I get the following error
when I do it via the Report Viewer. The problem is the web server can't
"see" itself (i.e. typing the URL of the ASP.net page doesn't seem to work)-
something which I will get the network people to look at tomorrow so I can't
see a more detailed error. I am just starting trying to get an understanding
of roles etc but some pointers would be great. Regards, Chris.
a..
An error has occurred during report processing. a.. Query execution failed
for data set 'Analysis_Services_Project1'. a.. For more information about
this error navigate to the report server on the local server machine, or
enable remote errors a..I figured it out - I needed to add the IUSR as a role to the Analysis
Services DB.
"Fresno Bob" <nospam@.nospam.com> wrote in message
news:%23QvrOp98HHA.3940@.TK2MSFTNGP05.phx.gbl...
> I've got most of my first stab at using Reporting Services. I am using the
> Report Viewer control in VS 2005. When I point it at a report based on
> standard TSQL it runs. My next query is based on Analysis Services. It
> runs via the URL when I login as an Administrator but I get the following
> error when I do it via the Report Viewer. The problem is the web server
> can't "see" itself (i.e. typing the URL of the ASP.net page doesn't seem
> to work)- something which I will get the network people to look at
> tomorrow so I can't see a more detailed error. I am just starting trying
> to get an understanding of roles etc but some pointers would be great.
> Regards, Chris.
> a..
> An error has occurred during report processing. a.. Query execution failed
> for data set 'Analysis_Services_Project1'. a.. For more information about
> this error navigate to the report server on the local server machine, or
> enable remote errors a..
>

Error on Associative Rules Viewer

Hello,

I don't know if this is the correct forum or if it would perhaps be the server setup & upgrade, however, I'll ask here first. I am going through the SQL 2005 data mining tutorials and have encountered an error that states:

Query (1,6) The '[System].[Microsoft].[AnalysisServices].[System].[DataMining].[AssociationRules].[GetStatistics]' function does not exist.

After looking around for a bit it appeared that this function is generally used in a stored procedure run from the server. Is this correct? What do I need to do to either correctly import the function into the project or to make sure that it is installed on the server?

We are running the Ent Ed. now, however, we just upgraded to this after I had already started on this project. Could that be a problem?

Any help on this would be greatly appreciated.

Thanks for your time.
Eric Wisdahl

Did you try another other viwer? If this happens to every viewer, you may find this post is helpful:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=928000&SiteID=1

Good luck,

|||

From your previous post in the other topic:

These are Analysis Services stored procedures that are suppposed to be installed with your server. Would you please start Management Studio and coonect to the Analysis Services instance you are using? After you connected, click the Assemblies in the object Explorer, you should be able to find System listed there. Right click system, and select properties. You will have a list of properties of this the system assembly.

At first, please verify your assemly exisits. The location of the assembly is list under general->Source. And it looks something like this:

C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\msmdspdm.dll

Please verify this file is not deleted by accident

Second, please check Security Settings. Usually, it should work fine for the following settings:

Impersonation Info ImpersonateServiceAccount

Permission Set Unrestricted.

Good luck,

I noticed that I do not, in fact, have the msmdspdm.dll in the appropriate spot. It states that the source should be in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdspdm.dll. I did find a file with this name in the MSSQL.4\OLAP\bin folder and put it into the MSSQL.2 folder. I then had to restart the service and it appears that this has fixed the problem.

Thank you very much for your time...

Eric Wisdahl

error message in event viewer but not in SQL server log

I have got a strange porblem. In the application log of the event viewer the
following error message apear:
SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
Unable to determine if the owner (sa) of job job name has server access
(reason: Unable to connect to server - check SQL Server and SQL Server Agent
errorlogs).
This error message does not apear in the SQL server log or the SQL server
agent log. In the SQL server I get the message that the job run succesfull.
This is correct because the job runs succesful. The error message in the
event viewer seems to be not correct.
The happens on a SQL server 2000 cluster environment with Windows Server 2003.
Hopefully someone can help me with this problemHi
"cas" wrote:
> I have got a strange porblem. In the application log of the event viewer the
> following error message apear:
> SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
> Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
> Unable to determine if the owner (sa) of job job name has server access
> (reason: Unable to connect to server - check SQL Server and SQL Server Agent
> errorlogs).
> This error message does not apear in the SQL server log or the SQL server
> agent log. In the SQL server I get the message that the job run succesfull.
> This is correct because the job runs succesful. The error message in the
> event viewer seems to be not correct.
> The happens on a SQL server 2000 cluster environment with Windows Server 2003.
> Hopefully someone can help me with this problem
This sounds like you have something similar to
http://support.microsoft.com/default.aspx/kb/286253 although not the same
message it could be a conflict occurring when two jobs are run at the same
time. Have you checked the schedules for your jobs?
John|||John,
This is the only job that is scheduled at 08:00 in the morning. This is not
the same as in http://support.microsoft.com/default.aspx/kb/286253
The error message only apear in the event viewer and not in SQL logs. In SQL
server the job is succeeded, and this is correct. I can see that the results
of the job are OK.
"John Bell" wrote:
> Hi
> "cas" wrote:
> > I have got a strange porblem. In the application log of the event viewer the
> > following error message apear:
> > SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
> > Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
> > Unable to determine if the owner (sa) of job job name has server access
> > (reason: Unable to connect to server - check SQL Server and SQL Server Agent
> > errorlogs).
> >
> > This error message does not apear in the SQL server log or the SQL server
> > agent log. In the SQL server I get the message that the job run succesfull.
> > This is correct because the job runs succesful. The error message in the
> > event viewer seems to be not correct.
> > The happens on a SQL server 2000 cluster environment with Windows Server 2003.
> > Hopefully someone can help me with this problem
> This sounds like you have something similar to
> http://support.microsoft.com/default.aspx/kb/286253 although not the same
> message it could be a conflict occurring when two jobs are run at the same
> time. Have you checked the schedules for your jobs?
> John|||"cas" wrote:
> John,
> This is the only job that is scheduled at 08:00 in the morning. This is not
> the same as in http://support.microsoft.com/default.aspx/kb/286253
> The error message only apear in the event viewer and not in SQL logs. In SQL
> server the job is succeeded, and this is correct. I can see that the results
> of the job are OK.
>
So you haven't tried changing the schedule to see if it still occurs?
John

error message in event viewer but not in SQL server log

I have got a strange porblem. In the application log of the event viewer the
following error message apear:
SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
Unable to determine if the owner (sa) of job job name has server access
(reason: Unable to connect to server - check SQL Server and SQL Server Agent
errorlogs).
This error message does not apear in the SQL server log or the SQL server
agent log. In the SQL server I get the message that the job run succesfull.
This is correct because the job runs succesful. The error message in the
event viewer seems to be not correct.
The happens on a SQL server 2000 cluster environment with Windows Server 2003.
Hopefully someone can help me with this problem
Hi
"cas" wrote:

> I have got a strange porblem. In the application log of the event viewer the
> following error message apear:
> SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
> Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
> Unable to determine if the owner (sa) of job job name has server access
> (reason: Unable to connect to server - check SQL Server and SQL Server Agent
> errorlogs).
> This error message does not apear in the SQL server log or the SQL server
> agent log. In the SQL server I get the message that the job run succesfull.
> This is correct because the job runs succesful. The error message in the
> event viewer seems to be not correct.
> The happens on a SQL server 2000 cluster environment with Windows Server 2003.
> Hopefully someone can help me with this problem
This sounds like you have something similar to
http://support.microsoft.com/default.aspx/kb/286253 although not the same
message it could be a conflict occurring when two jobs are run at the same
time. Have you checked the schedules for your jobs?
John
|||John,
This is the only job that is scheduled at 08:00 in the morning. This is not
the same as in http://support.microsoft.com/default.aspx/kb/286253
The error message only apear in the event viewer and not in SQL logs. In SQL
server the job is succeeded, and this is correct. I can see that the results
of the job are OK.
"John Bell" wrote:

> Hi
> "cas" wrote:
>
> This sounds like you have something similar to
> http://support.microsoft.com/default.aspx/kb/286253 although not the same
> message it could be a conflict occurring when two jobs are run at the same
> time. Have you checked the schedules for your jobs?
> John
|||"cas" wrote:

> John,
> This is the only job that is scheduled at 08:00 in the morning. This is not
> the same as in http://support.microsoft.com/default.aspx/kb/286253
> The error message only apear in the event viewer and not in SQL logs. In SQL
> server the job is succeeded, and this is correct. I can see that the results
> of the job are OK.
>
So you haven't tried changing the schedule to see if it still occurs?
John

error message in event viewer but not in SQL server log

I have got a strange porblem. In the application log of the event viewer the
following error message apear:
SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed.
Unable to determine if the owner (sa) of job job name has server access
(reason: Unable to connect to server - check SQL Server and SQL Server Agent
errorlogs).
This error message does not apear in the SQL server log or the SQL server
agent log. In the SQL server I get the message that the job run succesfull.
This is correct because the job runs succesful. The error message in the
event viewer seems to be not correct.
The happens on a SQL server 2000 cluster environment with Windows Server 200
3.
Hopefully someone can help me with this problemHi
"cas" wrote:

> I have got a strange porblem. In the application log of the event viewer t
he
> following error message apear:
> SQL Server Scheduled Job 'job name' (0xE90E17B42DE94240935ED80B7702BD49) -
> Status: Failed - Invoked on: 2007-02-13 08:00:00 - Message: The job failed
.
> Unable to determine if the owner (sa) of job job name has server access
> (reason: Unable to connect to server - check SQL Server and SQL Server Age
nt
> errorlogs).
> This error message does not apear in the SQL server log or the SQL server
> agent log. In the SQL server I get the message that the job run succesfull
.
> This is correct because the job runs succesful. The error message in the
> event viewer seems to be not correct.
> The happens on a SQL server 2000 cluster environment with Windows Server 2
003.
> Hopefully someone can help me with this problem
This sounds like you have something similar to
http://support.microsoft.com/default.aspx/kb/286253 although not the same
message it could be a conflict occurring when two jobs are run at the same
time. Have you checked the schedules for your jobs?
John|||John,
This is the only job that is scheduled at 08:00 in the morning. This is not
the same as in http://support.microsoft.com/default.aspx/kb/286253
The error message only apear in the event viewer and not in SQL logs. In SQL
server the job is succeeded, and this is correct. I can see that the results
of the job are OK.
"John Bell" wrote:

> Hi
> "cas" wrote:
>
> This sounds like you have something similar to
> http://support.microsoft.com/default.aspx/kb/286253 although not the same
> message it could be a conflict occurring when two jobs are run at the same
> time. Have you checked the schedules for your jobs?
> John|||"cas" wrote:

> John,
> This is the only job that is scheduled at 08:00 in the morning. This is no
t
> the same as in http://support.microsoft.com/default.aspx/kb/286253
> The error message only apear in the event viewer and not in SQL logs. In S
QL
> server the job is succeeded, and this is correct. I can see that the resul
ts
> of the job are OK.
>
So you haven't tried changing the schedule to see if it still occurs?
John