Hi.
I try to instansiate an COMTI-component in a VB6-application. It's the first time we try that in a server 2003, and we only get a error 424, Object required. We use this comti to reach anoter computer, so it's just installed with an export of .msi-file from the other one. We have don e this a lotsa times on other mashines with XP and server 2000, and never got this problem, so I guess it's 2003-related. Can anyone help us with this
/Erik
COMTI and Server2003 in VB6?
Hot Topic
- Error loading VB.Net
- Using XML in Comments
- system Shutdown
- VB App freezes when accessing properties of Excel object...
- Working with Files in VB.NET compared to VBA
- Update SQLdataBase w/ VB 2005 Beta2
- Error with Dataset 2003 ??
- Generating thumbnails for video files?
- DataGrid Cell Value ???
- XML code commenting in Office Tools projects?
Visual Basic
- KEYBD_EVENT problems
- ASP.Net Problem ! PLEASE PLEASE HELP
- Opening a *.chm file from a windows forms application
- How to use UpdateLayeredWindow API to create translucent form with ranging alpha values
- Installing VB.Net without product ID
- VB calling C executable
- Is there a practical way to use SecureString?
- VoIP
- form inheritance
- Datagrid Child Record Links
COMTI and Server2003 in VB6?
nivz_k
These forums are for VB.NET and there are better places to find answers for older versions of VB. Maybe the VB6 newgroups - http://msdn.microsoft.com/newsgroups/default.aspx dg=microsoft.public.vb.general.discussion&lang=en&cr=US
or perhaps www.vbcity.com may be useful places to search for answers on VB6 related questions.
However, as to your problem. I have come across a similar problem a couple of times with apps that worked just fine in XP and below written in VB6 and not working on Windows 2003 and eventually tracked it down to local software restriction policies on the box preventing the application from creating DCOM components.
Obviously I cant be sure that this is the cause but I would hazard the guess that the installer you put on is a proxy to a dcom component on a remote machine and that with the software restriction policies its not allowing this to occur and then giving you the error 424. Either way I would be fairly sure that the Problem is related to Software Restriction Policies on the box, I think by default a lot of them are quite tight on 2003 (almost the reverse of XP which was quite open and hence unsecure)
A web search on "Software Restriction Policies + windows 2003" will reveal a lot of hits but the Control Panel -> Adminstrative Tasks -> Local Security Policy -> Software Restriction Policies appears to be the area I would focus on.
Good luck