Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / COM / April 2004



Tip: Looking for answers? Try searching our database.

strange DCOM security problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Daniel Roberts - 21 Apr 2004 19:06 GMT
I have a DCOM server application that I have recently recompiled and redistributed (by simply copying the exe over the old one). The new server has 1 new class, but did not break binary compatabiliy. The client applications now get a runtime error 70 when trying to access the new class, but the rest of the classes work fine. I ran DCOMCNFG and everything seems to be fine. On a whim I decided to add the usergroups to the default launch and default access permission (even though the server is set to use custom access and custom launch). Now it works fine. My question is this, why would modifying the default access and default launch have any effect on my server application that is set to use custom ?
Tony Proctor - 22 Apr 2004 07:24 GMT
Are you sure you don't accidentally have multiple versions registered
Daniel? Sorry but it's the only thing I could think of. Maybe you've set
explicit permissions for one version, but the other is still subject to the
defaults.

           Tony Proctor

> I have a DCOM server application that I have recently recompiled and redistributed (by simply copying the exe over the old one). The new server
has 1 new class, but did not break binary compatabiliy. The client
applications now get a runtime error 70 when trying to access the new class,
but the rest of the classes work fine. I ran DCOMCNFG and everything seems
to be fine. On a whim I decided to add the usergroups to the default launch
and default access permission (even though the server is set to use custom
access and custom launch). Now it works fine. My question is this, why would
modifying the default access and default launch have any effect on my server
application that is set to use custom ?
Daniel Roberts - 22 Apr 2004 17:26 GMT
Good suggestion Tony, but I checked that already. Its almost like the new class is not being recognized as part of the server. Once upon a time I read of someone having similar problems. I just wanted to see if anyone had a know bug or better yet a know solution

Thanks
Danie
 
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



©2009 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.