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 ('100414-000007', '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 11:23:11' WHERE ref_no = '100414-000007'
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
	Answers

	Help
	Help


	Search Results


	Related Answers

Product

Category

Search Text (optional)

Search Tips?

Search by		Sort by

	Reference #
	100414-000007

	Product
	Maximizer Maximizer CRM 11

	Category
	Compatibility

	Date Updated
	04/15/2010 03:06 PM

Print Answer

Fax Activities in Automated Campaigns Fail when Using Microsoft Fax

Question

Fax Activities in Automated Campaigns Fail when Using Microsoft Fax

Problem

This issue affects automated campaigns with fax activities using Microsoft Fax where special dialing rules are required. The automated campaign fails to send the fax activities.

Reason

Maximizer does not follow system dialing rules for faxing.

Answer

Solution

Add a setting to the MaConfig table to set a fax number prefix for fax activities in automated campaigns.

To set the fax number prefix in the MaConfig table:

Run the following query on the MaConfig database on the SQL server.

INSERT INTO MaConfig (eFile, eSection, eKey, eValue)
VALUES ('', 'Global Settings', 'FAX_NUMBER-PREFIX', '[prefix]')

Replace [prefix] with the prefix required for the fax number.

Versions Affected

Maximizer CRM 11, Enterprise Edition only

How well did this answer your question?


	Back to Search Results