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', 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 ('000926-000004', '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 10:52:34' WHERE ref_no = '000926-000004'
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 #
	000926-000004

	Product
	Maximizer All Articles

	Category
	How-To Import - Export

	Date Updated
	04/06/2010 12:25 PM

Print Answer

Importing into Maximizer

Question

Maximizer allows you to import address book entries from various databases as long as the records can reside in a file format that Maximizer can import. Maximizer can import the following file formats:

Comma-delimited
Tab-delimited
Dbase III/III+
Dbase IV

Answer

To import records from another database application, that application must export the records into one of the foregoing formats. Consult the application's user documentation or contact the software manufacturer for information on how to perform an export on the records.

Resolution

To import address book records from an external file:

In Maximizer, load the database into which you wish to import.

Choose File > Import > Address Book Entries.

If this menu is disabled then you do not have Transfer and Import/export rights. Contact your Maximizer Administrator for assistance.

In the Import Address Book Entries screen (see below), click Browse and browse to the file you wish to import. Highlight the file and click Open or OK.

In the Type of import frame, verify that Companies/Individuals is selected. In the Error handling frame, verify that Write errors to file is selected. Click OK.

Refer to the image below. In the Available Maximizer fields screen, highlight a field and click Add to match the middle panel with the right-hand panel. Continue until all fields are accounted for, then click Import.

Maximizer will import the records. After the import is complete, it will display a message stating how many were imported. Click OK.

Maximizer has successfully imported records from the import file.

Applies To

Maximizer CRM 10.x
Maximizer Enterprise 9.5
Maximizer 9
Maximizer Enterprise 9
Maximizer 8
Maximizer Enterprise 8

Changes made
- Image inserted (10/03/03)
- Reallocation (9/10/04)
- Updated the applicable versions (6/04/10)

How well did this answer your question?


	Back to Search Results