November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
I have executed "exec sp_updatestats" but I am still getting the same error.
Hi Priyanta,
Error trace says something not well with SQL so can you please make sure that you are able to access the SQL databases.
Please check the connection string and try to connect the databases.
Hi Priyanta
Did you finally get to the bottom of this. I am restoring a db and setting up a site on my dev machine for the first time and am getting the exact same error.
Regards
Sandeep
Hi Priyanta
Hi
We seem to haev resolved this issue. It looks like this is to do with some uncomited property or some CMS uncomiited transaction when the backup of the DB was being taken.
There are a couple of other threads pointing this out.
We got everyone to commit their cms changes and stoppped all content editors from doing any work while we took the backup of the DB.
The fresh copy of DB does not seem to have the issue.
There is an article to increase the epi timeout which seems to be doing something more than timing out but we were not sure how long it would run so we just got a fresh copy of the CMS DB and restored and it seem to work.
Regards
Sandeep
Can you connect to the database instance using SQL Server Management studio using information in connectionStrings?
HI Quan
Yes I was able to connect to it in mgmt studio without any issue. The application was also able to speak to the DB as when I changed the db name or the username to a non existent value it gave an error that DB does not exist. Comm manager was also loading fine.
As mentioned above taking a fresh backup of the cms seem to have esolved the issue. Would be good to know why it was not working.
Regards
Sandeep
Hi,
I successfully installed Episerver Commerce by following the steps provided in Episerver World website. When I try to launch Episerver CMS, I get Exception "System.ComponentModel.Win32Exception: The wait operation timed out".Kindly, help me to resolve this issue, let me know if more details required. Please find below the complete stack trace of the exception.