Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Proget Error
-
Hey guys we get this two errors today in the morning can you tell us what mean the error msg?
Application: ProGet.Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Data.SqlClient.SqlException Stack: at Inedo.TimedExecuterBase.ExecuteMethodHost(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers() ---------- Faulting application name: ProGet.Service.exe, version: 3.0.0.2, time stamp: 0x53236ab3 Faulting module name: KERNELBASE.dll, version: 6.3.9600.16656, time stamp: 0x5318237f Exception code: 0xe0434352 Fault offset: 0x00000000000043c8 Faulting process id: 0xf40 Faulting application start time: 0x01cf55a208ca320c Faulting application path: C:\Program Files\ProGet\Service\ProGet.Service.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 5f908023-c383-11e3-80be-00155d015703 Faulting package full name: Faulting package-relative application ID
Proget is hosted on Windows 2012R2 in IIS 8.5 .
Product: ProGet
Version: 3.0.0
-
This usually means that the connection to the SQL Server instance was lost. If SQL Server is on a different server, was that server rebooted for updates perhaps?
-
we checked the db server and server db server was online all the time.
I checked the Windows EventLog today and found 100 and more error msg like this:
`Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/14/2014 5:22:10 PM
Event time (UTC): 4/14/2014 3:22:10 PM
Event ID: b4c2513f2d09490f8fea20543dc7f0d7
Event sequence: 37
Event occurrence: 36
Event detail code: 0Application information:
Application domain: /LM/W3SVC/2/ROOT-1-130419415313981407
Trust level: Full
Application Virtual Path: /
Application Path: C:\Program Files\ProGet\WebApp\
Machine name: TESTNGETFRA01Process information:
Process ID: 5720
Process name: w3wp.exe
Account name: INTERN\SA_ProGetException information:
Exception type: SqlException
Exception message: 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, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TrySetMetaData(_SqlMetaDataSet metaData, Boolean moreInfo) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() 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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource
1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
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.ExecuteDbDataReader(CommandBehavior behavior)
at Inedo.Data.DatabaseFactory.Inedo.Data.IDatabaseExecuter.ExecuteDataSet(String storedProcName, String[] tableNames, DbParameter[] parameters)
at Inedo.ProGet.Data.StoredProcedures.Dashboards_GetDashboardInfo.Execute()
at Inedo.ProGet.WebApplication.Pages.RootPage.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)The wait operation timed out
Request information:
Request URL: https://nuget.test-dev.net:443/
Request path: /
User host address: 192.168.xxx.xxx
User: admintl
Is authenticated: True
Authentication Type:
Thread account name: INTERN\SA_ProGetThread information:
Thread ID: 32
Thread account name: INTERN\SA_ProGet
Is impersonating: False
Stack trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TrySetMetaData(_SqlMetaDataSet metaData, Boolean moreInfo) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() 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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource
1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
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.ExecuteDbDataReader(CommandBehavior behavior)
at Inedo.Data.DatabaseFactory.Inedo.Data.IDatabaseExecuter.ExecuteDataSet(String storedProcName, String[] tableNames, DbParameter[] parameters)
at Inedo.ProGet.Data.StoredProcedures.Dashboards_GetDashboardInfo.Execute()
at Inedo.ProGet.WebApplication.Pages.RootPage.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)Custom event details: `
-
Hi guy
we found out that something on Proget Startpage needs more than 30sec to load.
Pls check this and make a option to disable the- "Latest News from Inedo",
- "Proget Help & Support",
- "Local feeds" and
- "Lastest Local Packages"´
ProGet Loading time:
-
Thanks for the info. It seems that our RSS feed was returning far more data than it was supposed to, and it also is not being cached client-side as much as it is supposed to be. We've just updated inedo.com to return much less data - this should greatly reduce the loading time you see. We'll fix the caching issue in the next ProGet release.
-
Hi guys,
we updated ProGet to version 3.0.2 and the problem with the Timeouts still there.
pls fix it or you have any workaround for us?
-
This is slightly odd. Can you try running the query
EXEC [Dashboards_GetDashboardInfo] 10
against the ProGet database and see how long it takes on your installation? This query should be instant and should virtually never time out.
There must be something else going on here. Are you certain that the connection strings to ProGet's SQL database are pointing at the database server, named instance, and database name that you believe it to be?
-
Hi your statment runs 5min it is very slow.
We changed the stored procedures "Dashboards_GetDashboardInfo"
This query:
`SELECT * FROM [Packages_Extended] WHERE [Project_Indicator] = 'N'
ORDER BY [Published_Date] DESC`
to this:
`SELECT TOP 0 * FROM [Packages_Extended] WHERE [Project_Indicator] = 'N'
ORDER BY [Published_Date] DESC`
now we get now no timeouts and no errors
-
Thank you for the analysis. Curious, how many packages do you have total across all feeds, and what sort of database server is this running on (version, hardware or VM specs)? Even though the publish date is unindexed (though it will be in the next version ;)), it seems odd that it would take 5 minutes unless there are hundreds of thousands of packages or more.
-
We have 6328 packages in all feeds.
On the database server runs an windows 2008 with an MSSQL Server 2008.
-
For completeness, v3.0.3 was just published which adds an index to Publish_Date and the dashboard query now returns virtually instantly tested against 100,000+ packages in the database.