Comments
1 comment
-
Hi @...,
Thanks for your post and sorry to hear about this issue!
I was doing some searching on this and there is a stackoverflow post here: https://stackoverflow.com/questions/15488922/connection-to-sql-server-works-sometimes which describes a similar issue, where connecting to a SQL database from a .NET application sometimes fails with the same error.
It sounds like there may be certain Windows or .NET updates that could be to blame, and the second most popular suggestion for this was to actually increase the timeout to 30 seconds.
Can you kindly give this a try?
You can specify a custom connection string using the steps here - https://documentation.red-gate.com/display/SA6/Configuring+reporting+on+multiple+computers#Configuringreportingonmultiplecomputers-authentication - and increase the timeout that way.
Please let me know if that helps or not!
Add comment
Please sign in to leave a comment.
[MSBuild output] Messaging.proj(14,3): error : SmartAssembly build failed:
[MSBuild output] Messaging.proj(14,3): error : Unable to connect to the SQL database:
[MSBuild output] Messaging.proj(14,3): error : 'Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1702; handshake=1174; '
[MSBuild output] Messaging.proj(14,3): error :
[MSBuild output] Messaging.proj(14,3): error : Connection string:
[MSBuild output] Messaging.proj(14,3): error : Server=VS004-SQL2008;Integrated security=SSPI;database=master;Connect Timeout=2
[MSBuild output]
Anyone else seen this? Really annoying!