• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 762
  • Last Modified:

Windows 2003 Terminal Services server crash and reboot

Hi,

Twice this week (Monday afternoon at busy time, and 5pm Friday at quiet time of day) our terminal services server rebooted for no apparent reason.

The following were found in event log (on Monday, this was after the reboot. Today they appeared before the crash):
lserver (1264) The database engine is initiating recovery steps.
lserver (1264) The database engine has successfully completed recovery steps.
lserver (1264) The database engine has begun replaying logfile C:\WINDOWS\System32\LServer\edb.log.

Other than those, there's quite a few of these:
Windows cannot access the file gpt.ini for GPO... (rest not copied here)

I cannot see any obvious cause.

Can anyone advise, and/or provide resolution?
0
guernseypost
Asked:
guernseypost
  • 3
  • 2
  • 2
2 Solutions
 
zelron22Commented:
Any other error messages?  Any in the system event log?  
0
 
Hypercat (Deb)Commented:
Normally, the edb.log file is an Exchange server transaction log file.  Are you trying to run Exchange server and terminal services on the same machine?  This is definitely NOT a good idea!
0
 
zelron22Commented:
Hypercat, I believe in this case the .edb is the licensing database...there are many different uses for edb databases.

Is your server up to date with patches?  ARe you running the licensing server on the same server as your TS?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Hypercat (Deb)Commented:
zelron22 - I think you're right, I thought of that after I submitted my post...
0
 
guernseypostAuthor Commented:
Checked the patch situation after posting the question - we didn't even have SP2! Remedied that situation Friday evening. Will monitor over the next few days.

Yes, the licence server is on the ts server.
0
 
guernseypostAuthor Commented:
Happened again last Monday (6th April). MS support gave us a hotfix, which was applied that evening.
Am monitoring at the moment.
0
 
guernseypostAuthor Commented:
So far so good with that hotfix. Thanks for your help and suggestions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now