Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / July 2003

Tip: Looking for answers? Try searching our database.

Data.SqlXml not found on Web Service machine

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
[ mcberio ] - 29 Jul 2003 17:35 GMT
Hi,

We are trying to set-up our app on a remote network. On one machine we have
SqlServer 2000, on the other we have our Web Service.

The error message on the Web Service machine is:

"File or Assembly Name Microsoft.Data.SqlXML or one of its dependancies was
not found."

We believe all required service packs etc are installed... except SQLXML 3.0
won't install on the Web Service machine because SqlServer isn't installed
here.

Must the web service run on the SqlServer machine? We can't figure out how
to install the Data.SqlXml dll as a standalone component.

Tried google and MSDN with no joy. Any ideas would be greatly appreciated.

Many thanks,

JB
Dave Beauchemin [MVP] - 30 Jul 2003 16:58 GMT
SQLXML 3.0 is meant to be installed on a web server too... Think of it as a
driver (though it's a lot more than that, but for purposes of
simplification) for SQL Server.

You need to have it on the server your web service is running on in order
for you to be able to use this functionality (specifically, access the
Microsoft.Data.SqlXml assembly).
Signature


    Dave Beauchemin
    Microsoft MVP, MCP
    www.webdotmag.com

> Hi,
>
[quoted text clipped - 18 lines]
>
> JB
[ mcberio ] - 30 Jul 2003 18:22 GMT
Hi,

Thanks for the response. I appreciate it.

When we tried to run the install of SQLXML on the web server running the Web
Services (note this machine doesn't have a SqlServer installed - our
database is on a separate server) we got a message saying:

"...at least SQL Server client installation is required..."

It seems like a bit of a restriction that you must install a SqlServer
client before you can install SQLXML. That means if you have a Web Service
which needs the Data.SqlXml assembly then not only do you need to install
SQLXML, but you need to install some version of SqlServer too!

Surely I am missing something here? There must we a way to install the
assembly on a database-less server?

Many thanks,

JB

> SQLXML 3.0 is meant to be installed on a web server too... Think of it as a
> driver (though it's a lot more than that, but for purposes of
[quoted text clipped - 28 lines]
> >
> > JB
Dave Beauchemin [MVP] - 30 Jul 2003 18:39 GMT
JB,

If it's asking you for SQL Server Client, you can simply install the Client
connectivity tools and it should work (the client connectivity tools do not
install SQL Server, they just install Enterprise Manager and the like).

See
http://www.microsoft.com/downloads/details.aspx?FamilyId=4023DEEA-F179-45DE-B41D
-84E4FF655A3B&displaylang=en

for the requirements page (you will also need MDAC 2.6 and the SOAP Toolkit
2.0 to be installed before installing SQLXML).

See the microsoft.public.sqlserver.xml group for additional information.
Signature


    Dave Beauchemin
    Microsoft MVP, MCP
    www.webdotmag.com

> Hi,
>
[quoted text clipped - 54 lines]
> > >
> > > JB

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.