Ask A Question

View Question

Hello!
I did everything this topic suggests to re-connect database to MS Azure instance. DB itself is up and running. When I'm trying to reconnect config files to point SQL Azure database, the relevant service doesn't start (ProGet Web Server).
Connection strings I'm trying to use:

  1. <add key="InedoLib.DbConnectionString" value="Server=ABCD.database.windows.net;Database=ProGet;User ID=admin@ABCD.database.windows.net;Password=P@ssw0rd1;Trusted_Connection=False;Encrypt=True;" />
  2. <add key="InedoLib.DbConnectionString" value="tcp:Data Source=ABCD.database.windows.net; Initial Catalog=ProGet; Integrated Security=False;User ID=admin;Password=P@ssw0rd1;" />

Windows service only starts with the initial connection string.

The error message I receive when trying to strat the service is next:
"The ProGet Web Server service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."

Product: ProGet
Version: 4.7.12

When a Windows Service doesn't start, then you can find an error message in the windows error logs...

You can also run the service interactively - http://inedo.com/support/kb/1015/running-an-inedo-products-services-interactively

This is the message from windows error logs:
"The ProGet Web Server service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
It was my initial question, what's happening with the service start? I can't make run again after connection strings update.

That's the error from the SCM, but the .NET error is also logged.

You may want to try running the service interactively in this case, then you can see the error message and identify what's wrong with the db connection.

Answer Question