Hello, A couple of our remote users(WINDOWS 7 Machine) getting the error "Database login failed: unspecified error." while login through SLX Client.

They had a new remote DB cut and DB were attached successfully.

- Tried recreating datalink and database connections. From Connction Manager DB connction is tested successfully. However from SLX Client the test connection is getting Failed.

- All Users are running under global firewall setting so not a firewall issue either.

I stopped SLXSystem.exe .while restarting it not able to restart...throwing error like"....not responded in timely fashion..."

Please help how to troubleshoot this "Database login failed: unspecified error."

If the database is a remote database then you can run Connection Manager - set the connection name to (Local) and then re-create the connection in SLX to this new connection (probably best to delete both connmgr and client entries to be sure). That way you'll avoid the network and be accessing locally and avoid any f/wall issues. Which SQL Provider are you using with 2005? MSSQLOleDB or Native Client?

In connction Managr we are using SQL Native Client.

Should I create the connection in the same way in Client? Thanks

In a remote situation the host & remote are one and the same:

In Connection Manager - specify the connection to the SQL Server - in here, set connection as (Local) - unless you are using a named instance - in which case, go with standard hostname but make sure it resolves and tests. The connection will use a provider which should be SQL Native client. You will use sysdba/masterkey as login details.

In SLX Client (Admin, Architect etc) you will then define the connection (using Data Link Manager, the ellipses) to create a connection to the provider. In here you will drop down the SLX server and then the connection defined above. You will use the SLX Username/password here.

However: On logging in - it will interrogate the server via connmgr and attempt to open the same connection that SLX Server does - using the same SQL Provider (SQL Native Client) so it will hit the same firewall issues as if it were connecting across the network. So, using firewall manager ensure the SQL Server ports are open and also ports 1706-1707. I generally create a rule that enables 1706-1707,1433-1434 to enable all.

Also, run CliConfig and make sure the connection settings are TCP-IP.