| Event Information | According to Microsoft :
CAUSE:
This error occurs when an XSLT file specified in the ADF, for use by the XSLT content formatter, is not valid. When a notification is ready to be distributed, the distributor attempts to format that notification using the content formatter specified in the ADF for that notification class. If the content formatter is specified using XsltFormatter then the distributor calls the XsltFormatter class to format the notification. The XsltFormatter class, in turn, attempts to open and use the XSLT file specified in the arguments passed to it. Specifically, the distributor uses the .NET Framework XslTransform.Load(string) method. If a problem is encountered while loading the XSLT file, then the distributor logs error 7003. In the event log entry, the XSLT Transform File information specifies the path to the faulty XSLT file. The entry also includes Description information that describes the problem.
RESOLUTION:
Use the event log entry to identify the invalid XSLT file and help determine why the XSLT file is invalid. If the description information does not provide enough information, investigate the XSLT file more closely. Here are two ways to determine what is wrong with the XSLT file: 1) Write a simple C# program that loads the XSLT file using the Load(string) method in the XslTransform class of the .NET Framework. 2) Attempt to format a raw notification using the XSLT file. To do this you must first use Notification Services to generate a raw XML notification. To generate a raw notification, temporarily replace your XSLT file with a new file called Noop.xslt that has the following code:
Now change the ADF to use this XSLT file instead of the faulty one, and run your NS$ service. This transform file passes the entire raw notification through unchanged. When you run your notification service using this XSLT file, you get an unformatted notification. Now try to use your original XSLT file to format that notification."
|
