Wednesday, August 10, 2016

After installing SharePoint 2010 or 2013 server hangs on "Applying User Settings" or "Applying Computer Settings".

Problem: SharePoint server hangs on reboot, appears to hang at "Applying User Settings" or "Applying Computer Settings" stage of the startup process. Disconnecting the NIC, restarting, then reconnecting the NIC will get the server back online but it's a hassle and not a real solution.

Solution: Stumbled upon this article by Ed Williams. It appears Microsoft has a hotfix for this, but it seemed easier to apply the suggested registry fix. This creates a service dependency on the HTTP service so it waits for the CRYPTOSVC to start. This has resolved all our SharePoint hanging issues.

To work around the issue without installing the hotfix, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys depend on crytosvc service to be started first. To do this, follow these steps:


1. Click StartStart button, type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
3. On the Edit menu, point to New, and then click Multi-string Value.
4. Type DependOnService, and then press ENTER.
5. Right-click DependOnService, and then click Modify.
6. In the Value data box, type CRYPTSVC, and then click OK. 
7. Exit Registry Editor.
8. Restart the computer.
Thanks to Ed and to Colorado Springs SharePoint!

Wednesday, May 25, 2016

Scheduled backup fails with ANS1909E, ANS1512E rc=1 and ANR2579E rc 1

Problem: Scheduled backup fails with ANS1909E, ANS1512E rc=1 and ANR2579E rc 1

Solution: After a quick google you might find this page instructing you to run the schedule in the foreground. This is great unless the schedule is full of other nodes and you can't run it any time during the day. Instead, I checked the schedule details on the TSM server console;

q sched domainname schedulename f=d

The schedule was referencing an object on the node to be backed up. When I verified the path and filename discovered a typo.

Using the update schedule command I fixed the path;

update sched domainname schedulename objects='"c:\Program Files\Tivoli\TSM\Backup.cmd'"

Note: In order to get quotes around the path you need to enclose the quotes on the front/end with a single quote. ie. singlequote doublequote string doublequote singlequote

Friday, May 20, 2016

Deploy EPOPS agent to all Windows servers using PSEXEC

Problem: VMware doesn't really give you an easy way to deploy out it's EPOPS agents. Not for free anyways.

Solution: Here's a method that worked really well for me. Grab pstools and extract to a folder, c:\temp sounds good. Right-click your CMD prompt and Run As, choose an account that has access to remotely connect to your servers.

Command:
psexec @serverlist.txt -c vRealize-Endpoint-Operations-Management-Agent-x86-64-win-6.2.1-3720494.exe -serverAddress vrops.domain.local -securePort 443 -username admin -password yourpass -serverCertificateThumbprint 03:51:F2:... /verysilent /dir="c:\ep-agent"

The serverlist.txt is a list of your servers you want to deploy to.

Modify this with your environment info. The Cert Thumbprint is copied from the admin web gui. It's pretty long so make sure copy the entire Thumbprint and include it in the command.

Psexec will copy the exe to the c:\windows\system folder on the remote system, execute the command then remove the exe file when it's done. Slick!