Windows Server - AppCmd crashing
-
@obsolesce said in Windows Server - AppCmd crashing:
@bbigford said in Windows Server - AppCmd crashing:
@obsolesce said in Windows Server - AppCmd crashing:
What OS?
Server 2012 R2
Is it fully up to date? Did it start happening soon after a patch? Does the fist occurrence of the error line up with any installed patches?
It's fully up to date, but it's actually been happening for a very long time from what I can see. This is a system that was neglected by the previous IT provider so it's hard to say if it was ever healthy.
-
Are all RDS (Broker/Gateway/Web/Session Host) set up on the same server?
If that is the case, make sure Broker/Gateway/Web are set up correctly and have the correct permissions set for the deployment and for the collection(s).
Obvious, but make sure the host is up to date.
Where is the RD License server? Has it been set up and activated correctly and is the Session Host working with it without error?
-
Is there a dump file or just this application that is failing?
-
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
-
@brrabill said in Windows Server - AppCmd crashing:
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
No printers installed... but I had wondered the same thing as I found that on some forums.
-
@dbeato said in Windows Server - AppCmd crashing:
Is there a dump file or just this application that is failing?
I tried using a couple programs that would capture a dump file. Never could get them working. I've disabled some Windows features on RD/CA stuff that were unnecessary, and backups are now completing without error. I'll report back if they keep going well through the weekend.
-
@phlipelder said in Windows Server - AppCmd crashing:
Are all RDS (Broker/Gateway/Web/Session Host) set up on the same server?
If that is the case, make sure Broker/Gateway/Web are set up correctly and have the correct permissions set for the deployment and for the collection(s).
Obvious, but make sure the host is up to date.
Where is the RD License server? Has it been set up and activated correctly and is the Session Host working with it without error?
All the features are on the same server, and it has every feature added (I recently removed some for testing). As far as permissions, I finally saw in the advanced settings where you could specify the local account (Network Service or otherwise), and I am assuming the log file that it writes to is in c:\programdata...\WER as I can see some appcmd.exe output files in there, but I was a little unsure if I understood the permissions piece of that requirement correctly.
-
Is this a physical or virtual setup?
-
-
Also found vssadmin crashing. Found a scheduled task to create a shadow copy, which conflicts with backup software installed on the server. Not sure wtf they have been thinking after cleaning up this server so far. This one is definitely going to be redone before too long.
Backups are officially healthy; completing without error.
-
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
No printers installed... but I had wondered the same thing as I found that on some forums.
It drove me nuts.
Kept rebooting the server in the middle of the day, randomly. It was awful.
-
@brrabill said in Windows Server - AppCmd crashing:
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
No printers installed... but I had wondered the same thing as I found that on some forums.
It drove me nuts.
Kept rebooting the server in the middle of the day, randomly. It was awful.
Are you sure the spooler caused the reboot rather than a faulting driver not being isolated and caused the server to reboot because of a driver issue? I've witnessed print spoolers on servers crash many times and cause the whole list of printers to become unavailable, but that is about the extent of it.
-
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
No printers installed... but I had wondered the same thing as I found that on some forums.
It drove me nuts.
Kept rebooting the server in the middle of the day, randomly. It was awful.
Are you sure the spooler caused the reboot rather than a faulting driver not being isolated and caused the server to reboot because of a driver issue? I've witnessed print spoolers on servers crash many times and cause the whole list of printers to become unavailable, but that is about the extent of it.
Pretty sure it was the driver.
I think it was an older printer that maybe didn't have an updated driver.
-
@brrabill said in Windows Server - AppCmd crashing:
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
@bbigford said in Windows Server - AppCmd crashing:
@brrabill said in Windows Server - AppCmd crashing:
Are there any printers installed on it?
I had server once that kept randomly crashing and it turns out it was a printer driver of all things.
No printers installed... but I had wondered the same thing as I found that on some forums.
It drove me nuts.
Kept rebooting the server in the middle of the day, randomly. It was awful.
Are you sure the spooler caused the reboot rather than a faulting driver not being isolated and caused the server to reboot because of a driver issue? I've witnessed print spoolers on servers crash many times and cause the whole list of printers to become unavailable, but that is about the extent of it.
Pretty sure it was the driver.
I think it was an older printer that maybe didn't have an updated driver.
I could definitely see a problematic driver causing a server to crash. If it isn't isolated, it could certainly cause the spooler to crash as well (but without causing the server to crash).