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!

External Development Forums - SalesLogix OLEDB Provider
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.

Forums RSS Feed

Back to Forum List | Back to SalesLogix OLEDB Provider | New Thread

View: Search:

Author

Thread: Saleslogix OLEDB Connection using Shared Memory protocol

Guy Barrett
Posts: 63

Saleslogix OLEDB Connection using Shared Memory protocol Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 09 Aug 12 7:31 AM

Hi All,

Both my Saleslogix Server and SQL Server are on the same box, so presumably when I set up a connection I should be able to use the "Shared Memory" protocal for speed? So, I set the "Network Library" value in the connection manager to "dbmslpcn", and a clicking the test button in the connection manager works a treat.

However, from the client end, it will not connect. I get a "Cannot initialise data dictionary" error when I test the connection at the client end. If I ignore the error and attempt to login using the connection anyway, I get the error "Cannot open database 'Saleslogix' requested by the login. Login failed."

Has anyone else successfully connected using the SQL Server "Shared Memory" protocol?

I'm using SLX 7.22.1871, on SQL Server 2005 (latest SP), and I've ensure the protocal is enabled in the SQL configuration.

Please Help?

[Reply][Quote]

Page 1 of 1

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!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 4/18/2024 9:55:40 PM