fiogf49gjkf0d SalesLogix Customizations typically wouldn't cause this problems.
Things to check:
a) Verify that the Connection defined within "Connection Manager" did Save the PAssword (Editing and clicking on the Test button, if the password is saved, it would work with no problem).
b) Verify that the Admin WorkStation has the Correct SQL Client Installed. For Example, if you are using SQL 2008, but your workstation doesn't have SQL Native Client 10.x it won't run.
c) Make sure that Name Resolution is in Place. If you define the Connection with "SERVERNAME" then the workstation should be able to resolve "SERVERNAME"
d) Using SQL Configuration MAnager (on the client), restrict the Protocols to TCP/IP
e) Use netstat to check what Connections are being established. You should be able to see the Connection to Server:1706 for SLX, and one for SQLServer:1433 (unless using a diff port) for SQL Server.
When using different Versions of SLX, you ussually don't get "Connection" errors. You may get an error telling you that the DB is not of the Correct Version and/or that it will be Updated (depending on the Circumstances).... |