This is an issue which sql 2012 often seems to throw when it is trying to catch up with operator script actions. It requires you to run the same command again to achieve the required task. Unfortunately this is another downtime feature of the latest MS product.
the full error
"Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)"
Did you enable Shared Memory and Named Pipes providers in SQL configuration? If no, try opening the SQL Server Configuration Manager utility and enabling Shared Memory (and Named Pipes to be safe). The
Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.
When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful.
Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied?
You can use SQL Server Initialize from Backup…