I had SolidCP 1.2.1 working on my local machine for a while. Then suddenly yesterday I started getting a “HTTP Error 503. The service is unavailable.” error. I tried to no avail a whole number of ways to fix it. Finally, I decided to uninstall and delete everything and reinstall with the latest version (v1.4.1) on my Windows 7 Machine. Installation was successful after a few failed attempts. I go to access the site, same error. I am at a complete loss…
The Event Viewer has three items:
- WARNING (5021): The identity of application pool SolidCP Server Pool 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 (5057): Application pool SolidCP Server Pool 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 (5059): Application pool SolidCP Server Pool has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
I checked the SolidCP accounts (Portal, Server, and Enterprise) and they appear to be defined correctly. I also check Local Policies and made sure that IIS_IUSRS was listed in “Log on as batch job”. I don’t know what else to try, and I have no clue why it worked last week and yesterday just decided to stop working.
Does anyone have any clues?
Ok, so I have resolved my problem. For anyone else having the same issue, I am adding this to record my solution. When I have a problem to solve, I am like a dog with a bone, and I will not let it go. So I kept digging…
In the Event Viewer, on the 1st of the three errors (WARNING: 5021), I noticed in the “Details” tab there some more information, specifically the “Binary Data”, which shows a code “80070700”. So I searched for this code as it related to the WAS Event 5021, and it led me to information about the NetLogon service. So I went and opened my Services window and checked, to find that the NetLogon service was not running and it was set to “Manual”. So I started the service manually and attempted to access my websites, and BINGO, they worked! So now I flipped the NetLogon service properties to “Automatic” so that it starts when Windows starts.
I hope that this helps anyone else that has this issue in the future.
I only wish I figured this out before I erased my previous instance that was all set up, I lost all my settings and now have to re-create or import every Server, IIS Website, Database, etc… Not thrilled about having lost all my data…but live and learn.
Error 503 is generally always a stopped application pool.
The error your seeing is that the application pool stopped due to invalid identity (windows user)
Usually simply checking the user, maybe re-setting password (on windows user and then set it in the app pool) should do the trick.
Maybe you have a password experation policy or password policy which rejected the users password?
Thank you for the speedy response. This is my local machine, which has no expiration policy. And if the Password Policy rejected the password complexity, wouldn’t the install have encountered an error when creating the SolidCP accounts?
Can I change the passwords to the three user accounts (Server, Portal, and Enterprise) manually through Computer Manager in windows to test this theory? Is there anything else I would need to do, or should I change the passwords elsewhere?
I would first check the application pools state in IIS Management.
see if 1 or all 3 are stopped.
whichever is stopped –> check the user used –> reset it’s password in computer management –> then set the password in Application pool advanced settings. (requires setting user + password not just password).
Thats all that needs to be done.
Each AppPool would crash the first time the associated website was accessed. So I went and updated all three account passwords in Windows, reset them in the IIS AppPools with the new passwords, and restarted all the stopped AppPools. Then I tried to access the sites again, same error and the AppPools to associated website stopped.
And you still receive the same event error that application pool identity is not valid?
Correct, the same three items in the Event Viewer, 2 Warnings, and 1 Error.
Not really sure then.. the issue is straight forward that IIS is not accepting the Windows users/ pass defined in application pool.
Normally the setup, aswell as manual reset should give you a simple fix. (for any website not just SolidCP).
You could try a more simple password like: hyCbtadxj53b3Qduqbwc
or try a reboot and see if something changes.
I am at a complete loss as to why the Windows system is continuing to complain that the Identity being used is invalid, especially when the install is fresh, all the information was created new. I have tried everything that I could think of and find online to resolve this to no avail.
At this point, I contacted our Networking Department. While I use SolidCP for my local machine to test and manage my development environments, I wonder if there is some sort of Group Policy that our networking team implemented that is overriding my local system and causing SolidCP not to function. I am not as familiar with policies, so I can only hope they fess up or fix what they changed (if they did). I can’t see any other explanation as to why this worked and then just suddenly stopped.
This error is indeed a valid one, even in 1.4.6 version, uninstalling and re installing did not solve it, create a new app pool, with correct settings ie SolidcpServer with same password and user works, almost looks like microsoft buggers up the app pool name somewhere..
- Views8931 times
- Answers11 answers