Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, November 22, 2024 
 slxdeveloper.com
 Community
 Members
 General
 Architect
 External
 Web
 Downloads
 Resources
11/22/2024 8:51:28 PM







 
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 ThreadView:  Search:  
 Author  Thread: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.
Bruce Edwards
Posts: 4
 
Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 30 Apr 07 11:53 PM
fiogf49gjkf0d
Hey all;

I have a client who has recently upgraded from a SQL 2000 / SLX 6.1 sp1a install to a SQL 2005 / SLX 7.0 sp1 environment.

All has gone reasonably well, except for one machine that is returning an error that reads:

'Unable to initialize data dictionary'

whenever they attempt to log into SLX.

This machine *has* got SQL Native Client 2005 installed.

This machine sits outside the domain of the main SLX Server.

(NB: I just found out that an MSDE 2000 instance is also on that same machine - could this be causing SalesLogix to use the wrong libraries?)

Has anybody seen this issue before, or know how to resolve it?
[Reply][Quote]
Ron Buchanan
Posts: 72
 
Re: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 25 May 07 3:08 PM
fiogf49gjkf0d
A little late response... did you whip it?

Just guessing, but run CLICONFG and make sure and alias points to the IP of that external SQL box.
[Reply][Quote]
Sokha S.
Posts: 19
 
Re: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 31 Oct 07 4:02 PM
I generally get this error when the client cannot access the SQL Server. Check the datalink to see if its point to the corrected Saleslogix database. I would also check to see if both machines can see each other by pinging the Saleslogix machine. Hope that helps.
[Reply][Quote]
Frank Chaffin
Posts: 475
 
Re: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 01 Nov 07 2:11 AM
I am assuming that this is a SalesLogix Network user...

you also need to make sure port 1706 (or what ever port you selected) is open.
[Reply][Quote]
Ruchi
Posts: 19
 
Re: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Jul 08 2:06 AM
Hi,
I m getting the same problem. I tried with all the above solutions. Please let me know if any one has any other solution.

Thanks
Ruchi
[Reply][Quote]
Carla Tillman
Posts: 290
 
Re: Help: Unable to Initialize Provider error on 7.0.1 machine outside domain.Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 23 Jul 08 12:10 PM

Some additional info on this issue:

http://www.slxdeveloper.com/forum.aspx?forumid=3000&postid=11604
[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 | Subscribe to the slxdeveloper.com Latest Article RSS feed   
 
page cache (param): 11/22/2024 9:28:36 PM