PRTG issue executing running Custom Sensor on 64-bit Windows
paul | Thursday, 19 May 2016 | PRTG | vbs

We recently experienced an issue executing Custom Sensor VBS scripts on 64-bit machine. The scripts would execute fine on 32-bit Windows machines but did not produce the expected results when executed on 64-bit Windows machines.

This was caused by the PRTG Remote Probe's running the Custom Sensor in 32-bit mode on 64-bit Windows machines. When a vbs/Powershell script is executed in 32-bit mode on a 64-bit machine then it does not have access to files the System32 folder (where 64-bit programs are stored). It is neccessary to change the script to use the SysWOW64 folder (where the 32-bit programs are stored) or use the sysnative path.

For example:

netint.vbs (original script)

strCommand = "netsh.exe mbn show signal interface=*"
Set WshShell = CreateObject("WScript.Shell")
Set WshShellExec = WshShell.Exec(strCommand)
Can be changed to:
netint.vbs (new script)
Set fso = CreateObject("Scripting.FileSystemObject")
If (fso.FileExists("c:\windows\sysnative\netsh.exe")) Then
strCommand = "c:\windows\sysnative\netsh.exe mbn show signal interface=*"
strCommand = "netsh.exe mbn show signal interface=*"
End If
Set WshShell = CreateObject("WScript.Shell")
Set WshShellExec = WshShell.Exec(strCommand)


This is also affects Powershell script. This can be worked around the same way by using the sysnative path to access any programs called in the script or calling the script in 64-bit mode from the Custom Sensor powershell script as below:


$powershell=join-path $PSHOME.tolower().replace("syswow64","sysnative").replace("system32","sysnative") powershell.exe
&"$powershell" -NonInteractive -NoProfile -ExecutionPolicy Bypass -file "C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\custom1.ps1"
The called Powershell script should then execute in 64-bit mode.
Display Comments...

When trying to use the "edit top 25 rows" in SSMS (SQL Management Studio 2012) the application displayed the error dialog "Exception has been thrown by the target of an invocation (SQLEditors) Unable to find the requested .Net Framework Data Provider. It may not be installed (System.Data)"

1. Search C:\Windows\\Framework\vX\machine.config (where vx is the version of .net you are using) for the file machine.config. Version used by SSMS can be found in SSMS menu "Help _. About...".

2. Edit XML file and search for tags <DBProviderFactories>. Ensure there is a matching </DBProviderFactories> to close it.

3. Remove any extra duplicate closing tags.

4. Save and restart SSMS.

Try it again.

Display Comments...
Domino file locking issue
paul | Tuesday, 17 May 2016 | IBM | Domino

Occasionally we get NSF files locked on clustered Domino servers and this results in an error like the one below when attempting to access them.

Database Fixup: Unable to fixup database d:\Domino\data\mail\jayz.nsf: This database is currently in use by another person or process, and cannot be accessed at this time.  In order to share a Notes database, it mvia a Domino Server by all users of the database.

This looks like a non-Domino process has a lock on the file but is actually the Cluster Replicator causing the issue. Restarting the server clears the lock but if it cannot be restarted then using the Unlocker application can force the release of the file lock.

1. Install Unlocker ( on Domino server

2. Right click on NSF file in Windows epxlorer and select Unlocker

3. Select Unlock to force the release of file locks

Try accessing file again.

Display Comments...
Bad Windows WSUS Update
paul | Monday, 09 May 2016 | Microsoft | WSUS

After April's Patch Tuesday our Windows Update Servers stated having issues with the WSUS Service terminating unexpectedly, with event 7031, every 10 minutes.

Looking at the updates installed on patch Tuesday it was easy to locate the one related to WSUS, KB3148812, and uninstall it. Normal service resumed after that.

More information on the bad update is on the WIndowsIT Pro website at:

Display Comments...
Dell Kace K1000 - "Access Denied: Please contact Administrator."
paul | Tuesday, 03 May 2016 | Kace | Access
User cannot log into K1000 Administrator portal (http://kace/admin) even with a role which has administrator console permissions assigned to it. User can log in using the User portal but when they tried to access the Administrator portal the login was rejected with the error "Access Denied: Please contact Administrator.".
This was found to be due to the Role's Administrator Console Permissions. Affected role had Write access selected in one item and All Hide selected above it. Editing and selecting options again and then saving role the allowed the user to log in again.
Display Comments...
Page 1 of 60 (301 Articles) << 1 2 3 4 5  Next >>