Hi,
I raised as message earlier in this forum with regards to an error when
preforming a XSLT transform (see bottom of this message).
On further investigation I'm find that some of the XSLT file have an
namespace for encoding i.e.
<xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform'
xmlns:e="http://xxx.co.uk/xxx" xmlns:msxsl='urn:schemas-microsoft-com:xslt'
xmlns:var='urn:var' xmlns:userJScript='urn:userJScript'
exclude-result-prefixes='msxsl var userJScript DateHelper e'
xmlns:DateHelper="urn:extn-obj" version='1.0'>
and the elements are being referenced as such e.g.
<xsl:if test='e:street'><Address1><xsl:value-of
select='e:street/text()'/></Address1></xsl:if>
Could this somehow have an affect on the below message
Previous Message
============
Whilst performing a simple XLST transform, I am receiving a
CryptographicException. No encryption is being used by the program itself.
At present I have found no pattern into reproducing the error, seemingly
random but often.
The stack trace is as follows;
System.Security.Cryptography.CryptographicExceptio n : The parameter is
incorrect.
System.Security.Cryptography.CryptographicExceptio n: The parameter is
incorrect.
at System.Security.Policy.PolicyLevel.GenericResolve( Evidence evidence,
Boolean& allConst)
at System.Security.Policy.PolicyLevel.Resolve(Evidenc e evidence, Int32
count, Char[] serializedEvidence)
at System.Security.PolicyManager.Resolve(Evidence evidence, PermissionSet
request)
at System.Security.SecurityManager.ResolvePolicy(Evid ence evidence)
at System.Xml.Xsl.Compiler.Compile(NavigatorInput input, XmlResolver
xmlResolver, Evidence evidence)
at System.Xml.Xsl.XslTransform.Compile(XPathNavigator stylesheet,
XmlResolver resolver, Evidence evidence)
at System.Xml.Xsl.XslTransform.Load(XPathNavigator stylesheet, XmlResolver
resolver, Evidence evidence)
at System.Xml.Xsl.XslTransform.Load(XmlReader stylesheet, XmlResolver
resolver, Evidence evidence)
Could anyone point out any possible areas where I could investigate, i.e.
Would SSL have an affect, would the XSLT encoding uft-8 instead of uft-16 be
an issue
