Hi,

We migrating web service hosting to 64 bits windows server 2008 and done that part successfully. Part of this migartion is to use saleslogix oledb provider 6.26 for the connection and we have install 6.26 on our new machine but we still having some connection issue. The error message we are getting at the moment is:

SalesLogix OLEDB Provider Connection Factory
Connection Factory NOT configured.

Can you somebody confirm that whether:

(1) Can we still use the SalesLogix OLEDB provider 6.26 on a 64 bits windows server 2008?

If we can, is there any issues I should be aware of? I have went through quite a few list and none seemed to be fix my issue so can someone put me on a right path please.

Thanks!

Regards - Raj

You can use it on a 64-bit machine, but NOT from a 64-bit application. You need to configure the application pool to run as a 32-bit application only. To do this, select the application pool in IIS and click Advanced Settings. Then look for the property "Enable 32-Bit Applications" and chnage to True.

Ryan,

Thats one of those step I followed but no luck. Is there are any other issues causing this?

Quote: Originally posted by Raj Ubendran Ryan, Thats one of those step I followed but no luck. Is there are any other issues causing this?

That's the only thing I ever change and I've never had an issue. To be honest, I've never seen the specific message you mentioned from the "SalesLogix OLEDB Provider Connection Factory". That doesn't sound like an error coming directly from the SLX Provider. Do you maybe have your own layer or connection factory that could be throwing that? If so maybe you could get more details from the inner exception or by tracing back to that factory.

If that's not it, maybe start with a small/simple test app to see if you can isolate the root problem

You right, that error was from a test application we run here to pin point the error where it is originate from but from saleslogix client we gets the follwoing error:

"Object refrence not set to an instance of object"

Can you give any more details about where this is coming from? The SLX Provider itself won't throw an Obejct reference not set to an instance of an object error.

This is the error message I'm getting while trying to create a connection to the server:

"A connection with the server could not be established"

Is there a firewall between this server and the SLX or SQL server? Are they in different domains? Maybe to test connectivity between the servers create a simple test app that only opens a connection to see what happens.

Basically, if you're getting an error like that then it sees the SLX provider just fine, it is just unable to connect.

I run the udl from new machine for to invoke sales logix oledb provider for 32 bit machine by following:

On Run command:

C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll",OpenDSLFile C:\test.udl

Then that brings the data link properties where I could see the "SalesLogix OLEDB Provider" in the provider tab and selected that one and click <NEXT> to go to connection tab, that's it, it just carshed?

This say something that it see the SLX provider but when you trying to connect to a server (IMPORTANT BEOFRE EVEN CONNECTING TO THE SERVER) it is cashing here?

These servers are on the same domain and I can rule out fire wall 101%.

this sounds like a 2008 permissions issue. I'd verify all the slxservice users permissions are in place and reinstall the provider off the dvd under that user. Then retest

No, that didn't help...

Question:

  Are you sure that SP6 was applied succesfully?

  Have you tried uninstalling it and reinstalling it?

  Based on the Fact that the UDL test crashes after you select the Provider but before giving you the Chance to enter any info on it, it may be signs that something is corrupted.

  Are there any Event Log entries created when the UDL crashes?

  If neither of the above helps, I would follow up with Process Monitor and try to determine what makes it crash (e.g. unaccesible Registry entries, unacessible Files, missing Files, unreadable Files, Required Components, etc). I mean, it could be something as simple as a Required C Runtime library not installed on that machine.

Season's Greetings!