Post reply

Conneting to OLAP from rs

  • July 13, 2006 at 7:52 am

    #114287

    Hi All

    I'm, new to the this forum

    I am struggling to get My Reports that connect to an OLAP Analasys server to execute on the Web interface.

    I keep on getting the error below:

    An error has occurred during report processing. (rsProcessingAborted) 

    • Cannot create a connection to data source 'WebLogs'. (rsErrorOpeningConnection)

      • The following system error occurred: No connection could be made because the target machine actively refused it. .

    What is strange about the error is that It only occurs when I run the report through the web interface, when I run it in vs.net it executes without a problem.

    My Connection string for the data source looks like this.

    SQLQueryMode=Calculated;Default MDX Visual Mode=0;Real Time Olap=False;Safety Options=1;Secured Cell Value=0;MDX Compatibility=0;Data Source=MOTORSNEWSQL;Cache Authentication=False;Default Isolation Mode=0;Provider=MSOLAP.3;Non Empty Threshold=0;Impersonation Level=Impersonate;SQL Compatibility=0;Mode=ReadWrite;Location=MOTORSNEWSQL;Compression Level=0;Packet Size=4096;MDX Unique Name Style=0;Auto Synch Period=20000;Initial Catalog=Web Logs

    Also:

    My Report manager runs on a different Server than my SQL and OLAP

    Any advice would be greatly appreciated.

     

  • July 14, 2006 at 6:43 am

    #649221

    That's a pretty long connection string.

    The difference may be that when you're designing the report you connect to AS as yourself, but when it run it from the RS web page it may be connecting as the machine user that RS runs under.

    We use NTLM for windows authentication, and we had to edit the RS DataSource after it was deployed and specify a windows user and password that could connect to AS.

    My understanding is that if you're using Kerberos (Active Directory will use this) then the end user's id could be impersonated.

    HTH,

    Jim

  • July 14, 2006 at 8:00 am

    #649256

    I have tried doing that without any success

    I have also changed the Cubes roles so that everyone has access to see if that made a difference, but still no joy.

    Anyting else you can think of?

  • July 17, 2006 at 7:11 am

    #649506

    I got the problem sorted out

    It seems that it was someting in the connection sting after all

    Out of desperation I removed everyting except the Most common things and it now works fine

    Below is the working conn string

    Provider=MSOLAP.3;Data Source=MOTORSNEWSQL;Initial Catalog=Web Logs;Location=MOTORSNEWSQL

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply