http 503 service unavailable on SharePoint

Error: http 503 service unavailable

Whenever I see this error message on share point site, first I look at status of Application pool . If it is disabled/stopped then I look at windows event-viewer log .

There were couple of warning messages followed by an error message in event viewer .

Warning Message 1: Event ID 5059 : Event Source : WAS

“The identity of application pool SharePoint – mysharepoint.loacl443 is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.”

Warning Message 2: Even ID 5057 : Event Source: WAS
“Application pool SharePoint – mysharepoint.loacl443 has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.”

Error Message :
“Application pool SharePoint – mysharepoint.loacl443 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.”

sharepoint event viewer errors

sharepoint event viewer errors


As a solution ,

I have changed application identity account password and set the same password for that service account from share point management shell .

Set-SPManagedAccount -identity MYDOMAIN\serviceaccount_user -NewPassword (Converto-Securestring “P@ssword” -AsPlainText -Force) -SetNewPassword

sharepoint web application pool settings

sharepoint web application pool settings

Then restarted WAS service from command prompt window ( run as Administrator )
net stop was /y
net start was

net start w3svc

Auto Start Oracle Virtual box VM

——————————-

We can make Oracle virtual-box Vm start automatically when host system reboots.
This can be done by attaching a batch file to scheduletasks in windows environment .

Create a batch file that cotanins like ..

“C:\Program Files\Oracle\VirtualBox\VBoxManage.exe” startvm “Gues-OS-Name”

then create a basic schedule task and choose when system start option .

If you want the VM window to be hidden and not to leave a command prompt window, you can change the batch file like below

“C:\Program Files\Oracle\VirtualBox\VBoxManage.exe” startvm “Gues-OS-Name” –type headless

Change RDP listening port without System Reboot

——————————————

We can easily change remote desktop listening port to some other port than the default 3389.

By default RDP listens on TCP 3389. Once we change this port to some other port , We may need to restart the system to activate the new listening port .

open registry editor and navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Then click on PortNumber and select radio button Decimal which will show value in Decimal. Now enter a desired port number and close the registry editor.
RDP_REG_EDIT

RDP_SERVICES_RESTART
To activate this new port , press Windows+R on keyborad which opens up run window. Type services.msc in run window and press enter now we can restart “Remote Desktop Services” from Sevices list . This will cause any existing remote desktop connection to close and one may need to reopen remotedesktop on new port by entering IPADDRESS:NEWPORT on Remote Desktop client (mstsc)

openfire 3.8.2 and Windows 2008 Activedirectory

 

 

If you have problem with openfire 3.8.2 and activedirectory integration  and clicking on  “TestSettings” displays nothing  then dont think that there is AD connection problem . If  your AD domain is  yourdomain.com  then try to set   just  dc=yourdomain,dc=com  in BaseDN  and  in Administartor DN  put  DomainAdmin@yourdomain.com  .

Still i dont have any clue why openfire 3.8.2 is not displaying any message when i click on TestSettings in Profilesettings page . But it is successfully connecting and fetching user details when i tried to add an admin account from AD in the end of LDAP setup .

Screen Shot 2013-08-07 at 7.05.08 AM

 

 

 

 

MMC could not create the snap-in

I am using 32bit windows 2008  server as  AD domain controller   . After upgrading dot net framework ,all mmc snap-ins were failing to open .

All tools like Server Manager , Event Viewer were showing an error message  like..

MMC could not create the snap-in

MMC could not create the snap-in. The snap-in might not have been installed correctly.

Name: Server Manager

CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb}

 

2

 

Finally I  came to know that it is due to .netframework and it can be fixed by removing .net 3.5  or renaming machine.config  file in  .netframework 2.x  CONFIG directory .

First I ran  sfc /scannow  then renamed C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config to machine.config.old

1

After rebooting the server everything worked fine.

 

You may try to remove .net 3.5 SP1  if you dont want to rename machine.config  in .netframe work 2.x directory .