- Community Home
- >
- Storage
- >
- Legacy
- >
- Storage Software
- >
- sql.preg timeout period expired
Storage Software
1753971
Members
8487
Online
108811
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
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
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
10-22-2009 11:11 AM
10-22-2009 11:11 AM
sql.preg timeout period expired
Receiving period emails from various VSQLs. Nothing appears to be harmed so I've been ignoring them. Should I increase a timeout seeting somewhere? If so, where?
message: Volume C:\SQLMounts\PRODDATA\OTGPRD\Data\sql.preg from instance OTGPRD failed with error This operation returned because the timeout period expired.
message: Volume C:\SQLMounts\PRODDATA\OTGPRD\Data\sql.preg from instance OTGPRD failed with error This operation returned because the timeout period expired.
- Tags:
- SQL
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2009 04:51 AM
10-24-2009 04:51 AM
Re: sql.preg timeout period expired
SQL.preg contains the registry keys that are copied from live SQL node to backup SQL node during a failover or rehost. The message indicates either 1) a network issue or 2) a storage issue. You can adjust the timeout value also (Right click OTGPRD in Application tab, Probe configuration.
Probe Configuration:
Timeout (seconds): 45 seconds is the max we should consider.
1) Network -
Make certain you have current NIC drivers, esp if using Broadcom.
Verify all the network config stuff - Public has discourage admin. Admin network has admin traffic configured.
Verify Flow control, RSS and all offloads are disbled on ALL nics;
Public NIC should be first followed by the admin network in the Network Bindings
Admin Network Interface Card (NIC)
* Disable NetBIOS over = TCP/IP
* Remove the checkmark for Client for Microsoft and File and Print sharing.
* IP properties - Advanced - DNS tab - Uncheck â Register this connectionâ s addresses in DNS.â This is checked by default
* Do not list any DNS servers for the private NICs.
* Remove File and Print Sharing for Microsoft Networks
* Leave the DNS and WINS fields blank on the private interfaces.
2) Storage - verify not using unsupported storport driver and current or 1 revision back miniport driver. All storage VAR require minimum of this driver version.
http://support.microsoft.com/kb/932755
Probe Configuration:
Timeout (seconds): 45 seconds is the max we should consider.
1) Network -
Make certain you have current NIC drivers, esp if using Broadcom.
Verify all the network config stuff - Public has discourage admin. Admin network has admin traffic configured.
Verify Flow control, RSS and all offloads are disbled on ALL nics;
Public NIC should be first followed by the admin network in the Network Bindings
Admin Network Interface Card (NIC)
* Disable NetBIOS over = TCP/IP
* Remove the checkmark for Client for Microsoft and File and Print sharing.
* IP properties - Advanced - DNS tab - Uncheck â Register this connectionâ s addresses in DNS.â This is checked by default
* Do not list any DNS servers for the private NICs.
* Remove File and Print Sharing for Microsoft Networks
* Leave the DNS and WINS fields blank on the private interfaces.
2) Storage - verify not using unsupported storport driver and current or 1 revision back miniport driver. All storage VAR require minimum of this driver version.
http://support.microsoft.com/kb/932755
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