- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL380G4 Win2003 Terminal Server
ProLiant Servers (ML,DL,SL)
1753766
Members
5396
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2006 03:34 AM
тАО01-26-2006 03:34 AM
DL380G4 Win2003 Terminal Server
We have a Windows 2003 Terminal Server with 5 x 72Gb Ultra 320 drives connected to Smart Array 6i Controller in RAID level 5 configuration
We have a problem where the entire system stops randomly for 10-15 seconds
Microsoft seem to think the problem lies with the cpqcissm driver but we are using the latest version released by HP
We have a problem where the entire system stops randomly for 10-15 seconds
Microsoft seem to think the problem lies with the cpqcissm driver but we are using the latest version released by HP
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2006 05:59 AM
тАО01-26-2006 05:59 AM
Re: DL380G4 Win2003 Terminal Server
Kevin,
Do you have any errors in event viewer and in HP integrated management log viewer?
Make sure you have last firmware (server BIOS, SmartArray, SCSI disks)
Do you have any errors in event viewer and in HP integrated management log viewer?
Make sure you have last firmware (server BIOS, SmartArray, SCSI disks)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2006 07:55 PM
тАО01-26-2006 07:55 PM
Re: DL380G4 Win2003 Terminal Server
Nothing at all in the Integrated Management Log
Application log shows some application hang errors which we have gone through with microsoft, their experts have taken a complete crash dump and are pointing the cause to a 'locking' issue with cpqcissm.
Email from microsoft contains:
"The pause that you are seeing on the server is due to locks on the registry.
There is a thread that holds a lock to the registry, and it is writing to it. For some reason it├в s not releasing it and hence making other threads wait.
"On further analysis it was found out that the reason for its wait was because of the fact that some of the IRP├в s (Interrupt Request Packet) of cpqcissm is still waiting."
Application log shows some application hang errors which we have gone through with microsoft, their experts have taken a complete crash dump and are pointing the cause to a 'locking' issue with cpqcissm.
Email from microsoft contains:
"The pause that you are seeing on the server is due to locks on the registry.
There is a thread that holds a lock to the registry, and it is writing to it. For some reason it├в s not releasing it and hence making other threads wait.
"On further analysis it was found out that the reason for its wait was because of the fact that some of the IRP├в s (Interrupt Request Packet) of cpqcissm is still waiting."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 09:32 PM
тАО01-27-2006 09:32 PM
Re: DL380G4 Win2003 Terminal Server
You could try installing the uphclean (User Profile Hive Cleanup) service.
This could help a bit.
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
You say you sent a crashdump, what was the BSOD-code? Does the server crash often?
Regards,
Matthijs
This could help a bit.
http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
You say you sent a crashdump, what was the BSOD-code? Does the server crash often?
Regards,
Matthijs
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP