Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 0, 0, 0, 0, 0, 1, 0, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 1, 0, 0, 0, 0, 0, 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:189
In Fcn.:stats_update_faq
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO incident_stats (ref_no, faq_date, faq_hits, interface_id) VALUES ('090813-000000', '2010-09-07 00:00:00', 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:solved.c
Line:68
In Fcn.:solved_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:UPDATE incidents SET solved_count = solved_count + 2, access_time = '2010-09-07 12:14:58' WHERE ref_no = '090813-000000'
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:573
In Fcn.:sql_execute
Called Fcn.:SQLExecute() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Answer
 
Maximizer > Support > Knowledge Base Search New - Searching Tips Disclaimer
 Answers 
   
  Help  
Search Results
Related Answers
Product

   
Category

     
Search Text (optional) Search Tips? 
   
Search by      Sort by

Powered by RightNow Web
  Reference #  
090813-000000
  Product  
Maximizer
  All Articles
  Category  
Errors
  Application Behavior
  Date Updated  
11/16/2009 04:59 PM

 Print  Print Answer 		  
  Upgrading to Workflow Automation Server 7.5 Causes Events to Stop Working
  Question
 

Upgrading Workflow Automation Server to Version 7.5 Causes Events to Stop Working

Problem

After upgrading to Workflow Automation Server 7.5, all events stop working due to SQL statement errors. Upon further examination of the events, the SQL queries have been truncated.
  Answer
 

Solution

This is a known issue with Workflow Automation Server 7.5. To correct the issue, you must upgrade to Workflow Automation Server 7.8. Click here to download Workflow Automation Server 7.8.

Follow the below instructions to recover your queries.

  1. Stop the Workflow Automation Server Windows Service by going to Control Panel > Administrative Tools > Services. Select Workflow Automation Server and click Stop.
  2. End all Workflow Automation Server processes by going to start > run, type taskmgr, and press enter. Find and end any processes starting with KS_.
  3. Revert back to the Workflow Automation Server MS Access if you have already migrated to the Workflow Automation Server SQL Backend and have determined there is data corruption. Click here for instructions on how to revert back to the MS Access back end.
  4. Go to the \program files\Maximizer\Workflow Automation\Bin\ folder and rename the following files:
    • KS_Object_SQL2005_Plus.sql to KS_Object_SQL2005_Plus.OLD
    • KS_Inbox_SQL2005_Plus.sql to KS_Inbox_SQL2005_Plus.OLD
    • KS_Object.sql to KS_Object_SQL2005_Plus.sql
    • KS_Inbox.sql to KS_Inbox_SQL2005_Plus.sql
  5. Migrate your MS Access Database to the SQL Server Backend by going to Start > Programs > Workflow Automation > Migrate Database to SQL Server.
  6. Start the Workflow Automation Server Windows Service by going to Control Panel > Administrative Tools > Services. Select Workflow Automation Server and click Start.
 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results