Re: SP6 and problems with XML

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 04/29/04 

Date: Thu, 29 Apr 2004 10:57:54 -0400

Would you know which DLL or OCX is causing the behaviour?
Which reference did you have to check off to get the XML
support? And which reference for the DocumentDOM support? 

-- 
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.
"Dave V" <d_verschleiser@hotmail.com> wrote in message
news:5f7791f7.0404290445.388118cf@posting.google.com...
Randy,
    Thanks for the suggestion.  The runtime DLL's were different, but
installing the updated version on the production server did not fix
the problem.
    Any other ideas?
Thanks,
Dave
"Randy Birch" <rgb_removethis@mvps.org> wrote in message
news:<eF16T9ZLEHA.1392@TK2MSFTNGP09.phx.gbl>...
> It is possible the VB runtime also changed, and is now mis-matched with
the
> runtime on the production server. Download this file, extract the exe to a
> test machine, and compare the version of the runtime in that on the
server.
> If they are different, you'll probably need to upgrade the server version
> (after testing for compatibility with other apps). Either that, or set up
a
> test machine with the files you have on the server, and if the component
> fails there, install the SP6 runtime and try again ... at least you're
> working on a test machine if other problems develop, or if this does not
> resolve the problem you haven't tampered with the prod server.
>
>
http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp6/download/default.aspx
>
> You want the last item on the page (Download Visual Basic Runtime)
> -- 
>
> Randy Birch
> MVP Visual Basic
> http://vbnet.mvps.org/
> Please respond only to the newsgroups so all can benefit.
>
>
> "Dave V" <d_verschleiser@hotmail.com> wrote in message
> news:5f7791f7.0404281903.7a299420@posting.google.com...
> : Hi,
> :
> :     Today I upgraded my development machine with Visual Studio SP6.
> : Now, when I compile my app and upload my DLL to my production app
> : server, I get an error (Object variable or with block variable not
> : set) whenever I try to access an object of type DOMDocument30.  My DLL
> : resides on the app server and is called from an ASP page on a separate
> : web server.  A proxy stub for the DLL is registered on the web server,
> : and the DLL has been set up as a COM+ app on the app server.  This app
> : has been in production for months without a hitch.
> :     Here's a simplified example:
> :
> : Sub Test(ByVal vsXMLString as string)
> : Dim loXML as New DomDocument30
> :
> :     loXML.loadXML vsXMLString
> :
> : End Sub
> :
> :     In this example, the error occurs when I try to call loadXML.
> : I've tried other methods of the object as well, and I always get this
> : error.  The code I'm running hasn't changed at all.  Like I said, the
> : only thing different is that I installed SP6 on my dev machine,
> : re-compiled there, and re-installed my DLL on my prod server.  (I also
> : recreated the proxy stub and reinstalled it on the web server.)  Now
> : my app doesn't run in production and my users are ready to slit my
> : throat (not to mention my boss).  Any ideas?
> :     (Using Win2K Pro on all machines mentioned.)
> :
> : Thanks,
> : Dave

Relevant Pages

  • Re: DCOM Surrogates
    ... > believed it was possible to create a remote-server dll where I did not ... you're server has to be instantiated in a runnable process. ... but I am quite excited about this technology and what it ... then have to change the main app to accomodate it. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Desperate help
    ... Can you get around the problem by decompiling the dll, ... > I hav lost the source to the app, it hasnt needed changed in some time ... > exact) is now broken and cannot be changed server side. ... > the world NOT to use DEVPATH, I dont see it being an issue here, I ...
    (microsoft.public.dotnet.framework.clr)
  • Re: SP6 and problems with XML
    ... Would you know which DLL or OCX is causing the behaviour? ... > runtime on the production server. ... > test machine with the files you have on the server, ... when I compile my app and upload my DLL to my production app ...
    (microsoft.public.vb.bugs)
  • SP6 and problems with XML
    ... when I compile my app and upload my DLL to my production app ... resides on the app server and is called from an ASP page on a separate ...
    (microsoft.public.vstudio.general)
  • SP6 and problems with XML
    ... when I compile my app and upload my DLL to my production app ... resides on the app server and is called from an ASP page on a separate ...
    (microsoft.public.vb.enterprise)