space space space
 
 

QuoteAdvantage Knowledge Base

1. Displaying Detailed Error Messages

   1. How to enable detailed error messages in Microsoft CRM

   2. How to enable detailed error messages in QuoteAdvantage

   3. How to display the QuoteAdvantage Support page



2. Errors Starting Microsoft CRM

   1. Microsoft CRM displays an error message after logging in.



3. Errors Loading the QuoteAdvantage Page

   1. The request failed with HTTP status 400: Bad Request.

   2. The underlying connection was closed: The remote name could not be resolved.

   3. Error: Could not find file "c:\inetpub\wwwroot\QuoteAdvantage\bin\CategoryList.xml"

   4 The QuoteAdvantage icon is not displayed on the Quote navigation bar



4. Customization issues

   1. The 'ABCDEF' start tag on line 'X' doesn't match the end tag of 'XYZ' in file 'file:///c:/inetpub/wwwroot/ QuoteAdvantage/bin/CategoryList.xml'. Line J, position K.

   2. The product with ConfigID = ABCDEF could not be loaded

   3. Error in CategoryList.xml. A categoryId value was not found for the 'Category X' category.

 


Section 1 - Displaying Detailed Error Messages

1.1 - How to enable detailed error messages in Microsoft CRM

The first step to resolving a deployment issue is to enable Microsoft CRM to display useful error messages. Normally, detailed error messages are disabled for security reasons. In many cases, an error can occur and no warnings will be displayed to the user. To enable error messages, perform the following steps:

    1. Using Windows Explorer, navigate to the \inetpub\wwwroot\folder
2. Open the web.config file in Notepad or your favorite XML code editor.
3. Find the <appSettings> section near the top of the file.
4. In the <appSettings> section, find the <add key="”DevErrors”"> entry.
5. Set the value for DevErrors to “On”.
6. Close and re-open Microsoft CRM in the web browser. Re-test the area where you suspect a problem was occurring. A detailed error message should be displayed.


1.2 - How to enable detailed error messages in QuoteAdvantage

If a runtime error occurs on a QuoteAdvantage screen, then the error message is controlled by a setting that is separate from Microsoft CRM. To enable error messages in QuoteAdvantage, perform the following steps:

    1. Using Windows Explorer, navigate to the \inetpub\wwwroot\QuoteAdvantage folder
2. Open the web.config file in Notepad or your favorite XML code editor. 3. Find the <appSettings> section near the top of the file.
4. Locate the <customErrors> section.
5. Set the value for “mode” to “Off”. This will enable verbose error messages to be displayed.
6. Close and re-open Microsoft CRM in the web browser. Re-test the area where you suspect a problem was occurring. A detailed error message should be displayed.
7. After the issue has been corrected, be sure to return this setting to “On” in order to minimize the amount of error information that is displayed for end-users.


1.3 - How to display the QuoteAdvantage Support page

The Support page provides information about the currently installed version of the software and the license key that is being used. You can access the Support page from a web browser by going to the following URL on your server: http://myserver/QuoteAdvantage/Support.aspx

This URL is only accessible by explicitly typing its address. A direct link is not provided in the QuoteAdvantage user interface.




Section 2 - Errors Starting Microsoft CRM

2.1 - Microsoft CRM displays an error message after logging in.
An error has occurred. For more information, contact your system administrator. – Try Again


This type of error message will be displayed by Microsoft CRM if a serious error occurs as the application initializes. For additional detail, you will need Administrative privileges. Open the Event Viewer by pressing Start – All Programs – Administrative Tools – Event Viewer. In the “Application” section, look for errors that were generated by Microsoft CRM. You may find useful information here, but in many cases, it will be limited to stack trace information that is only valuable to Microsoft support personnel.

The most common source of this type of failure as a result of installing QuoteAdvantage is an error in the isv.config file or in the web.config file. Carefully review the changes that were described in Chapter 8 of the Installation Guide. A common problem is to mistype something in the XML. If a closing tag is missing or incorrectly spelled, this type of error message will probably be displayed. Proof your XML changes carefully. In many cases, the error may be difficult to see. If you can’t find the source of the problem, try reverting back to the original isv.config and web.config files before you made any changes.

If you experience problems saving changes to these configuration files, it may be because Microsoft CRM has locked them. To resolve this, restart IIS, and the locks should be released.

Remember, changes to the isv.config file are not actually applied until IIS has been restarted.




Section 3 - Errors Loading the QuoteAdvantage Page

3.1 - The request failed with HTTP status 400: Bad Request. [ProductConfigException: Unable to connect to Microsoft CRM. Url: http://.... Server: my_server UserName: CRM\Administrator]

If the QuoteAdvantage tab fails to load in Microsoft CRM, then the most likely problem is a mistake in the web.config file in the QuoteAdvantageWeb folder. Inspect this file to make sure that the QuoteAdvantage.CrmSdk.CrmService setting is correct. Refer to Chapter 10 of the Installation Guide for additional information.


3.2 - The underlying connection was closed: The remote name could not be resolved. [ProductConfigException: Unable to connect to Microsoft CRM. Url: http://.... Server: my_server UserName: CRM\Administrator]

If the QuoteAdvantage tab fails to load in Microsoft CRM, then the most likely problem is a mistake in the web.config file in the QuoteAdvantageWeb folder. Inspect this file to make sure that the QuoteAdvantage.CrmSdk.CrmService setting is correct.Refer to Chapter 10 of the Installation Guide for additional information.


3.3 - Error: Could not find file "c:\inetpub\wwwroot\QuoteAdvantage\bin\CategoryList.xml"

This problem is caused when the CategoryList.xml file was not found. Refer to Chapter 9 of the Installation Guide for information about how to create this file.


3.4 - The QuoteAdvantage icon is not displayed on the Quote navigation bar

Inspect the isv.config file in the _Resources folder. The <NavBarItem> entry is probably incorrect. Also, verify that the QuoteAdvantage.gif file is available in the QuoteAdvantage folder. See Chapter 7 of the Installation Guide for additional information.



Section 4 - Customization Issues

4.1 - The 'ABCDEF' start tag on line 'X' doesn't match the end tag of 'XYZ' in file 'file:///c:/inetpub/wwwroot/QuoteAdvantage/bin/CategoryList.xml'. Line J, position K.

This type of error is usually caused by mistyping something in one of the XML files. Carefully inspect the XML file on the line number that was mentioned in the error message. All of your starting XML tags must be precisely matched with a corresponding end tag. For example, a <Category> entry must be ended with a </Category> entry. If the start and end tags are not exactly symmetrical, then error messages will be displayed.


4.2 - The product with ConfigID = ABCDEF could not be loaded

A configId value was not specified correctly in either the Microsoft CRM database or the Parent Product’s rules.xml file. First, inspect the XML file where the rule was loaded. Make sure the configId value is spelled correctly everywhere that it is used. If it seems to be correct, open the Product that uses this configId with the Microsoft CRM product catalog. The configId that is displayed in the catalog should match the configId that is used in the rule files. Refer to Chapter 3 of the Users Guide for additional information about how to specify configID values.


4.3 - Error in CategoryList.xml. A categoryId value was not found for the 'Category X' category.

In the CategoryList.xml file, each <Category> entry should include a “categoryId” value. If this value is missing, then you will see errors when a user clicks on the category entry in the tree list. Carefully inspect your XML file to find the missing entry. Refer to Chapter 3 of the Users Guide for additional detail.
 
     

Home  |  Products  |  Open Source  |  Support  |  Contact Us
©2005-2008 Callisto Systems, Inc.Privacy PolicyLegal