How can we help you today? How can we help you today?
webrunner

Activity overview

Latest activity by webrunner

Results from SQL Data Compare of msdb
Hello experts, I have tried SQL Data Compare 12 with the msdb database on two different servers and get blank results. I mean totally blank - not a list saying all data is identical. Does anyone kn...
3 followers 4 comments 0 votes
SQL Prompt 7.2.2.273 update took away Source Control?
Hello experts, A few days ago I decided to update my SQL Prompt to version 7.2.2.273. Now it seems when I open SQL Server Management Studio, the source control icons for one of my database servers ...
1 follower 1 comment 0 votes
SQL Source Control icons
Hello experts, What do the SQL Source Control 3 icons mean? For example, one database that I linked to source control shows a green cylinder with a small gray sphere near the bottom, but another da...
1 follower 1 comment 0 votes
Thanks for the update. Which version of the patched SQL Monitor should we use if we are running SQL Monitor 3.3? Thanks again, webrunner / comments
Thanks for the update. Which version of the patched SQL Monitor should we use if we are running SQL Monitor 3.3? Thanks again, webrunner
0 votes
SQL Prompt 5 and INSERT statements
Hello experts, When I format SQL for an INSERT statement, the columns in the INSERT clause are always formatted with a line break after each column. But I want them to match whichever format I choo...
0 followers 0 comments 0 votes
Hello again, Chris, With help from my systems team I was able to test the connection via SSMS and figure out that it was a firewall issue. You can close out this issue as resolved. Thanks again, webrunner / comments
Hello again, Chris, With help from my systems team I was able to test the connection via SSMS and figure out that it was a firewall issue. You can close out this issue as resolved. Thanks again, we...
0 votes
Thank you, Chris, for your reply. I am looking into this now and will reply with results once I have installed SSMS on the monitoring server and tried the steps you recommended. - webrunner / comments
Thank you, Chris, for your reply. I am looking into this now and will reply with results once I have installed SSMS on the monitoring server and tried the steps you recommended. - webrunner
0 votes
Hello chriskelly, Thank you so much for your reply. The log information is posted below. - webrunner Date Group Event Outcome Exception Exception message 10 Jul 2014 9:55 AM SQL GetUtcServerTimeAndProcessId Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL GetVersion Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL GetErrorLogPath Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL #4Jv Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL #nKv Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL #IKv Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL #LVG Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL Database Custom Metrics - fetching online databases Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL #7Jv Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:55 AM SQL Ping Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 10 Jul 2014 9:52 AM SQL #2Kv Cannot connect SqlException A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) / comments
Hello chriskelly, Thank you so much for your reply. The log information is posted below. - webrunner Date Group Event Outcome Exception Exception message 10 Jul 2014 9:55 AM SQL GetUtcServer...
0 votes
Connection failed for (local)
Hello experts, I want to know the possible causes of this scenario, and how it can be fixed. 1. I am running SQL Monitor 3.3. 2. We recently upgraded two servers from SQL 2008 R2 to SQL 2012. 3. On...
3 followers 6 comments 0 votes