Troubleshooting

This section provides troubleshooting tips in response to error messages that may appear when running your application.

"Out of memory" dialog in Excel

Reason:

An "Out of Memory" message may be reported if there is insufficient memory available to complete each process, even if it seems that there is sufficient memory available in the system as a whole. In this case, the Dialog Sniffer log file may contain one or both of the following messages:

I_n_s_p_e_c_t_W_i_n_d_o_w_H_o_o_k__i_s__i_n_v_o_k_e_d__i_n_ r_e_s_p_o_n_s_e__t_o_ W_M__I_N_I_T_D_I_A_L_O_G_. Tue Oct 19 12:17:47 2004 E_n_t_e_r_e_d__I_s_A_M_e_s_s_a_g_e_ B_o_x__f_u_n_c_t_i_o_n_._._. T_h_e__o_p_e_n_e_d__w_i_n_d_o_w_'_s__c_l_a_s_s__n_a_m_e__i_s_:__<#32770> T_h_e__o_p_e_n_e_d__w_i_n_d_o_w_'_s__t_e_x_t__i_s_:__<Microsoft Visual Basic> S_t_a_t_i_c__t_e_x_t__i_s_:__<Microsoft Visual Basic> D_e_s_t_r_o_y__p_a_t_t_e_r_n_s__r_e_t_r_i_e_v_e_d_. B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Button> B_u_t_t_o_n__c_o_n_t_a_i_n_s__t_h_i_s__t_e_x_t:__<OK> B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Button> B_u_t_t_o_n__c_o_n_t_a_i_n_s__t_h_i_s__t_e_x_t:__<Help> B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Static> _G_e_t_W_i_n_d_o_w_T_e_x_t__r_e_t_u_r_n_s__t_h_e__e_r_r_o_r_:__ <Cannot create a file when that file already exists. > B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Static> S_t_a_t_i_c__t_e_x_t__i_s_:__<Out of memory>

I_n_s_p_e_c_t_W_i_n_d_o_w_H_o_o_k__i_s__i_n_v_o_k_e_d__i_n_ r_e_s_p_o_n_s_e__t_o_ W_M__I_N_I_T_D_I_A_L_O_G_. Tue Oct 19 12:24:25 2004 E_n_t_e_r_e_d__I_s_A_M_e_s_s_a_g_e_ B_o_x__f_u_n_c_t_i_o_n_._._. T_h_e__o_p_e_n_e_d__w_i_n_d_o_w_'_s__c_l_a_s_s__n_a_m_e__i_s_:__<#32770> T_h_e__o_p_e_n_e_d__w_i_n_d_o_w_'_s__t_e_x_t__i_s_:__ <Microsoft Excel> S_t_a_t_i_c__t_e_x_t__i_s_:__<Microsoft Excel> D_e_s_t_r_o_y__p_a_t_t_e_r_n_s__r_e_t_r_i_e_v_e_d_. B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Button> B_u_t_t_o_n__c_o_n_t_a_i_n_s__t_h_i_s__t_e_x_t:__<OK> B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Static> _G_e_t_W_i_n_d_o_w_T_e_x_t__r_e_t_u_r_n_s__t_h_e__e_r_r_o_r_:__ <Cannot create a file when that file already exists. > B_e_g_i_n__t_o_ _i_n_s_p_e_c_t__t_h_e__w_i_n_d_o_w_. C_l_a_s_s__N_a_m_e_:__<Static> S_t_a_t_i_c__t_e_x_t__i_s_:__<Not enough memory to run Microsoft Excel.>

Solution:

  1. Increase the memory size per process.
  2. Increase the desktop heap value as follows:
    1. From the Start menu, select Run.

    2. Enter regedit to invoke the registry editor.

    3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\.

    4. Double-click the Windows parameter to display the value data.

      For example:

      %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType= Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll= winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

      The desktop heap memory is defined under:

      SharedSection=1024,3072,512

    5. Increase the desktop heap memory.

      The third number ("512" in the example above) is a non-interactive desktop heap. Because the non-interactive desktop heap is mapped into the address space of each and every process, this value should not be set to an arbitrarily high value, but should only be increased sufficiently to allow all the desired applications (such as Excel) to run.

"Unable to Run Macro" dialog in Excel

Reason:

Excel security settings are set too high, disallowing the client macros from running without direct user approval.

Solution:

  1. In Excel, select Tools > Macro > Security.
  2. Click the Security Level tab, and then click Low.

Dialog Sniffer does not log data in %SOAM_HOME%\logs\Sniffer and does not recognize FATAL_PATTERNS and NON_FATAL_PATTERNS

Reason:

Environment variable "SOAM_HOME" is not set to the "DialogSnifferService" process so the sniffer crashes when it creates a log folder or file. (The sniffer calls the ACE method and without "SOAM_HOME", it cannot load ACE.dll.) This behavior has been observed on all Windows platforms.

Solution:

Reboot your machine.

Client hangs when running Excel 2003 on 64-bit compute host

Reason:

Symphony Connector on compute host fails to start Excel process. This behavior has been observed only on Windows 2003 64-bit machines with Microsoft Office 2003 installed while running Symphony connector in 32-bit mode.

Solution:

Install the latest updates for Microsoft Office 2003 on all compute hosts in the cluster.

"This workbook has lost its VBA project ..." message in Excel 2007

Reason:

This error happens if "Visual Basic for Application" was not installed during the installation of MS Office 2007.

Solution:

Update your installation of MS Office:
  1. Close Excel if it is open.
  2. In the Control Panel, choose Add or Remove Programs (or Programs and Features in Windows Vista).
  3. Select Microsoft Office in the list and click Change.
  4. Choose Add or Remove Features.
  5. Select Visual Basic for Applications in the Office Shared Features list and set it to Run from My Computer. Click Continue.
  6. After the installation is finished, you will be able to use the Excel file with its VBA project when you start Excel.