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 ('2012-02-09 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 ('2012-02-09 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 ('070205-000051', '2012-02-09 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 = '2012-02-09 00:26:01' WHERE ref_no = '070205-000051'
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 #  
070205-000051
  Product  
Maximizer
  All Articles
  Category  
Installation
  Install
  Date Updated  
08/14/2008 11:10 AM

 Print  Print Answer 		  
  Pervasive PSQL v9 Service Setup v1.2 utility
  Question
 

This article provides information for Installing Maximizer 9 on Windows Vista. As noted in Knowledge Base article 070205-000056 Maximizer Support for Windows Vista, after the installation of Maximizer 9 on Windows Vista, several extra steps are necessary to work within Vista's User Account Control model.
  Answer
 

The following resolution will guide you through the steps of downloading and running a utility that will configure the Pervasive.SQL Engine to run within the Windows Vista environment.

RESOLUTION

After Maximizer 9 has been installed on Windows Vista perform:
  1. Click the link below and download the Pervasive PSQL Service Setup v1.2 utility. You will have to agree to Download Terms before the download begins:

    Pervasive PSQL Service Setup v1.2 utility

    The file downloaded is named psqlsvcsetup.zip.

  2. Open Windows Explorer and browse to the folder that psqlsvcsetup.zip was downloaded.


  3. Double-click psqlsvcsetup.zip. This will show the content of the zip file.

    Content of compressed file

  4. Double-click the file named psqlsvcsetup.


  5. A message box appears prompting if you wish to extract all files or run the selected. Click the Run button.

    Run selected file

  6. The User Account Control dialog box may appear. If this message box appears then click Allow to continue the installation.


  7. The Setup - Pervasive PSQL Service Utility windows appears. Click Next to proceed.


  8. The Select Service Account option will appear:

    Select Service Account

    If you are currently logged into Windows Vista with Administrative privileges then accept the default value of Local System and click Next. Otherwise, click This Account and enter the Account name and password of a user that has Administrator privileges.

After the installation program has finished, Maximizer 9 may be started without an User Account Control warnings.

If the installation freezes at the end, re-run these steps, but at step 4, rather than double clicking on the psqlsvcsetup file, right click and select Run As Administrator and continue with the rest of the instructions.

MORE INFORMATION

For customers that have used Maximizer on an earlier Windows operating system (e.g. Windows XP, Windows 2000, etc) you may be use to seeing the Pervasive Workgroup Engine in the system tray.

System Tray Icon

After using the Pervasive PSQL Service Utility the Pervasive.SQL Workgroup Engine icon will no longer appear in the system tray. The Pervasive.SQL engine is running, however, the icon will no longer appear.

APPLIES TO

• Maximizer 9
• Maximizer Enterprise 9.5 (Pervasive)


At 05/05/2008 09:51 AM we wrote - Updated Pervasive Tool URL.
 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results