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!
|
|
Database login failed: Invalid object name 'SYSTEMINFO'
Posted: 30 Jun 07 1:41 AM
|
We just started getting this tonight. Has anyone ever run into this issue? No one has access to any of the SalesLogix databases on the server. The version is 7.0.1.
I went to the SalesLogix server, opened the Connection Manager and all of the connections test OK. But whenever I try to login through the Administrator or Client I am getting a
Database login failed: Invalid object name 'SYSTEMINFO'
If I edit the datalink from the client side and click Test Connection I am getting a slightly different error.
Unable to initialize data dictionary. Invalid object name 'SYTEMINFO'.,
We have a development server and I tested connecting to the SalesLogix database there. All worked fine. So this seems to be an issue with our production SalesLogix server and/or production SalesLogix database server.
At this point we are at a complete standstill. No one can access any of the databases!
Any help/suggestions would be appreciated.
Thanks,
John G.
|
|
|
|
Re: Database login failed: Invalid object name 'SYSTEMINFO'
Posted: 30 Jun 07 1:53 AM
|
Figured this out. Earlier, the SYSADMIN database role was added to the sysdba user. I don't know why this would have created the above issue, but it did. After removing the role all was well again.
Thanks for listening!
John G. |
|
|
|
Re: Database login failed: Invalid object name 'SYSTEMINFO'
Posted: 30 Jun 07 1:54 AM
|
Figured this out. Earlier, the SYSADMIN database role was added to the sysdba user. I don't know why this would have created the above issue, but it did. After removing the role all was well again.
Thanks for listening!
John G. |
|
|
|
Re: Database login failed: Invalid object name 'SYSTEMINFO'
Posted: 30 Jun 07 8:29 AM
|
VERY common and WELL KI.. In fact if you use the SalesLogix on-line knowledge base it will point you to the exact solution you performed.
Also, it's very clear in documentation that the sysdba use must have NO server roles - never 
Good to see you were able to work it out.
--
rjl |
|
|
| |
| |
|