September 27, 2014 at 1:15 pm
Hello - My first post and new to the forum.
Let me explain the setup. We have remote SQL 2012 server that is running the database for our App-V 5 Management and Reporting Server.
We have 2 App-V Servers. One server has no issue connecting to the database. The other server always gets Event ID 202 error when connecting to the database. The error is as follows:
A database error occurred. Reason: 'A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)'
I shared above error message with our database administrator. He is unable to resolve the issue. Appreciate, if you guys have any input on how to resolve this error.
The SQL Server is running 2012, The App-V servers are running Server 2012.
We have App-V Admins groups that has full access to the database + both App-V Servers also has full access to the database.
I hope you guys can help me.
Thanks
Ram
September 27, 2014 at 11:25 pm
Since you confirm one server can connect without issue this would tell me it is a client issue on that server. You might verify connection strings being used between each server and verify version of the provider being used on the server to connect to the SQL Server instance.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
September 28, 2014 at 10:01 am
Thank you Shawn. Will pass on the info to our DB Admin and see, if he can figure what is stop this server from access the database.
September 28, 2014 at 10:50 am
Also check with the network admin to ensure there are no firewalls in the way.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2014 at 1:12 pm
Thanks Shaw. I setup the App-V server. The configuration on both the App-V servers are identical. No firewall created on either of the server. I would rule out firewall reason being App-V 2 server can access the database without any issue.
Just one more information - In App-V the administration of Management Server is done through web console where, I add App-V packages and deploy to clients. Do you guys think IIS has issue on Server 1 while connecting to the database.
I see event ID 202 repeating at every 5 minutes interval in event viewer. I have been struggling with this error for almost 2 weeks with no solution. Don't want to call MS to fix the issue and pay support fee. Trying to see, if, I can find solutuion.
Searched the net - unable to find any solution.
Ram
September 28, 2014 at 1:24 pm
ramlan (9/28/2014)
Thanks Shaw. I setup the App-V server. The configuration on both the App-V servers are identical. No firewall created on either of the server. I would rule out firewall reason being App-V 2 server can access the database without any issue.
Do not count out firewall unless you also configured the network access. Firewall can exist elsewhere besides "ON" the server.
Verify the connection string between the two servers. On the server having problems you can test the client/provider being used by following these steps:
1. Create a text file on the desktop, test.txt
2. Change the extension of the file to "udl", so it becomes "text.udl"
3. This creates a Microsoft Data Link ( see attached image )
From there you can test which provider IIS is using for the connection to see if it will make a successful connection.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
September 28, 2014 at 2:23 pm
Thanks Shawn. I will do the needful on Monday and update by PM.
Will definitely check firewall on the database server.
Ram
September 28, 2014 at 2:44 pm
Shawn Melton (9/28/2014)
Verify the connection string between the two servers. On the server having problems you can test the client/provider being used by following these steps:1. Create a text file on the desktop, test.txt
2. Change the extension of the file to "udl", so it becomes "text.udl"
3. This creates a Microsoft Data Link ( see attached image )
You can also try telnet to the server on the port SQL is listening on, to verify whether something's blocking the port.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2014 at 5:37 pm
Thanks - I will try everything you guys have offered on above issue. Will update tomorrow.
Ram
September 29, 2014 at 8:18 am
I was searching the net and somebody told me they had similar issue with APP-V server with the same error and advised to reset iis.
I open command prompt and typed IISRESET
Issue resolved - no event ID 202 error in event viewer. Will monitor the status for few more days to make sure it does not pop up again.
Thanks
Ram
September 29, 2014 at 3:18 pm
Same error (event id 202) started to reappear again. So will do more investigation to fix the error.
Gave all the info to the DB. Was busy - Did not find time to do necessary test. Hopefully he will do tomorrow. Will keep you updated.
Ram
September 29, 2014 at 3:19 pm
Same error (event id 202) started to reappear again. So will more investigation to fix the error.
Gave all the info to the DB. Was busy - Did not find time to do necessary test. Hopefully he will do tomorrow. Will keep you updated.
Ram
Viewing 12 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply