Home » 2013
Yearly Archives: 2013
DPM Errors with SQL Server Windows Management Instrumentation
Error in DPM:
“DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer”
In order to fix the error:
- Login to your database server
- Open Command Prompt and browse to C:\\Program Files (x86)\\Microsoft SQL Server\\100\\Shared
- Run the command: mofcomp sqlmgmproviderxpsp2up.mof
mofcomp C:\\Program Files (x86)\Microsoft SQL Server\\100\Shared\\sqlmgmproviderxpsp2up.mof
CertMgr.exe Tool
The Microsoft CertMgr.exe tool is included in few SDKs like the Windows SDK, Drivers SDK, and with Visual Studios. As of this writing it is a standalone executable and can simply be copied to other computers with requiring installation or other support files. (more…)
IIS port (socket) pooling
To add an IP address to the IP inclusion list
- Click Start, and then click Run.
- Type cmd, and then click OK to open a command prompt.
- Type the following, where xxx.xxx.x.x is the IP address you want to add:
httpcfg set iplisten -i xxx.xxx.x.x
When this succeeds, Httpcfg returns the following:
HttpSetServiceConfiguration completed with 0
To view additional status codes, see the Httpcfg help.
- After the IP address is added, use the following command to list it:
httpcfg query iplisten
Httpcfg returns the following:
IP :xxx.xxx.x.x
- From the command prompt, stop the HTTP service and its dependent services. To do this, type the following string at the command prompt:
net stop http /y
- From the command prompt, restart the HTTP service and it dependent services. To do this, type the following string at the command prompt:
net start w3svc
Note When you start w3svc, all services that were stopped when HTTP was stopped will start.
Uninstall System Center 2012 DPM Agent From The Command Line
http://support.microsoft.com/kb/2756127
To uninstall an update, run the following command:
Note The <RTMProductCodeGuid> placeholder represents one of the following GUIDs:
| Server | 7348450D-5558-4CA6-8E71-044720D304F2 |
| Console (amd64) | 95241780-B772-4A42-A1F0-8FA951FAF619 |
| Console (x86) | 4FC5546F-AD4A-4C76-9B48-DF11F946EDD0 |
| Reporting | A1A61449-81E0-4C25-82DD-92B0A3CB4E77 |
| WebConsole (amd64) | 20F530CC-FD73-43FE-ABD3-138D140A77A9 |
| Agent (amd64) | 5155DCF6-A1B5-4882-A670-60BF9FCFD688 |
| Agent (x86) | D14AAC0-B9A1-4CEF-B507-23755C1EBE3A |
| Agent (IA-64) | 16499EB-B3D8-4473-9EF4-AB72FDDECD4B |
| Gateway | 7032CF7-3861-4150-8EDD-4DE2540C6E7B |
Connect to Windows Internal Database (WID) on Server 2012
There has been a change to the Named Pipe path of the Window Internal Database (WID) on Windows Servers 2012. The new path uses “tsql” instead of “sql” that has been in all previous versions.
Use this string in the “Server name” field of the “Connect to Server” dialog of the Microsoft SQL Server Management Studio program:
\\\\.\pipe\\MICROSOFT##WID\\tsql\\query
Cisco VPN on Windows 8
I have run across this issue when installing both the Cisco AnyConnect VPN client and the traditional Cisco VPN client. Once the client is installed and you attempt to establish the VPN connection you might get one of the following messages: “Unable to establish VPN” or “The VPN client driver encountered an error.”
The fix is you need to change the “Display Name” in the registry. Open the following registry key and take out the extra INF stuff at the front of the “Display Name” data. The different VPN clients use different Registry keys.
HKLM\SYSTEM\CurrentControlSet\Services\vpnva\DisplayName
HKLM\SYSTEM\CurrentControlSet\Services\CVirtA\DisplayName
HKLM\SYSTEM\CurrentControlSet\Services\CVPND\DisplayName