Request Time out , when installing ublogsy Latest Release 2.1.0.0
Hi ,
On installing the new version of ublogsy i am getting the request timeout error, i have tried reinstalling using local package too with no success, is it something to do with webconfig time out settings or somethign else,
And if after an hour it is still waiting, would you up the timeout to two, or three hours? I think not.
If this is a one-time thing upon installation of the package then it might be tolerable, but in my opinion, if it takes longer that a few minutes to install then this is at least a terrible user experience and could at a stretch be classified a bug (unless it's uploading a high-def movie as part of it or something and, along with a declaration of 'taking ages to install is expected behaviour of this package', that is clearly stated somewhere)
I only copied and pasted that as an example. Typically any type of Umbraco package install will not take longer than a minute or so. If it takes longer than that then there is clearly some other issue. The point was to let it go long enough to see if there was something else going on.
Mr A, check your umbraco log table.
Are you using a db on localhost, external db or SQL CE?
Just a theory but if it is not a clean umbraco installation you may have some ghost nodes.
If this is the case you can remove them with:
-- DELETE GHOST NODES begin transaction
DELETE FROM umbracoNode WHERE ( id IN ( SELECT umbracoNode_1.id FROM umbracoNode AS umbracoNode_1 CROSS JOIN cmsContent WHERE (umbracoNode_1.nodeObjectType = 'C66BA18E-EAF3-4CFF-8A22-41B16D66A972' ) AND ( umbracoNode_1.id NOT IN ( SELECT nodeId FROM cmsContent AS cmsContent_1 ) ) ) ) commit transaction
Request Time out , when installing ublogsy Latest Release 2.1.0.0
Hi ,
On installing the new version of ublogsy i am getting the request timeout error, i have tried reinstalling using local package too with no success, is it something to do with webconfig time out settings or somethign else,
Try modifying your web.config
<httpRuntime
maxRequestLength="1048576"
executionTimeout="3600"
/>
http://www.websupergoo.com/helpupload50/source/2-tech_notes/3-web.config.htm
Anthony, I don't think setting the timeout to an hour is exactly appropriate - it's treating the symptom and note the disease.
I see this day in, day out with things like WCF services, ASP.NET websites and the like, and it is rarely the right thing to do.
Furthermore, if the OP is in debug mode, then this shouldn't even be necessary as a workaround.
I have changed the runtime , now its just stuck on installing the package , and on the bottomleft of the browser shows waiting for localhost
And if after an hour it is still waiting, would you up the timeout to two, or three hours? I think not.
If this is a one-time thing upon installation of the package then it might be tolerable, but in my opinion, if it takes longer that a few minutes to install then this is at least a terrible user experience and could at a stretch be classified a bug (unless it's uploading a high-def movie as part of it or something and, along with a declaration of 'taking ages to install is expected behaviour of this package', that is clearly stated somewhere)
Grant I agree.
I only copied and pasted that as an example. Typically any type of Umbraco package install will not take longer than a minute or so. If it takes longer than that then there is clearly some other issue. The point was to let it go long enough to see if there was something else going on.
Mr A, check your umbraco log table.
Are you using a db on localhost, external db or SQL CE?
I am facing the same "Request timeout" issue, and dont see that extension of timeout period as a solution.
I am using SQL Express on the same host as the web app.
These are the errors I get in log:
At /umbraco/developer/packages/installer.aspx?installing=businesslogic&dir=.... Error loading actionhandler 'umbEnsureUniqueName': umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteReader ---> System.Threading.ThreadAbortException: Thread was being aborted. at SNIReadSync(SNIConn* , SNIPacket** , Int32 ) at SNINativeMethodWrapper.SNIReadSync(SafeHandle pConn, IntPtr& packet, Int32 timeout) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at System.Data.SqlClient.TdsParserStateObject.ReadByte() 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(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteReader(String commandText, SqlParameter[] parameters) at umbraco.DataLayer.SqlHelper1.ExecuteReader(String commandText, IParameter[] parameters) --- End of inner exception stack trace --- at umbraco.DataLayer.SqlHelper1.ExecuteReader(String commandText, IParameter[] parameters) at umbraco.cms.businesslogic.web.Document.GetChildrenBySearch(Int32 NodeId, String searchString) at umbraco.ActionHandlers.umbEnsureUniqueName.Execute(Document documentObject, IAction action) at umbraco.BusinessLogic.Actions.Action.RunActionHandlers(Document d, IAction action)This looks like a funky db error.
Error loading actionhandler 'umbEnsureUniqueName':
Just a theory but if it is not a clean umbraco installation you may have some ghost nodes.
If this is the case you can remove them with:
-- DELETE GHOST NODES
begin transaction
DELETE FROM umbracoNode
WHERE
(
id IN
(
SELECT umbracoNode_1.id
FROM umbracoNode AS umbracoNode_1 CROSS JOIN cmsContent
WHERE (umbracoNode_1.nodeObjectType = 'C66BA18E-EAF3-4CFF-8A22-41B16D66A972'
)
AND
(
umbracoNode_1.id NOT IN
(
SELECT nodeId
FROM cmsContent AS cmsContent_1
)
)
)
)
commit transaction
Just an update on this issue.
Today I installed uBlogsy and it timed out. I increased the timeout and it took over 30mins to install.
The dev server is in the cloud but is only accessible if I'm VPN'd into the office in London. I am currently physically in Australia.
After taking ages, I decided to use sql server locally. It installed in a matter of seconds. Same files, just different db location.
I have seen this before when using uSiteBuilder. Doctype creation slams the Umbraco API which in turn devestates the sql server.
Basically my issue was that my dev webserver (local host) was not physically close enough to my db. I'm not sure if the VPN also contributed.
is working on a reply...