4/29/2024 2:29:34 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
Trouble connecting to 7.0 provider
Posted: 20 Dec 09 3:48 PM
|
I have a site where we just replaced an aging server with a new box. They are running 7.0 (sp1). There are a variety of connections to the provider, including several Scribe jobs, Eventix integrator, and Communigator. All the SLX clients, the Scribe jobs, and the web service for the Eventix online registrations are all connecting fine. Communigator is having a problem. The integration works fine for Communigator until it tries to write back to SLX when it errors and cannot connect.
If you use the trusty Datalink Designer there is no trouble connecting. We are running on Port 1707 instead of 1706. If you create an empty .udl file it cannot connect. It says the provider is unavailable. The message is "Provider is no longer available. Ensure that the provider is installed properly." The guys at Communigator feel we need to resolve this so that you can do the simple connection with an empty .udl file.
I've tried changing back to port 1706, running the SLX services as Local System, running them on the usual service account (which is a local administrator on the new server), reinstalling MDAC, reinstalling the SLX providers, gutting and reinstalling SalesLogix completely. In all of this the SalesLogix always seems to run fine, but you cannot connect using the .udl file as it will not let you move off the provider tab after selecting the SLX provider. Again, the Datalink Designer does not error and allows you to choose the "SalesLogix OLE DB Provder" in any of the above scenarios. All of which makes me think it may be something I have not touched.
Any ideas what to try next? Server is Server 2003. I did try changing the port to 1707 on one of my own machines running 7.2 and I was able to connect with a .udl file. I also tried changing the port back to 1706 on the client site, which did not help. So it does not seem to be the port.
Maria Amodei |
|
|
|
Re: Trouble connecting to 7.0 provider
Posted: 25 Jan 10 11:13 AM
|
"Again, the Datalink Designer does not error and allows you to choose the "SalesLogix OLE DB Provder" in any of the above scenarios. All of which makes me think it may be something I have not touched."
What version of SQL server are you using?
If SQL Server 2005 or newer then you MUST install the SQL Native Client on any/all SLX Client machines, and also must use this as the connection 'method' for the Datalink Designer.
We don't care if the datalink designer 'allows' you to chose the "SalesLogix OLE DB Provder" . You MUST use the SQL NAtive Client as the connection and the client must be installed on any/all SLX Client machines.
Did I state Must? |
|
|
|
Re: Trouble connecting to 7.0 provider
Posted: 25 Jan 10 11:58 AM
|
Hi RJ,
It is a SQL 2000 box for the db. That's in the lineup to be updated, but not an issue for now.
I'm able to run a blank UDL file from a batch file that forces it to look to 32 bit drivers and it does find the SLX provider this way. I do get a valid connection string, which works for most programs. We have everything connecting fine now except the communigator. We may end up making a 32 bit virtual box to run the Communigator. I'll make one last try on that probably later today.
Maria
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|