Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, November 22, 2024 
 
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!
 Administration Forums - Installation
Forum to discuss installing SalesLogix and general installation topics. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Installation | New ThreadView:  Search:  
 Author  Thread: DataDictionary problem
Andrew Risbey
Posts: 3
 
DataDictionary problemYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Apr 08 1:01 PM
I've just moved a 6.1.2 setup from SQL 2000 to a new Windows Server 2003 server with SQL Server 2005 (Standard Ed). I can login to Administrator and Architect and connect to the database - but data changes are not being saved. Every time I try to update data in Administrator it creates this error in the event log:

Source : odbcdrv_open_cursor
Description : An error occurred attempting to retrieve table information from the datadictionary component.
Table method returned : SalesLogix OLEDB DataDictionary Access - ERROR Invalid Table Not Found in DataDictionary Buffer

I did the usual stuff with the sysdba orphaned user and I have also confirmed the sysdba login works via SQL Management Studio.

When I try to login to the Sales client, it logs the user in (shown as logged in via Administrator) but it fails to load correctly - seems to fail when loading activities.

If anyone can cast any light on this it would be much appreciated.
[Reply][Quote]
Robert Levine
Posts: 132
 
Re: DataDictionary problemYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Apr 08 8:53 AM
I'm not sure what you did, and don't have an answer for you. But possibly you could check:
1. Did you do a completely new install on the new server rather than "moving" the application? You should installed the full standard servers and administrative workstation.
2. Have you created and shared the standard Sync Logs folders?
3. Was the SalesLogix OLE-DB Provider correctly installed?
4. Have you correctly changed the references to the Sync Server Path and the Documents & Library sub-folders in the database (from old server to new)?
5. Check that the Slx services are running.
6. And possibly also check the port assignments.
[Reply][Quote]
Andrew Risbey
Posts: 3
 
Re: DataDictionary problemYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Apr 08 9:00 AM
Robert, thanks for your reply. In response:
1. I did a new install of the software, including the admin workstation. I can login to the admin workstation, use the d/b manager, etc - it's just that changes to info (such as office address) is not saved - and creates the error I mentioned. I also created a new database - and then restored a backup of the old database over this new one.
2. Yes, created and shared.
3. Yes, and it is running as a service.
4. Yes, updated.
5. Yes, both services are running - SalesLogix OLEDB Provider & SLX Server (OLEDB Service Loader).
6. Not sure what you mean by this?

One other thought was whether 6.1.2 is actually compatible with SQL Server 2005?

Thanks for any help.
[Reply][Quote]
Robert Levine
Posts: 132
 
Re: DataDictionary problemYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Apr 08 10:00 AM
Good point. I don't see Slx 6.1.2 being compatible with SQL 2005 in the SalesLogix KnowledgeBase. But then, SQL 2005 came out later than Slx 6.1.2. You might want to give Sage a call on this one.
[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 11:53:58 PM