Problems loggin in to SQL server. : SQL2005, Server 2003, Terminal Server 2003

Experts Exchange

	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

4.2

Problems loggin in to SQL server.

Asked by RHWeston in SQL Server 2005, Windows 2003 Server

Tags: SQL2005, Server 2003, Terminal Server 2003

A year ago I purchased an application which uses an SQL database in SQL Server 2005. The database is loaded on our main server, which runs W2003 SBS and is our Domain Controller, Exchange Server and print server. At the time we also had a W2003 Terminal Server running 32 bit. Some people access the database directly from their workstations, but most people use the Terminal Server. We had no problems until this week. We took our W2003 Terminal Server and rebuilt it with 64 bit W2003. We reloaded the application and thought things were going okay but have found an interesting problem.
User A has a workstation and can connect through the workstation, but when he is on the TS and tries to connect he gets a message "Could not connect to database: Cannot open database "Service" requested by the login. The login failed. Connection: Provider SQLOLEDB;Network Library=dbnmpntw;Trusted_Connection=yes;Server=lmg01\ESC;Database=Service" LMG01 is the name of our server, so LMG01\ESC is the name of the Database server. The Database is Service.
User B has no workstation, but only a thin client. User B can log in to the TS and try to connect using the same settings and is successful.
The login method is Windows authentication. When user B is asked to fill in a Database Name he can search and see 4 available databases. When user A tries to search there is no dabase found. I used Microsoft SQL Server Management Studio Express and went to the folders for Security and Logins. Both users A and B are there. I looked at every possible window. Connection properties were identical, except for the SPID. Th only other place I could see a difference was under Login Properties, User Mapping. User B did have the Database Service checked as mapped, but User A did not. I did place a check for that database and tried to save it. It would not save it and a copy of the error message is attached.
I contacted Customer Support at the firm which supplied the programs and they suggested I contact Microsoft for support. Before I go down that path I thought I would first try here. I am a novice at SQL and therefore might need extra details. Also this is Friday and I will not be able to check back on this until Monday

View the Solution FREE for 30 Days

Attachments:

sqlerror.jpg (25 KB) (File Type Details)

Error message when trying to change login mapping

20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. aneeshatti...1,605,632
2. rrjegan171,516,636
3. angelIII1,457,953
4. chapmandew927,604
5. RiteshShah654,191
6. BrandonG...623,489
7. mark_wills573,509
8. reb73484,935
9. mwvisa1474,516
10. acperkins420,181
11. ralmada387,102
12. CGLuttrell386,285
13. matthews...310,006
14. Sharath_...300,365
15. JestersGrind231,831
16. tigin44219,338
17. pssandhu211,636
18. EugeneZ202,754
19. udayakum...200,308
20. pcelba195,296
21. momi_sa...194,257
22. DanielWilson190,783
23. prabhakar...187,610
24. St3veMax182,397
25. brejk181,029

1. angelIII5,045,718
2. chapmandew3,728,125
3. aneeshatti...2,752,338
4. rrjegan171,516,636
5. mark_wills1,403,775
6. BrandonG...1,324,338
7. mwvisa1921,972
8. acperkins816,148
9. momi_sa...681,226
10. RiteshShah654,191
11. matthews...610,554
12. appari586,119
13. dtodd555,876
14. dqmq547,704
15. ptjcb545,683
16. Yveau539,545
17. DanielWilson521,282
18. EugeneZ502,048
19. reb73484,935
20. brejk449,023
21. PFrog404,802
22. PedroCGD404,474
23. ralmada389,102
24. CGLuttrell386,285
25. imitchie352,938

Problems loggin in to SQL server.

Asked by RHWeston in SQL Server 2005, Windows 2003 Server

Tags: SQL2005, Server 2003, Terminal Server 2003

About this solution