|
|
|
It’s well past my bedtime – AGAIN! But I wanted to catch you up on developments. I’ve got my eardrops, but it’s hard to do the 4X a day when you’re on site at the client.
I’m feeling tired, but my biggest complaint is my feet. The numbness is a real irritant. It makes walking uncomfortable and a little shaky.
The project is going well and I will be coming home tomorrow night.
I was having a problem with one station. If a user could successfully log into Dynamics on that station, then they could not log into Dynamics on any other station, unless I reset their password on anther station. I didn’t change the password, I only reset it. Once I did that they could log in on the other stations, but now I could not log them into the original station – until I reset the user password on that station.
Microsoft tech support came to my rescue. They had me check out how the SQL ODBC driver was set up on the one station. I immediately found the problem. On all stations the ODBC driver referenced the SQL Server as the server name. On my one station, the ODBC driver referenced the IP address of the server. I change the one station to use the sever name and my problem went away.
I am curious that everything worked fine using Dynamics 8.0, 9.0 seems much pickier about security issues.
The client is still using SQL Server 2000. The hardware tech that works with me on this client said that SQL 2005 is not for the faint of heart.
Posted by The Vorlon at April 12, 2006 9:55 PM