Cryptic error from SqlXml 3.0 Managed Classes

Hi,
I have a windows service written in C# that is using the SqlXml 3.0 Managed
Classes.
The service has functioned reliably until we came across this problem on one
Windows 2000 server installation.
I'm confused that SqlXml is returning this message - In order to
troubleshoot I would need to know the service dependencies for SqlXml -
something I have not been able to establish so far from the on-line
documentation.
Message: The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it.
Source: mscorlib
Stacktrace:
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at Microsoft.Data.SqlXml.SqlXmlCommand.fillManagedWra pper()
at Microsoft.Data.SqlXml.SqlXmlCommand.construct()
at Microsoft.Data.SqlXml.SqlXmlCommand..ctor(String cnString)
at xxxxx.DataAccess.SqlClientHelper.ExecSqlXmlQuery(S tring sqlxmlquery,
String sqlxmlconnectionstring, Hashtable sqlXmlParams, Boolean isSP)
at xxxxx.Occam.ReportQueue.Report.GetNext(Int32 currentLoad, Int32
ceiling, DBConfig dbconfig, Config config, LanguageManager languageManager)
Eagerly awaiting any suggestions on this. This is an important issue for us,
as it's preventing us from completing roll-out to an important client.
regards,
James Ashton
Hi James,
As far as I know SQLXML does not have any service dependencies,. I think
this is happening because either sqlxml is not registered properly or the
managed wrapper is not being loaded properly. Please make sure that sqlxml
is registered properly and that the managed wrapper is in the assembly
cache.
If you are still hitting this problem let me know.
Thank you,
Amar Nalla
PS: This posting is provided AS IS and confers no rights or warranties.
"James Ashton" <JamesAshton@.discussions.microsoft.com> wrote in message
news:A6967A3A-31D8-4EAE-ABE6-8BDE6BE39A8F@.microsoft.com...
> Hi,
> I have a windows service written in C# that is using the SqlXml 3.0
Managed
> Classes.
> The service has functioned reliably until we came across this problem on
one
> Windows 2000 server installation.
> I'm confused that SqlXml is returning this message - In order to
> troubleshoot I would need to know the service dependencies for SqlXml -
> something I have not been able to establish so far from the on-line
> documentation.
>
> Message: The service cannot be started, either because it is disabled or
> because it has no enabled devices associated with it.
> Source: mscorlib
> Stacktrace:
> at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly)
> at System.Activator.CreateInstance(Type type, Boolean nonPublic)
> at Microsoft.Data.SqlXml.SqlXmlCommand.fillManagedWra pper()
> at Microsoft.Data.SqlXml.SqlXmlCommand.construct()
> at Microsoft.Data.SqlXml.SqlXmlCommand..ctor(String cnString)
> at xxxxx.DataAccess.SqlClientHelper.ExecSqlXmlQuery(S tring sqlxmlquery,
> String sqlxmlconnectionstring, Hashtable sqlXmlParams, Boolean isSP)
> at xxxxx.Occam.ReportQueue.Report.GetNext(Int32 currentLoad, Int32
> ceiling, DBConfig dbconfig, Config config, LanguageManager
languageManager)
>
> Eagerly awaiting any suggestions on this. This is an important issue for
us,
> as it's preventing us from completing roll-out to an important client.
> regards,
> James Ashton
>
|||I did instruct the client on this, but I haven't heard from them yet as to
whether this was successful. I will contact them to find out, and then update
this thread.
Unfortunately this is one of those where we couldn't reproduce the error in
house. So hopefully, the client will inform me that it's an installation
problem.
many thanks Amar, and hopefully they won't have any more problems.
regards,
James Ashton
"Amar Nalla [MSFT]" wrote:

> Hi James,
> As far as I know SQLXML does not have any service dependencies,. I think
> this is happening because either sqlxml is not registered properly or the
> managed wrapper is not being loaded properly. Please make sure that sqlxml
> is registered properly and that the managed wrapper is in the assembly
> cache.
> If you are still hitting this problem let me know.
> Thank you,
> Amar Nalla
> PS: This posting is provided AS IS and confers no rights or warranties.
> "James Ashton" <JamesAshton@.discussions.microsoft.com> wrote in message
> news:A6967A3A-31D8-4EAE-ABE6-8BDE6BE39A8F@.microsoft.com...
> Managed
> one
> languageManager)
> us,
>
>