heteronymous
asked on
ODBC SQL Server Driver SQL Server Invalid object name 'SyUser' - Windows 7 64-bit, 32-bit Deltek FMS failure connecting to SQL Server server-based data.
Have one machine at a location running Windows 7 Pro 64-bit and it's running Deltek FMS just fine. Deltek FMS also calls some part(s) of itself "Wind2" - and uses MS FoxPro Visual locally and connects to a SQL server instance on a server (2008 SBS).
I'm trying to now get it working on a new Win 7 Pro (64-bit) PC and (after first installing dotnet 1.1 per http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/how-to-install-net-framework-11-in-windows-7-64/eb1e6232-e874-432e-ab43-17660e25e43d ) as required by this app.
Everything installs fine. As mentioned above, this is a network server, local (client app) install (of Deltek client) type setup.
The installer is run from the mapped drive with the Deltek install, per the instructions (which err on the rather vague side).
When launching Deltek, the error is:
An error occurred attempting to communicate to the database server:
[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object name 'SyUser'
I manually duplicated the ODBC settings via Windows\SysWOW64\odbcad32.
based on the settings from the working install on the other Win7 workstation (also 64-bit)
and still get the same error.
The SQL driver definition is to use a SQL-server based login, the Client Config (Network Library Configuration) is set correctly to Servershortname\Deltek and is set to and specifies to "change the default database" to FMS_Companyname
and still the error (above) persists.
Any help welcome, TIA !
I'm trying to now get it working on a new Win 7 Pro (64-bit) PC and (after first installing dotnet 1.1 per http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/how-to-install-net-framework-11-in-windows-7-64/eb1e6232-e874-432e-ab43-17660e25e43d ) as required by this app.
Everything installs fine. As mentioned above, this is a network server, local (client app) install (of Deltek client) type setup.
The installer is run from the mapped drive with the Deltek install, per the instructions (which err on the rather vague side).
When launching Deltek, the error is:
An error occurred attempting to communicate to the database server:
[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid object name 'SyUser'
I manually duplicated the ODBC settings via Windows\SysWOW64\odbcad32.
based on the settings from the working install on the other Win7 workstation (also 64-bit)
and still get the same error.
The SQL driver definition is to use a SQL-server based login, the Client Config (Network Library Configuration) is set correctly to Servershortname\Deltek and is set to and specifies to "change the default database" to FMS_Companyname
and still the error (above) persists.
Any help welcome, TIA !
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks very much. Daniel, while not providing the "solution" per se, you led me in the right direction.
Part of this really is "archeology" as there's *zero* documentation by the prior IT company on how they set up the existing installation. It turns out there's a *duplicate* folder (with ".new" at the end) that has the working (last/most current version of the installer), but the actual data lives in the wind2 folder not wind2.new.
Examining a working XP install led me to the wind2.ini file which mapped to <X>:\wind2
mapped drive (as require for this software) server location - where "<X>" is a consistent drive mapping for all client machines.
Part of this really is "archeology" as there's *zero* documentation by the prior IT company on how they set up the existing installation. It turns out there's a *duplicate* folder (with ".new" at the end) that has the working (last/most current version of the installer), but the actual data lives in the wind2 folder not wind2.new.
Examining a working XP install led me to the wind2.ini file which mapped to <X>:\wind2
mapped drive (as require for this software) server location - where "<X>" is a consistent drive mapping for all client machines.
I'm glad you solved your problem.
Regards,
Daniel
Regards,
Daniel
ASKER