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-000010', '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:53:08' WHERE ref_no = '100414-000010'
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 #  
100414-000010
  Product  
Maximizer
  Maximizer CRM 11
  Category  
Configuration
  Date Updated  
04/30/2010 09:21 AM

 Print  Print Answer
  
  Installing Maximizer CRM Group Edition in a Demilitarized Zone Infrastructure
  Question
 

Installing Maximizer CRM Group Edition in a Demilitarized Zone Infrastructure

Question

How do I install Maximizer CRM Group Edition including the components to run Maximizer Web Access in an infrastructure that includes a demilitarized zone?

  Answer
 

Solution

To install Maximizer CRM Group Edition in a demilitarized zone infrastructure:

  1. Install only Maximizer Server on a computer inside the private network.

    For more information, see Installing Maximizer CRM Server.

  2. Install only Maximizer Components for IIS on a computer outside the firewall in the demilitarized zone.

    When you are prompted to enter the name of the SQL Server, enter the name of the computer where you installed Maximizer Server.

    For more information, see Installing Maximizer Components for Microsoft IIS.

  3. On the Maximizer server computer, configure the SQL Server Express database engine to use port 1433.

    1. Open SQL Server Configuration Manager.
    2. In the left pane, expand SQL Server Network Configuration.
    3. Select Protocols for MAXIMIZER, and select TCP/IP protocol.
    4. Right-click, and select Properties.
      The TCP/IP Properties dialog box opens.
    5. On the Protocol tab, set Listen All to No.
    6. Select the IP Addresses tab.
      The dialog box displays a number of IP addresses in the format IP1, IP2, up to IPAll. One of these IP addresses is for the loopback adapter, 127.0.0.1. Additional addresses appear for each IP address on the computer. You may need to expand each address to identify the address you want to configure.
    7. Locate and expand the IP address you want to configure, and make the following changes:
      • If the TCP Dynamic Ports field is set to 0, delete the 0.
        The 0 value indicates that the database engine is listening on dynamic ports.
      • In the TCP Port field, enter 1433.
      • Set the Enabled field to Yes.
    8. Click OK.
    9. In the left pane, select SQL Server Services.
    10. Select the SQL Server (MAXIMIZER) service, right-click and select Restart to restart the service.
  4. Create an exception in the firewall to give the computer running the Maximizer IIS Components access to the Maximizer server database through port 1433.

    Depending on its configuration, you may need to perform additional steps to configure the firewall:

    • Open port 1434 to expose the SQL Server Browser service.
    • Create an exception for sqlservr.exe to allow the MAXIMIZER instance of SQL Server access through the firewall.

    For more information on any of these steps, follow instructions provided by the manufacturer of your firewall.

  5. Copy the MxzDir.cfg file from the SvrShare folder on the Maximizer server computer to any location on the IIS server computer.

    By default, the SvrShare folder is located in the following location: C:\Documents and Settings\All Users\Application Data\Maximizer\SvrShare.

  6. On the computer running Maximizer Components for IIS, edit the registry to point to the local copy of the MxzDir.cfg file.

    Warning Be extremely careful when updating the Windows Registry. Incorrectly modifying registry keys can lead to catastrophic program and system failures. If you are unsure about any of the following steps, please consult an experienced Windows user or a system administrator.

    1. Click Start > Run.
    2. Type regedit and click OK.
    3. Expand the HKLM\SOF\Maximizer Software\Maximizer\Common\Sys registry key.
    4. In the CENTRAL_WORKSPACES_PATH and WORKSPACES_PATH registry keys, enter the full path to the local copy of the MxzDir.cfg file.

Note: Whenever changes are made that affect the MxzDir.cfg file on the server computer, repeat Step 5 to update the copy of the file on the IIS computer.

The MxzDir.cfg file is affected by changes to Address Book configuration, licensing, email service and dashboard settings, MaxExchange server settings, as well as Microsoft IIS, Live Update, and Maximizer server addresses.

Versions Affected

  • Maximizer CRM 11 Group Edition
 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results