|
|
Dotnetnuke
Started by no-pro at 06-23-2008 8:21 PM. Topic has 6 replies.
 
 
|
|
Sort Posts:
|
|
|
|
06-23-2008, 8:21 PM
|
no-pro
Joined on 06-24-2008
Posts 1
|
SQL Connect timeouts
|
|
|
|
|
Howdy,
First just wanted to say thanks for putting these forums up, good call!
Anyway, my dilemma is I'm continually getting sql connect timeout errors with my DNN installation. The appear as critical errors in the event viewer and continually point to timeout issues. Is there something I can do from my end to alleviate these? On other DNN sites I maintain it usually pointed to resource restrictions at the db level as the culprit, could this be the case here?
Either way, any insight is appreciated, thanks! :D
Oh an here's the error from the event viewer.
AssemblyVersion: 04.05.05 PortalID: 0 PortalName: ******.com UserID: 3 UserName: ****** ActiveTabID: 37 ActiveTabName: Home RawURL: /default.aspx AbsoluteURL: /default.aspx AbsoluteURLReferrer: UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: 65c47e78-7413-4722-9d56-257c427f0ea7 InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Data.SqlClient.SqlConnection.OnError StackTrace: Message:
DotNetNuke.Services.Exceptions.PageLoadException: Timeout expired. The
timeout period elapsed prior to completion of the operation or the
server is not responding. ---> System.Data.SqlClient.SqlException:
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection) at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream,
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.SetMetaData(_SqlMetaDataSet
metaData, Boolean moreInfo) at
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand
cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj) at
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at
System.Data.SqlClient.SqlDataReader.get_MetaData() at
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds,
RunBehavior runBehavior, String resetOptionsString) at
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean
async) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String
method, DbAsyncResult result) at
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String
method) at
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior) at
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection
connection, SqlTransaction transaction, CommandType commandType, String
commandText, SqlParameter[] commandParameters, SqlConnectionOwnership
connectionOwnership) at
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String
connectionString, CommandType commandType, String commandText,
SqlParameter[] commandParameters) at
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String
connectionString, String spName, Object[] parameterValues) at
DotNetNuke.Data.SqlDataProvider.GetSearchItems(Int32 PortalID, Int32
TabID, Int32 ModuleID) at
DotNetNuke.Services.Search.SearchDataStore.GetSearchItems(Int32
PortalID, Int32 TabID, Int32 ModuleID) at
DotNetNuke.Modules.WhatsNew.WhatsNew.BindData() at
DotNetNuke.Modules.WhatsNew.WhatsNew.Page_Load(Object sender, EventArgs
e) at System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace --- Source: Server Name: DEDI451
|
|
|
|
|
Report
|
|
|
|
06-24-2008, 3:55 PM
|
admin
Joined on 08-10-2005
Posts 245
|
|
|
It would be better if you have our support staff to check. They can check your DNN site and the sql server that you are on to make sure it's not cause by high usage from certain customers.
|
|
|
|
|
Report
|
|
|
|
06-26-2008, 10:12 PM
|
deanman
Joined on 04-11-2007
Posts 197
|
|
|
I thought that WebHost4Life monitors the servers 24/7. Well, erare humanum est. :)
I <3 WebHost4Life.com
|
|
|
|
|
Report
|
|
|
|
06-27-2008, 9:00 PM
|
Fred-
Joined on 06-28-2008
Posts 2
|
Re: SQL Connect timeouts
|
|
|
|
|
|
It would seem your not the only one with sql DNN timeout problems...
Fred-
AssemblyVersion: 04.08.03 PortalID: 1 PortalName: Empire-Com Home of Peggy's Vinyl UserID: -1 UserName: ActiveTabID: 54 ActiveTabName: Home RawURL: /Home/tabid/54/Default.aspx AbsoluteURL: /Default.aspx AbsoluteURLReferrer: http://empire-com.com/Home/tabid/54/Default.aspx UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; .NET CLR 3.5.21022) DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: 4607b26e-6d1d-414a-bd2f-794bd5f5d31f InnerException: Unhandled Error: FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Data.ProviderBase.DbConnectionFactory.GetConnection StackTrace: Message: System.Exception: Unhandled Error: ---> DotNetNuke.Services.Exceptions.PageLoadException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Security.Membership.Data.SqlDataProvider.GetRolesByUser(Int32 UserId, Int32 PortalId) at DotNetNuke.Security.Membership.DNNRoleProvider.GetRoleNames(Int32 portalId, Int32 userId) at DotNetNuke.Entities.Users.UserInfo.get_Roles() at DotNetNuke.Entities.Users.UserInfo.IsInRole(String role) at DotNetNuke.Security.PortalSecurity.IsInRole(String role) at DotNetNuke.Common.Globals.IsLayoutMode() at DotNetNuke.UI.Skins.Skin.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) at DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) at System.Web.UI.TemplateControl.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.default_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace --- Source: Server Name: DEDI570
|
|
|
|
|
Report
|
|
|
|
06-28-2008, 9:52 AM
|
deanman
Joined on 04-11-2007
Posts 197
|
|
|
Hi Fred, You should update your DNN application to the latest version in order to fix some security issues.
And yes, you should NEVER post your domain name and the version of your current DNN (or any other) application. Otherwise, you make your site an easy target for hackers.
I <3 WebHost4Life.com
|
|
|
|
|
Report
|
|
|
|
06-30-2008, 10:35 PM
|
admin
Joined on 08-10-2005
Posts 245
|
|
|
We do monitor all of the server. But for sql timeout, it can be caused by DB too large or someone on the server running some heavy query every now and then. Those are hard to catch unless someone reports it.
|
|
|
|
|
Report
|
|
|
|
|
Webhost4life Fo... » Auto Plug-ins » Dotnetnuke » Re: SQL Connect timeouts
|
|
|
|