Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel CRM Desktop for Microsoft Outlook Administration Guide > Customizing Siebel CRM Desktop > Troubleshooting Problems That Occur When You Customize Siebel CRM DesktopTo resolve a problem that occurs when you customize Siebel CRM Desktop, look for it in the list of symptoms or error messages in Table 19.
Debugging in Siebel CRM DesktopIn order to debug customized script in Siebel CRM Desktop, you must have a third-party debugging tool, such as the Microsoft Just-In-Time Debugger provided by Microsoft Visual Studio. For more information about Visual Studio and the Just-In-Time Debugger, see the documentation at the Microsoft TechNet Web site. You can enable the Microsoft Just-In-Time Debugger by setting the following Windows Registry key: [HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings] "JITDebug"=dword:00000001 After setting the Windows Registry key, you must restart Microsoft Outlook. If a script error is encountered after the debugger is enabled, the user will be prompted to activate the debugger. You can force the debugger to be invoked by adding "debugger" at the desired location in the custom script and republishing the metadata package. NOTE: Oracle does not recommend enabling the Just-in Time debugger in production environments. The JIT debugger is only intended for use in development environments. |
![]() ![]() |
Siebel CRM Desktop for Microsoft Outlook Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |