Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Tuesday, May 14, 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 - Database Administration
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Database Administration | New ThreadView:  Search:  
 Author  Thread: Unable to Initialize Data Dictionary, Invalid Object Name 'SystemInfo'
Tom
Posts: 58
 
Unable to Initialize Data Dictionary, Invalid Object Name 'SystemInfo'Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 06 Jun 08 2:01 PM
I copied a SQL DB from one server to the next. I attached the DB successfully. I created a connection in the Connection Manager. When I go to add a datalink in the Datalink Properties of the SalesLogix Client, when I test the connection it says "Unable to Initialize Data Dictionary, Invalid Object Name 'SystemInfo'"

Is there some sql script I need to run to reset the sysdba account or something?

please advise.
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Unable to Initialize Data Dictionary, Invalid Object Name 'SystemInfo'Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Jun 08 4:06 AM
See here for a statement that will fixed your orphaned sysdba user: http://customerfx.com/pages/crmdeveloper/2004/10/14/1100.aspx

Execute this in Query Analyzer (or SQL Management Studio if on SQL2005) on the new database while logged in as 'sa'.
[Reply][Quote]
Alexander Pfingstl
Posts: 43
 
Re: Unable to Initialize Data Dictionary, Invalid Object Name 'SystemInfo'Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Jun 08 3:58 AM
Hi, Do you use the same sql server version?
If you use sql 2005, validate that the native client is installed on the client where you want to create the connection.
When we see this, it nearly happens that the native client is not installed on computer.
If you have this on the server where you successfully installed and tested your connection, perhaps reboot the server. We have seen situations where this helped.
[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): 5/14/2024 10:33:21 PM