A valid XSL transform file was not found.

Details
Product: SQL Server Notification Services
Event ID: 7002
Source: NotificationServices
Version: 2.0.9999.9
Message: A valid XSL transform file was not found.
   
Explanation
This error occurs when the XSLT content formatter cannot find a valid XSLT file to use, based on the path and file name supplied in the ADF.

For example, suppose that there is an XsltFormatter definition in the ADF with two arguments: XsltBaseDirectory with the value C:\TransformDirectory, and XsltFileName with the value StockTransform.xls. When the distributor tries to format a notification, it attempts to find the file StockTransform.xsl in one of the following paths, based on the locale and device type of the particular subscription it is trying to format:
C:\TransformDirectory\locale\deviceType
C:\TransformDirectory\locale
C:\TransformDirectory\deviceType
C:\TransformDirectory
You must define locales and device types if you want them. Likely values for locale are fr (French) and ja (Japanese). Likely values for the device type are HttpDeviceType or SMSDeviceType.

If the distributor cannot find StockTransform.xsl in any of these paths, it then logs error 7002. The distributor also logs error 7002 if it does find the transform file but the file is not a valid XSLT file. In this latter case, error 7002 is accompanied by error 7003.

   
User Action
First check the Windows application log to see if error 7002 is accompanied by error 7003. Make sure that both errors refer to the same file by checking the <xslt> element inside both error messages. If the two elements match, then the XSLT file does exist in the appropriate place, but it is not a valid XSLT file. For more information, see the help page for error 7003.

If you do not see a corresponding error 7003 in the Windows application log, then the distributor could not find your XSLT file at all. Open the ADF and find the problematic XsltFormatter definition. If the ADF defines more than one XSLT content formatter, you must identify the particular one that caused the error. To do this, look for the <xslt> element in the error message, and match the information there to one of the XSLT content formatters in the ADF.

After you identify the problematic XsltFormatter definition, check the XsltBaseDirectory and XsltFileName arguments in the ADF. If they are wrong, fix them. If they are correct, then go to the base directory and make sure the XSLT file exists there and / or in the appropriate locale or device type subdirectories.</xslt></xslt>

Related:

Leave a Reply