tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/140-682Cascade CMS: Discussion 2011-06-30T21:09:53Ztag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-05-26T16:23:03Z2011-05-26T16:23:03Z6.8.2<div><p>There could be a number of reason why this is occurring. Could
you attach your latest cascade.log file so that I can see what may
be preventing the startup?</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-05-26T16:40:13Z2011-05-26T16:40:13Z6.8.2<div><p>attached</p></div>steelejtag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-05-26T18:35:19Z2011-05-26T18:35:19Z6.8.2<div><p>It looks as if you're running into a deadlock issue on a table
within your database. Are you using SQL Server by chance? If so,
let's try enabling snapshop isolation.</p>
<p>Here is a link to our SQL Server installation instructions:</p>
<p><a href=
"http://www.hannonhill.com/kb/Database-Config/index.html">http://www.hannonhill.com/kb/Database-Config/index.html</a></p>
<p>Please have your DBA verify that you have enabled snapshot
isolation for the database, and let me know if this problem
persists afterward. A restart of CS will ne needed after applying
this change to the DB as well.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-06-13T14:19:06Z2011-06-13T14:19:06Z6.8.2<div><p>This appears to have resolved the problem in our test system and
the update was successful. We will proceed to our production
server.</p></div>steelejtag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-06-13T17:43:39Z2011-06-13T17:43:39Z6.8.2<div><p>Great, glad we could be of assistance!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-06-30T14:01:15Z2011-06-30T14:01:15Z6.8.2<div><p>Joel, this did the trick. We're in 6.8 in production.
thanks.</p></div>steelejtag:help-archives.hannonhill.com,2010-02-09:Comment/74732152011-06-30T20:44:37Z2011-06-30T20:44:37Z6.8.2<div><p>Glad we could help!</p></div>Joel