Link to home
Start Free TrialLog in
Avatar of chris_nt
chris_ntFlag for United States of America

asked on

2008r2 server boot problem

Greetings,
I have a Microsoft 2008r2 server that is not letting me get to a sign on screen. it boots to a screen that says "the system cannot find the file specified" and there is an ok button.  I can click the "ok"button but the same screen reappears.

History: this is an exchange server, 2010 with sp3. I was having problems with the mobile devices connecting to exchange, in the event viewer logs, it showed issues writing to iis.  Sooo, i rebooted the server and it came up with the error above.

 i can access most of the server remotely, if i rdp to the server, i get the same screen  "the system cannot find the file specified". I can access the c$ drive remotely and browse the hard drive, most of exchange is still working except iis. I was having problems with the mobile devices connecting to exchange, in the event viewer logs, it showed issues writing to iis.  Sooo, i rebooted the server and it came up with the error above. I can access most of exchange from the emc of the new server.

If i look in the event viewer from the bad server, the only thing it shows is repeated errors of "The IIS Admin Service service terminated with the following error:
The system cannot find the file specified."

I can access the event viewer logs from the bad sever from another exchange server i built to replace this during the issue. i can access and manage most services of the bad exchange server with the emc from the new server.

i have ran a chkdsk from boot media, it found no problems.

how can i find the file that is causing this.. or any other help is welcome.

thanks.
Avatar of Don Thomson
Don Thomson
Flag of Canada image

Have you tried booting into safe mode with networking  or last known good configuration?
Does the error msg give any indication as to which file is missing?
Avatar of chris_nt

ASKER

i have tried both, it still boots to the screen with the missing file error with an "ok" button.
Avatar of REIT
REIT

I would advise attempting a Startup Repair from the OEM Media

http://social.technet.microsoft.com/wiki/contents/articles/4162.windows-server-2008-repair-steps-for-no-boot-issues.aspx

Another thing to try, once booted into Windows RE then go to the Command Prompt and try the following command

bootrec /fixboot

Issue may well be Registry related, can you post a picture of the error please just to help us investigate further?
It's not a boot record issue, the system boots, it never gets a logon screen. i have attached the screenshot of the server desktop, and a shot of the system log file from event viewer.  i am remotely connected to the event viewer from a different server.

I believe these errors are related

User generated imageUser generated image
Can you remotely connect to the servers services and then stop the IIS related services?

Also worth trying the startup repair anyway to fix any discrepancies.
the "world wide web publishing service" won't start. are there any other services i can disable related to the iis?

the startup repair is on my list, but last course of action.
ok, the world wide web publishing service was started, i disable it and rebooted. same error
Update, disabling the  world wide web publishing service stopped the errors in the event log. so it looks good now, but still getting same screen on sever after boot. so i guess the errors aren't related.
Try the startup repair to see if it finds anything, also check the services on the server to see which are set Automatic and then see if they're all running correctly.
No backup's I guess. Can you boot into safe mode or safe mode with networking or even safe mode command prompt?
ASKER CERTIFIED SOLUTION
Avatar of chris_nt
chris_nt
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I do want to thank everyone for their help. Some time you just have to fdisk and move on.
Built new server, i hate not knowing what happened, but sometimes you have to fdisk it and move on.