August 18, 2009 at 4:10 am
Hi all,
I'm trying to get an SSRS report on a 64-bit 2K5 server with the OLEDB Provider for OLAP 9.0 to run against a 2K cube on a 32-bit 2K server with the OLEDB Provider for OLAP 8.0 and it's not playing ball. I'm getting the following error message:-
An error has occurred during report processing.
Cannot create a connection to data source 'MI1'.
The following system error occurred: No connection could be made because the target machine actively refused it. .
I've opened up the permissions as far as I can to eliminate that possible cause.
I've tried installing the 8.0 provider on the 2K5 box using ptslite.exe and ptsfull.exe, but it doesn't seem to be registering. Is there anything I can do about it and would it make a difference if I could?
Could I install the 9.0 provider on the 32 bit 2K box and would that enable the 2K5 SSRS reports to connect (without jeopardising the current OLAP reports that run on the 2K server?)
Or is it an issue between 64 and 32 bit? Or a combination of the above?
Any suggestions gratefully received. 🙂
August 18, 2009 at 5:05 am
I am a complete dunce at SSRS so apologies if this is completely wrong.
OLEDB Provider for OLAP 9.0 is the provider used to access SSAS (2005) cubes not analuysis services 2000 cubes
The provider you need is Microsoft OLE DB Provider for OLAP Services 8.0.
My justification for saying this is that I use Excel 2003 to connect to SSAS and Analysis services cubes and I have to use different providers.
Mark.
😎
August 18, 2009 at 6:12 am
Thanks for your response. I was under the impression that was true too. But I'm connecting from a 64 bit 2K5 box to a 2K cube on another server. Assuming what you say is true, do I need the 8.0 provider on the 2K5 box to do this?
However, when I try and do and do the 8.0 install on the 2K5 box this I don't seem to be getting anywhere.
August 18, 2009 at 6:32 am
PSB1 (8/18/2009)
Thanks for your response. I was under the impression that was true too. But I'm connecting from a 64 bit 2K5 box to a 2K cube on another server. Assuming what you say is true, do I need the 8.0 provider on the 2K5 box to do this?
I believe that the answer is yes. The box you are connecting from needs the provider to talk to whatever the data is on.
PSB1 (8/18/2009)
However, when I try and do and do the 8.0 install on the 2K5 box this I don't seem to be getting anywhere.
I am not sure what you are trying to install. Are you installing just the provider (the 64bit version as there are different versions) . I will have a look at my notes and add more in a bit.
Ells.
😎
August 18, 2009 at 7:36 am
have you got excel on the server where you are trying to attach to the 2000 cubes. If you have Excel 2003 on there then I have attached how you can see if you have the provider. Excel 2003 offers you the choice of which provider to use to connect.
OOh. Have you got SSMS on the machine you are trying to connect from? If so can you connect to the 2000 Analysis servies instance?
Just trying to help.
Ells.
😎
August 19, 2009 at 1:16 am
I can't connect to the 2000 AS from SSMS on the 2K5 box. I haven't got Excel on the 2K5 server, but running master..xp_enum_oledb_providers shows that I've only got the following:-
Microsoft OLE DB Provider for SQL Server
Microsoft OLE DB Provider for Analysis Services 9.0
OLE DB Provider for Microsoft Directory Services
SQL Native Client
Microsoft OLE DB Simple Provider
Microsoft OLE DB Provider for Indexing Service
So I definately haven't got the 8.0 on the 2K5 server. Could you point me to where I can get it from? Is there a 64 bit version that I have to use?
Many thanks for your help on this - it is greatly appreciated 😀
August 19, 2009 at 1:28 am
I had a quick look around and it is not easy to find. AS MS has declared 2000 as non supported getting help is going to become more and more difficult.
I am surprised more people have not had this problem. Clients I have worked for seem to be behind on Excel and so it has not been an issue. I will have a look.
Ells.
August 19, 2009 at 1:47 am
I would just suggest googling for the provider by name. Tread very carefully if you dont have a test box to test this on before you go live.
Ells.:cool:
August 20, 2009 at 1:51 am
I'll take a look. Luckily I have a test box for the first time in four years, so I can actually try it out without too much fear 🙂
I'm on leave for a few days but will let you know how I get on.
Cheers
PSB1
December 10, 2009 at 3:08 am
Now I recall doing backward compatibility testing for reports created in MSRS 2000 and running them on SSRS 2005 and had no problems, but we didn't do testing of reports across platforms and version too. But from what I'm seeing in your posting I don't think it has anything to do with version or platform. I would take another look at your connection string and perhaps do some testing. I used PortQry for testing ports to make sure they were open between servers. Ports for SSAS is on 2382/2383 but for SSAS 2000 perhaps it may be 2393/2394. Also, remember, SSAS uses strictly Windows Authentication, and SSRS impersonates your account so make sure your account is in the proper group on SSAS.
December 14, 2009 at 2:38 am
Thanks for the responese. I admit that permissions and security has never been my strong point 🙂
However, I managed to port over the 2000 cubes to 2005 and alter the reports to point at those instead. I had some issues around altering the MDX code in the dataset, but managed to get everything working eventually. I'm happier that I've moved completely off 2000 than trying to maintain a hybrid across servers.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply