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-000002', '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:20:53' WHERE ref_no = '100414-000002'
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-000002

	Product
	MaxMobile

	Category
	Errors Application Behavior

	Date Updated
	04/14/2010 09:49 AM

Print Answer

Adding Large Documents in MaxMobile Fails Without Displaying an Error Message

Question

Adding Large Documents in MaxMobile Fails Without Displaying an Error Message

Problem

This issue affects adding documents in MaxMobile when the documents are larger than the limit set in the web.config file on the MaxMobile Wireless Server but smaller than 4 MB. The document is not added, but an error message is not displayed to communicate the failure.

Reason

MaxMobile does not communicate the failure to add the document when it's due to the user-set limit instead of the 4 MB limit. Note that 4 MB is the largest file size allowed in MaxMobile, regardless of the limit specified in the web.config file.

Answer

Solution

There is no solution to this issue at this time.

Versions Affected

MaxMobile 11

How well did this answer your question?


	Back to Search Results