08-27-2009 06:47 PM
I got a error message about "Database login failed:invalid object name systeminfo" when i try to log into the 'Administrator' after installation for 7.5.
What should i to deal with it?
Thank you in advance!
Solved! Go to Solution.
08-27-2009 07:36 PM
Did you run the sysdba fix against the db?
Had you assigned ANY server roles to the sysdba user?.. if so.. remove all of them.
08-27-2009 08:59 PM
Great! After removing the sysadmin role from sysdba. The error disappears like a charm.
Now i get a new error 'The provider on server ***** is no longer in use. Please change your connection to the correct provider', but the connection test successes when i edit the data connection.
08-28-2009 06:20 AM
Good.. the back-end is now just fine. Now you have to deal with the "front end" (client side).
When you finally got the connection manager (SalesLogix Server) correct you probably overwrote another connection to the physical db. The DataLink client side is attempting to communicate w/that (original) back end.
In the SalesLogix SYSTEMINFO table there is a field called the "PINGSERVER". It contains the name of the Windows (SalesLogix) server where the connection Manager is located that actually "owns" the connection to the SalesLogix physical database.
SalesLogix db connection 101:
A - A physical (SalesLogix) database can only have ONE (1) has it's owner/master
B - A SalesLogix Server (Connection Manager) can manage/own many physical SalesLogix databases. They do not have to be on the same server as the database since they use the db's native OLEDB connection.
C - The client DataLink connection to the SalesLogix database is actually made to a SalesLogix Server managing/owning that physical database.
D - There can be many client DataLink connections to a SalesLogix Server.
08-28-2009 06:21 AM
08-31-2009 06:50 AM
11-05-2009 03:06 PM
So - If I installed the saleslogix connection manager using the local account on one SQL server, I should still be able to create a connection to a database on another SQL Server ?
11-05-2009 03:44 PM
04-03-2011 08:34 AM
I upgraded a 7.2.2 database running on sql 2k on win server 2003 to 7.5.3 running on sql 2008 R2 win server 2003 dev server. Luckily there's no sync server. This has been working in dev for about 2 weeks. Yesterday I installed 7.5.3 on the new production server from the same source files running win server 2003 and sql server 2008 R2. I ran the sql script to update sysdba, verified the sysdba users has no server rolls, and now I am getting this error message on both the dev and production server. I set the pingserver to the new server name, but that did not fix it? What else can I look for?