Dynamics GP stopped working on Vista (won't login to the server)

(0) Share

Report

Posted on by AJC

Hello Everyone, Looking for a bit of help!! We've been having an issue since Tuesday where 3 PC’s we have running Vista wont login to Dynamics; basically when login in Dynamics freezes after entering your users name and password, is shown in task manager as not responding and stays this way for several minutes until it then shows an error pop up saying “Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again.” We have had our IT support company looking into this but they don’t seem to have a clue as to what might be causing it. Just wondering if this is something anyone here has come across before, and if you know of a way to fix it? Everything worked fine up until Tuesday, there haven’t been any changes to the server that should effect it and I have tried resorting Vista on one of the machines to a time when it did work. Everybody running XP still has access, but I have recently tried installing Dynamics onto a old spare XP PC and that has the same problem. I have also tried reinstall Dynamics and the ODBC data server config but still nothing, tried running it under XP compatibility in Vista and with admin rights neither worked. Into our 3rd day now of not been able to login, getting a bit desperate for a solution.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Jivtesh Singh on at

Like (0)

Report

Do you have UAC enabled ? Try disabling it, restart and try again. That will help narrow down the problem.

Which ODBC are you using ? SQL Server Native Client ?

Is it a 32 bit system or a 64 bit system ?

Can you access the server from these VISTA workstations ? Try pinging the server, What message do you get ?

Jivtesh
www.jivtesh.com - GP Blog
www.gpwindow.com - GP Resources from GP MVPs and Experts

Was this reply helpful? Yes No
AJC 95 on at

Like (0)

Report

Thanks for the quick reply, you are better then the people we pay!!! UAC was enabled but disabling it has no effect the problem still occurs. Using SQL native. 32 Bit system Vista Business and Windows Small Business Server 2003 All the PC's connect to the server fine, pings in

Was this reply helpful? Yes No
Jivtesh Singh on at

Like (0)

Report

Are you testing logging in with the same user on XP and Vista ?

Can you validate your ODBC, test the connection when you run the ODBC Wizard ? Compare the ODBC on Vista and XP. There could be a problem with the server name.

If that doesn't help, create a DEXSQL.LOg and see what error you are getting in there. Check out this article on how to enable the log using Support Debugging Tool. http://dynamicsgpblogster.blogspot.com/2010/08/enabling-dexsql-logs-with-support.html

or follow these steps

Open Windows Explorer and locate the DEX.INI file. It will be under your GP installation folder for v9, and under the Data subfolder for v10.
Edit the file with notepad. Locate the following entries in the file and set their values to True
SQLLogODBCMessages=TRUE
SQLLogSQLStmt=TRUE

Jivtesh
www.jivtesh.com - GP Blog
www.gpwindow.com - GP Resources from GP MVPs and Experts

Was this reply helpful? Yes No
AJC 95 on at

Like (0)

Report

We have tested with the same login information yes. Login is successful on either a working XP machine or on the server it's self, but not with the Vista machines. log info: /* /* Date: 09/02/2010 Time: 15:01:03 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:01:03 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:01:03 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:01:03 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:01:03 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:02:06 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:02:06 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:02:06 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:02:06 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:02:06 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:03:09 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:03:09 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:03:09 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:03:09 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:03:09 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:04:12 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:04:12 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:04:12 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:04:12 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:04:12 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:05:15 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:05:15 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:05:15 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:05:15 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:05:15 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:06:18 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:06:18 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:06:18 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:06:18 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:06:18 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:07:21 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:07:21 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:07:21 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:07:21 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:07:21 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:08:24 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:08:24 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:08:24 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:08:24 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:08:24 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:09:27 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:09:27 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:09:27 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:09:27 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:09:27 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:10:30 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:10:30 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:10:30 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:10:30 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:10:30 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/ /* /* Date: 09/02/2010 Time: 15:11:33 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. */ /* /* Date: 09/02/2010 Time: 15:11:33 SQLSTATE:(08001) Native Err:(-1) stmt(0):*/ [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.*/ /* /* Date: 09/02/2010 Time: 15:11:33 SQLSTATE:(S1T00) Native Err:(0) stmt(0):*/ [Microsoft][SQL Native Client]Login timeout expired*/ /* /* Date: 09/02/2010 Time: 15:11:33 SQLSTATE:(00000) Native Err:(0) stmt(0):*/ */ /* /* Date: 09/02/2010 Time: 15:11:33 SQLSTATE:(00000) Native Err:(0) status(7):*/ SWSTATUS DUMP*/

Was this reply helpful? Yes No
Jivtesh Singh on at

Like (0)

Report

It looks like the SQL Server in the ODBC is specified incorrectly - maybe the instance name ? You might want to triple check that!

Which version of GP and SQL Are you on ? Is your SQL server on a named instance or the default setup.

When you setup GP, do you specify the server name during the install ? I saw the same error once when the user was specifying the wrong server name instance during the install.

Here are a couple of articles that address the error you are getting -

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx

http://blogs.msdn.com/b/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx

Was this reply helpful? Yes No
AJC 95 on at

Like (0)

Report

Thanks for your help Jivtesh.

I think after rechecking everything the problem lies in remote conections... I have looked in Surface Area Config and the instance is listed as local only but it won't change over to remote. Everytime I chancge to remote/ tcp-ip and named pipes, stop and start the service when re-opening the services and connections to re-check the settings it goes back to local only! any one got any ideas on how to get it to stay on remote conections?

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi,

It looks like you're on the way to backup all your Databases and re-install your SQL 2005 server... Use Microsoft's GP scripts for SQL server migration to capture all your user's credentials on the server, so you don't have to recreate them by hand. Re-installating the SQL server might take you 1-2 hours, but then you know where you are. Continuing to debug your problem may take you several hours or days, thus keeping your users from working... Backup also all your maintenance plans on the server if have some...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

Have you reviewed the Services running on the SQL server. Perhaps one of the remote services has stopped and not restarted after a reboot.

Was this reply helpful? Yes No