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-08 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-08 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 ('080916-000035', '2010-09-08 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-08 18:33:55' WHERE ref_no = '080916-000035'
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 #
	080916-000035

	Product
	MaxExchange MaxExchange Server

	Category
	Patches-Downloads

	Date Updated
	09/16/2008 08:59 AM

Print Answer

Installing MaxExchange 10 SR1 on a Network Domain Controller is Now Supported

Question

Installing MaxExchange on a Network Domain Controller is Now Supported

Problem

In the Release Notes of MaxExchange Synchronization Server version 10 Service Release 1 � Series 1833, a section was added called �Installing MaxExchange on a Domain Controller� under which it was claimed that: �Installing MaxExchange on a network domain controller is not supported.�

Cause

There were no known issues with MaxExchange running on a network domain controller at the time of release of MaxExchange Synchronization Server version 10 Service Release 1. However, it was felt that there had not been enough testing in such an environment to claim support for it.

Answer

Solution

The appropriate level of testing has since been completed of the scenario of running MaxExchange Synchronization Server version 10 Service Release 1 on a network domain controller. This means it will now be supported.

Those that wish to install MaxExchange Synchronization Server version 10 Service Release 1 on a network domain controller should be aware of the following:

Particularly in larger organizations, due to Corporate Policies in place on the network domain controller, connection to a MaxExchange Server may not be available. Changes to these policies may or may not be allowed by the organization, which may force installing MaxExchange on another computer. (Issues that have been seen because of such restrictive policies include but are not limited to Remotes not being able to connect to the Server, the connection working but timing out, the application not launching, etc.)
Servers running Windows Small Business Server, as well as being network domain controllers are often also used as a Microsoft Exchange Server. If this is the case, then you will not be able to use the email mode of transport for MaxExchange on that machine. This is because Microsoft doesn�t support installing a MAPI client onto a Microsoft Exchange Server. See the following Microsoft article for details:

http://support.microsoft.com/default.aspx?scid=kb;en-us;266418
Depending on the transport method used, it may be necessary to open certain ports in the firewall of the network domain controller. Depending on how the network is set up, this could be a potential security risk. If the network were configured in such a way that this is a risk, it would be wiser to setup a VPN server and have your Remotes connect through that first which will avoid the security risk. Please see the Microsoft website (http://www.microsoft.com) for details on how to setup a VPN and how to connect to it once it is configured.

As long as the above is followed, MaxExchange Synchronization Server version 10 Service Release 1 will run on a domain controller.

�

How well did this answer your question?


	Back to Search Results