Difference between revisions of "VT3000 - Errors - Database Connection is Closed"

From Versacall Support
Jump to navigation Jump to search
m (Text replacement - "https://www.linkedin.com/company/versacall-technologies-inc-/mycompany/" to "https://www.linkedin.com/company/versacall/")
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Overview=
{|style="background:transparent; color:black" border="0" height="230" align="center" valign="bottom"
These instructions explain how to resolve the "Database Connection is Closed" error received when logging into VT3000. This error can be received in any of the VersaCall programs as they are all related to the same issue.
|+style="background:transparent|
 
|-align="center"
 
|
=Error Message=
|[[Image:CallUsBtn.png|Call Now 858-677-6766]]
 
|
<gallery widths=503 heights=218>
|[[Image:SubmitTckBtn.png|link=https://www.versacall.com/customer-support/service-ticket]]
File:DBClosed1.png
|
</gallery>
|[[Image:EmailUsBtn.png|link=mailto:support@versacall.com?Subject=Help%20Needed%20Wiki&body=Type%20Message%20Here]]
 
|}
 
<br>
=Explanation=
 
This error occurs because the VersaCall software cannot communicate with the SQL Server where the databases are stored. To fix this error we need to determine if the SQL Server instance is local or if we are communicating with a server on your network.
 
 
=Requirements=
 
'''1.''' The VT3000 Core Software installed.
 
'''2.''' Access to the Computer/Server where the VersaCall software is installed.
 
'''3.''' Permission to Start & Stop a Windows service.
 
 
=Instructions - SQL Location and Login Information=
To complete the steps in this section you must be logged on to the computer/server hosting the VersaCall software.
 
'''1.''' Using Windows Explorer, navigate to the following location.
 
<gallery widths=112 heights=112>
File:DBClosed2.png
File:DBClosed3.png
File:DBClosed4.png
File:DBClosed5.png
File:DBClosed6.png
</gallery>
 
 
'''2.''' Click once on the "DatabaseRegistry.xml" file so that it is highlighted.
 
<gallery widths=112 heights=112>
File:DBClosed7.png
</gallery>
 
 
'''3.''' Right click on the "DatabaseRegistry.xml" icon - select File - Open With - select Notepad.
 
<gallery widths=536 heights=189>
File:DBClosed8.png
</gallery>
 
 
'''4.''' At the top of the document you will see "Address" in the text. If the text reads as "127.0.0.1\SQLEXPRESS" or another name (has to show 127.0.0.1 to be local), proceed to the next section. If your address begins with anything other than "127.0.0.1" it means your databases are stored on a server on your network. You will need to contact your IT department. They will be able to determine if the server is running or not and if your username and password are still valid. In many cases the passwords have been changed, see the "Instructions - Network Database" section below.
 
<gallery widths=446 heights=268>
File:DBClosed9.png
</gallery>
 
 
=Instructions - Local Database=
Use these instructions if your Address began with 127.0.0.1.
 
'''1.''' Open Windows Explorer.
 
<gallery widths=100 heights=84>
File:DBClosed10.png
</gallery>
 
 
'''2.''' In the address field type in "Control Panel" - hit the Enter key.
 
<gallery widths=338 heights=117>
File:DBClosed11.png
</gallery>
 
 
'''3.''' Select Administrative Tools from the list of options.
 
<gallery widths=203 heights=53>
File:DBClosed12.png
</gallery>
 
 
'''4.''' Select Services.
 
<gallery widths=118 heights=122>
File:DBClosed13.png
</gallery>
 
 
'''5.''' Scroll down the list of service names until you see "SQL Server (SQLEXPRESS)" if the name of your instance is different you will see that instead of SQLEXPRESS.
 
<gallery widths=530 heights=58>
File:DBClosed14.png
</gallery>
 
 
'''6.''' The Status of the service will have nothing showing. This means the service is not running and we need to restart it. If you service shows as "Running" in the status, please contact VersaCall Support.
 
<gallery widths=530 heights=58>
File:DBClosed15.png
</gallery>
 
 
'''7.''' Click on the service so that it is highlighted - select "Start the service from the options to the left of the service names.
 
<gallery widths=444 heights=92>
File:DBClosed16.png
</gallery>
 
 
'''8.''' A window will appear showing that the system is restarting the service with a progress bar.
 
<gallery widths=380 heights=177>
File:DBClosed17.png
</gallery>
 
 
'''9.''' The service status should now show as "Running" after the restarting service window goes away.
 
<gallery widths=530 heights=58>
File:DBClosed18.png
</gallery>
 
 
'''10.''' Return to the VT3000 web interface and log in. If you get the same error again contact VersaCall Support.
 
 
=Instructions - Network Database=
If your IT department told you that the password and/or username has changed, follow the instructions below. If there is another reason for the error, please contact VersaCall Support for assistance.
 
'''1.''' With the "DatabaseRegistry.xml" file open, go the the "Password" line. Change the password that is showing to the password that your IT department provided to you.
 
<gallery widths=446 heights=268>
File:DBClosed19.png
</gallery>
 
 
'''2.''' Repeat this step for all of the databases you see in the XML file. Once all the passwords have been updated select File - Save.
 
<gallery widths=230 heights=167>
File:DBClosed20.png
</gallery>
 
 
'''3.''' Close the notepad window and all other associated windows. Open the VT3000 web interface and log in. If you get the same error again contact VersaCall Support for further assistance.
 
 
 
----
----
----
<br>
[[File:GeneralHeader.png]]
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Overview'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|These instructions explain how to resolve the "Database Connection is Closed" error received when logging into VT3000. This error can be received in any of the VersaCall programs as they are all related to the same issue.  This error occurs because the VersaCall software cannot communicate with the SQL Server where the databases are stored. To fix this error we need to determine if the SQL Server instance is local or if we are communicating with a server on your network.
|}
|}
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Requirements'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
{| class="wikitable mw-collapsible mw-collapsed" width="775px;"
|-
|style="text-align: center;" | '''See Requirements Here'''
|-
|'''1.'''  The VT3000 Core Software installed and running on your system.
|-
|'''2.'''  Physical or Remote Access to the Computer/Server where the VersaCall SQL Server Instance is running.
|-
|'''3.'''  Permission to Stop/Start a Windows Service on the Computer/Server where the SQL Server Instance is running.
|}
|}
|}
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Error Message'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|[[File:DBClosed1.png|center|503px]]
|}
|}
<br>
----
----
<br>
[[File:InstructionHeader.png]]
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 1.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Log in to Windows on the computer where SQL Server is installed - select Windows Explorer.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed10.png|center|100px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 2.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|In the address field type in "Control Panel" - hit the Enter key.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed11.png|center|338px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 3.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Select Administrative Tools from the list of options.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed12.png|center|203px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 4.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Select Services.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed13.png|center|118px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 5.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Scroll down the list of service names until you see "SQL Server (SQLEXPRESS)" if the name of your instance is different you will see that instead of SQLEXPRESS.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed14.png|center|border530px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 6.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|The Status of the service will have nothing showing. This means the service is not running and we need to restart it. If your service shows as "Running" in status, please contact VersaCall Support.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed15.png|center|530px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 7.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Click on the service so that it is highlighted - select "Start the service from the options to the left of the service names.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed16.png|center|444px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 8.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|A window will appear showing that the system is restarting the service with a progress bar.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed17.png|center|380px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 9.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|The service status should now show as "Running" after the restarting service window goes away.
{|style="margin:left;"
|valign="top" |
{|class="wikitable" style="background:white; align:center;"
|-
|[[File:DBClosed18.png|center|530px]]
|}
|}
|}
|}
<br>
----
<br>
{|style="margin:left; width: 100px; background:#eaf3ff; padding:5px; border:2px solid #000000;"
|-
|<big>'''Step 10.'''</big>
{|style="margin:left; width: 800px; background:#F0F0F0; padding:5px; border:2px solid #000000;"
|valign="top" |
|-
|Return to the VT3000 web interface and log in. If you get the same error again contact VersaCall Support.
|}
|}
<br>
----
----
<br>
{|style="margin:auto;"
{|style="margin:auto;"
|valign="top" |
|+
{| class="article-table mw-collapsible mw-collapsed" data-expandtext="&#9660;" data-collapsetext="&#9650;"
[[File:RelatedHowTos.png|center]]
!<span style="font-size:150%; color:#0645ad">Related - Step by Step Guides</span>
|align="center" |
{| class="wikitable mw-collapsible mw-collapsed" width="400px;"
|-
|style="text-align: center;" | '''Select a Guide Here'''
|-
|-
|[[VT3000 - Back Up Database - SQL Server|Backup VersaCall Databases using SQL Server]]
|[[VT3000 - Back Up Database - SQL Server|Backup VersaCall Databases using SQL Server]]
Line 170: Line 265:
|-
|-
|[[VT3000 - Restore Database - VT3000 Core|Restore VersaCall Databases using VT3000]]
|[[VT3000 - Restore Database - VT3000 Core|Restore VersaCall Databases using VT3000]]
|}
|valign="top" |
{| class="article-table mw-collapsible mw-collapsed" data-expandtext="&#9660;" data-collapsetext="&#9650;"
!<span style="font-size:150%; color:#0645ad">Additional Help</span>
|-
|'''Submit a Ticket''' - https://www.versacall.com/customer-support/service-ticket
|-
|'''Training Videos''' - https://www.versacall.com/training
|}
|}
|}
|}
<br>
----
----
<br>
{|style="margin:auto;"
{|style="margin:auto;"
|+
[[File:SearchHeader.png|center]]
|align="center" |
|align="center" |
{|class="wikitable"
{|class="wikitable"
!<span style="font-size:150%; color:#0645ad">Search</span>
|-
|-
|<inputbox>type=search</inputbox>
|<inputbox>type=search</inputbox>
|}
|}
|}
<br>
----
----
 
<br>
 
[[File:VC Footer.png|center]]
{|style="background:transparent; color:black" border="0" height="200" align="center" valign="bottom" cellpadding=10px cellspacing=10px
|+style="background:transparent|
|-align="center"
|
|[[File:LinkedIn.png|Follow Us On LinkedIn|link=https://www.linkedin.com/company/versacall/]]
|
|[[File:BlogIcon.png|View our Blog|link=https://www.versacall.com/blog/]]
|}
<br>
[[Category:External Software]]
[[Category:External Software]]
[[Category:SQL Server]]
[[Category:SQL Server]]
[[Category:Errors]]
[[Category:Errors]]
[[Category:Database]]
[[Category:Database]]

Latest revision as of 19:24, 20 April 2023

Call Now 858-677-6766 SubmitTckBtn.png EmailUsBtn.png



GeneralHeader.png

Overview
These instructions explain how to resolve the "Database Connection is Closed" error received when logging into VT3000. This error can be received in any of the VersaCall programs as they are all related to the same issue. This error occurs because the VersaCall software cannot communicate with the SQL Server where the databases are stored. To fix this error we need to determine if the SQL Server instance is local or if we are communicating with a server on your network.


Requirements
See Requirements Here
1. The VT3000 Core Software installed and running on your system.
2. Physical or Remote Access to the Computer/Server where the VersaCall SQL Server Instance is running.
3. Permission to Stop/Start a Windows Service on the Computer/Server where the SQL Server Instance is running.


Error Message
DBClosed1.png



InstructionHeader.png

Step 1.
Log in to Windows on the computer where SQL Server is installed - select Windows Explorer.
DBClosed10.png



Step 2.
In the address field type in "Control Panel" - hit the Enter key.
DBClosed11.png



Step 3.
Select Administrative Tools from the list of options.
DBClosed12.png



Step 4.
Select Services.
DBClosed13.png



Step 5.
Scroll down the list of service names until you see "SQL Server (SQLEXPRESS)" if the name of your instance is different you will see that instead of SQLEXPRESS.
border530px



Step 6.
The Status of the service will have nothing showing. This means the service is not running and we need to restart it. If your service shows as "Running" in status, please contact VersaCall Support.
DBClosed15.png



Step 7.
Click on the service so that it is highlighted - select "Start the service from the options to the left of the service names.
DBClosed16.png



Step 8.
A window will appear showing that the system is restarting the service with a progress bar.
DBClosed17.png



Step 9.
The service status should now show as "Running" after the restarting service window goes away.
DBClosed18.png



Step 10.
Return to the VT3000 web interface and log in. If you get the same error again contact VersaCall Support.



RelatedHowTos.png
Select a Guide Here
Backup VersaCall Databases using SQL Server
Update VersaCall Databases using SQL Server
How to Script an SQL Database to an Earlier Version of SQL Server
Backup VersaCall Databases using VT3000 - Download Files
Backup VersaCall Databases using VT3000 - Make a Local Backup
Backup VersaCall Databases using VT3000 - Send the Backup to VersaCall
Update VersaCall Databases using VT3000
Restore VersaCall Databases using VT3000



SearchHeader.png

 



VC Footer.png
Follow Us On LinkedIn View our Blog


Retrieved from "http://support.versacall.com/index.php?title=VT3000_-_Errors_-_Database_Connection_is_Closed&oldid=9450"