-
Title
Could not connect to the service after a patch upgrade Windows Server 2008 R2 -
Description
Could not connect to the service (vRanger DB), after a Windows software upgrade. After a software patch process for Windows Server 2008 R2 the GUI of vRanger fails to connect to the DB.
Event viewer shows:
vRanger Backup & Replication encountered an error during startup. The exact error message was: The EXECUTE permission was denied on the object 'vz_InventorySourceConnectionSelectAll', database 'vRangerPro', schema 'dbo'..
ervice cannot be started. System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:xxxx/XXXXXXX.svc/.Or
Another application has already registered this URL with HTTP.SYS. ---> System.Net.HttpListenerException: Failed to listen on prefix 'http://+:xxxx/XXXXXXXt.svc/' because it conflicts with an existing registration on the machine.
at System.Net.HttpListener.AddAll()
at System.Net.HttpListener.Start()
at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
at System.ServiceModel.Channels.TransportChannelListener.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelLicking -
Cause
After a normal patch process for Windows Server 2008R2 the vRanger 6.0.2 GUI fails to connect to the Data Base vRanger PRO. The GUI of vRanger crashes with "Could not connect to the service message." Possible cause The Level Access for the vRanger Pro User is empty.
Possible cause:
Microsoft Baseline Security Analyzer (MBSA) checks for available updates to the operating system, Microsoft Data Access Components (MDAC), MSXML (Microsoft XML Parser), .NET Framework, and SQL Server. MBSA also scans a computer for insecure configuration settings. When MBSA checks for Windows service packs and patches, it includes in its scan Windows components, such as Internet Information Services (IIS) and COM+. MBSA uses Microsoft Update and Windows Server Update Services (WSUS) technologies to determine needed updates. This Microsoft Update data source is obtained either directly from the Microsoft Update Web site or, if offline or in a secure environment, from an offline catalog file named Wsusscn2.cab.
-
Resolution
If a system are going to perform and update that is base on the (MBSA) please ensure to follow this:
1. On the Programs menu, click Microsoft Baseline Security Analyzer.
2. Click Scan a computer.
Make sure that the following options are not selected, and then click Start scan.
*Check for Windows administrative vulnerabilities
*Check for weak passwords
*Check for IIS administrative vulnerabilities
*Check for SQL administrative vulnerabilitiesStarting the vRanger Service. Please first follow the instructions that appears on the links ( at the end of this document), If during the boot process of vRanger continues showing "Could not connect to the service..." please follow the next instructions:
1.) Logon to the vRanger Pro server.
2.) Stop all vRanger Services. vRanger Service -> vRanger FLR -> vRanger API.
3.) Use SQL Management Studio to login into vRanger local DB: Start | All Programs | Microsoft SQL Server 2005/2008 | SQL Server Management Studio Express.
4.) Attach to the server running your vRanger database.
5.) Check the credentials and permissions for the vRangerUserPro account. To do this navigate to:
Security | Logins folder | Right click on the account running the vRanger database, default is vRangerProUser | Select properties | Click in the Server Roles and select the appropriate credentials for your vRangerProUser. Please consult your DB administrator if you cannot do this please use the Chat option from our main web page using your registered account or create a SR ( service request).
3.) Close the management studio.
a) Start the vRanger Service then the FLR service and API service.
After this try to open the vRanger Backup & Replication program and check if the GUI pass the process to connect to DB.
The following articles refers to similar issues if you cannot fix the problem with the above resolution please review those ones:
-
Additional Information
The vRanger Pro DB vRanger creates an account to connect to the Quest database. This account uses a default password of “V!ZionC0re”. Quest Software recommends changing this default password. You may enter a new password after login using this account