SQL User cannot connect to SQL Server
paul | Tuesday, 16 August 2016 | SQL | user
A new SQL user account cannot log into the SQL server. A look into the server error logs show the errors below:
 
Login failed for user 'username'. Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.168.0.100]
Error: 18456, Severity: 14, State: 12.
 
This is an access issue with the user not having permission to connect to the SQL Server. The following command grants the correct permission:
 
GRANT CONNECT SQL TO "username"
GRANT CONNECT ON ENDPOINT::"TSQL Default TCP" TO "username";
Display Comments...
IBM Verse for Android not syncing Sent Items
paul | Wednesday, 27 July 2016 | IBM | Sent

We have had a number of users recently reporting their Sent Items were no longer syncing to their IBM Verse for Android client.

If they have multiple devices connected to Traveler then it is neccessary to get the device ID for the affected device. To do this run the Domino server console command "tell traveler show <username>" to list their settings as below:

Traveler:  IBM Traveler has validated that it can access the database mail/jdoe.nsf.
Traveler:  Monitoring of the database for changes is enabled.
Traveler:  Encrypting, decrypting and signing messages are enabled because the Notes ID is in the mail file or the ID vault.
Traveler: 
Traveler:  Canonical Name: CN=John Doe/OU=u/O=Mail
Traveler:  Internet Address: John.Doe@mail.co.uk
Traveler:  Home Mail Server: CN=Traveler/OU=s/O=Mail
Traveler:  Home Mail File: mail/jdoe.nsf
Traveler:  Current Monitor Server: CN=Traveler/OU=s/O=Mail Release 9.0.1FP5
Traveler:  Current Monitor File: mail/jdoe.nsf
Traveler:  Mail File Replicas: 
Traveler:   [CN=Traveler/OU=s/O=Mail, Traveler/jdoe.nsf] is reachable.
Traveler:     ACL for John Doe/u/mail:  Access=Manager Capabilities=create,update,read,delete,copy Missing Capabilities=none
Traveler:     ACL for Traveler/s/mail:  Access=Manager Capabilities=create,update,read,delete,copy Missing Capabilities=none
Traveler:   [CN=Traveler/OU=s/O=Mail, mail/jdoe.nsf] is reachable.
Traveler:     ACL for john doe/u/mail:  Access=Manager Capabilities=create,update,read,delete,copy Missing Capabilities=none
Traveler:     ACL for Traveler/s/mail:  Access=Manager Capabilities=create,update,read,delete,copy Missing Capabilities=none
Traveler:   [CN=Traveler/OU=s/O=Mail, Traveler/jdoe.nsf] is not reachable, status(0xa02) "Remote system no longer responding".
Traveler: 
Traveler:  Notes ID: Mail File contains the Notes ID which was last updated by CN=john doe/OU=u/O=Mail on Tuesday, September 23, 2014 5:42:17 AM BST.
Traveler:  Auto Sync User State: Monitoring enabled
Traveler:  Adaptive Sync Applications:  No applications in adapted state.
Traveler:  Last Prime Sync: Wednesday, July 27, 2016 12:56:32 PM BST
Traveler:  Banned Documents: 0
Traveler: 
Traveler:  Devices:
Traveler:  Device ID: Android_3cf63809f40ff697
Traveler:  Device Description: samsung SM-G900F:Android 6.0.1:IBM Verse/9.4.0.3 201605311401
Traveler:  Security Policy Status: Compliant
Traveler:  Security State: Clear
Traveler:  Approval State:  Approved by CN=john doe/OU=u/O=Mail on Friday, June 12, 2015 12:28:42 PM BST.
Traveler:  Last Sync: Wednesday, July 27, 2016 12:56:33 PM BST
Traveler:  Registration time: Friday, June 12, 2015 12:27:48 PM BST. Epoch Time: 1434108468830
Traveler:  Auto Sync Device State: Active
Traveler:  Auto Sync Connection State: Disconnected at Wednesday, July 27, 2016 12:56:21 PM BST
Traveler:  Auto Sync Applications to Synchronize: mail, calendar, contact, task, serviceability, security
Traveler:  Auto Sync Change Flags: clear
 
The line highlighted above shows the device ID for the device that we would want to reset.
 
Issue the command "tell traveler reset <device_id> <username>" at the Domino Traveler server console.
 
tell traveler reset Android_3cf63809f40ff697 "John Doe"
 
Or use * to reset all connected devices for that user (useful if they only have one device).
 
tell traveler reset * "John Doe"
 
A confirmation message will then be outputted to the Domino server console. When the device then next sync's it should pull down their email and the sent items.
 
Display Comments...
Another bad WSUS update
paul | Tuesday, 12 July 2016 | WSUS | kb3159706

After a Windows Update of one of our WSUS servers this week the WSUS service has started crashing.

KB3159706 (https://support.microsoft.com/en-us/kb/3159706) seems to have caused the issue. Uninstalling the update (WUSA.exe /uninstall /kb:3159706) has fixed the issue.

More information is on Lar Lohmann Blem's Blog here: http://larslohmann.blogspot.co.uk/2016/07/wsus-server-crash.html

Display Comments...
Windows Update issue causing VMWare server to lose static IP addresses
paul | Tuesday, 12 July 2016 | VMWare | KB3125574
Looks like Microsoft KB 3125574 may cause an issue on some VmWare VM's that use a VMXNet3 adapter and are running on Windows 7/Windows 2008 R2.
 
Machine's configured with static IP addresses are changing to use DHCP when the driver is updated by the Windows update. To resolve change back to use a static IP address. Seems to then lose the default gateway but readding it again then fixes this as well.
 
More information is on VmWare's website at https://blogs.vmware.com/apps/tag/microsoft-kb-3125574
 
Display Comments...
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=*"
Else
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:

launcher.ps1

$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...
Page 1 of 61 (305 Articles) << 1 2 3 4 5  Next >>