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 ('080226-000047', '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:15:45' WHERE ref_no = '080226-000047'
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 #  
080226-000047
  Product  
Maximizer
  Maximizer CRM 10
  Category  
Installation
  Install
  Date Updated  
04/07/2010 05:00 PM

 Print  Print Answer 		  
  Entry Point Not Found Error when Starting Maximizer CRM 10
  Question
 

Entry Point Not Found Error when Starting Maximizer CRM 10

Problem

This issue affects Maximizer CRM 10 installations upgraded from Maximizer 9 or older. When Maximizer CRM 10 is run for the first time after the installation, you may encounter one of the following error messages:

  • [Maximizer] Entry Point Error
  • The procedure entry point ... could not be located in the dynamic link library [file]

Reason

Some of the older Maximizer .DLL files were not removed properly from the system during the installation.
  Answer
 

Solution

Rename or delete the old .DLL files.

  1. Click Start > Find > Files or Folders (or Start > Search > For Files or Folders).
  2. Search your entire computer for the following files:
    • maabout.dll
    • madataio.dll
    • madblist.dll
    • mainterface.dll
    • maxdbase.dll
    • maxmisc.dll
    • mxchoose.dll
    • mxgetset.dll
    • mxlib32.dll
    • mxmail97.dll
    • mxzbtr32.dll
    • mxzio.dll
    • mxzstp32.dll
    • scriptdb.dll
    • *.tsf
    • mxchkdig.dll
    • maximizer.mif
    • MaConfig.dll
    • MaAccess.dll
    • MaMaster.dll

Do not delete or rename any files located inside the C:\Program Files\Common Files\Maximizer folder.

Any files listed outside this folder are safe to delete.

(For example: Change Mxmail97.dll to Mxmail97.OLD)

Versions Affected

  • Maximizer CRM 10

At 11/05/2009 10:15 AM we wrote - Added MaMaster.dll to the list.
At 04/07/2010 04:32 PM we wrote - Removed additional information

 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results