It's not a certificates problem (as seen online) as we don't use encrypted connections.Īny suggestions? Otherwise we will probably resort to a full reinstall. We also checked the Surface Area Configuration tool to ensure it accepts connections. The aforementioned protocols are all enabled, and the SQL services are all running happily (apart from the SQL Server Agent, which cannot connect to SQL Server either). When you try to connect to the instance by using the TCP/IP protocol, you receive the following error message:Īn existing connection was forcibly closed by the remote host.No process is on the other end of the pipe. When you try to connect to the instance by using the named pipes protocol or the shared memory protocol, you receive the following error message:.It may flash an error: 'The application or DLL C:Program FilesSymantecBackup ExecBeSQL. (By default C:Program FilesSymantecBackupExec). Depending on the protocol used for the connection attempt, we get one of the following two errors: On the Backup Exec server, open a command prompt console and change the directory to Backup Exec installation directory. Since then, we have been unable to connect to SQL Server 2005, even locally via Management Studio. Some updates were installed during the restart, which may or may not have been a factor. After some network maintenance last weekend, we had some trouble with our development server which led to us restart it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |