 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / COM / September 2008Registration Problems for my DLL
I have a DLL long running in multiple locations. A new customer, however, is running into problems. After further investigation, the DLL registration succeeds but I found there to be no entry in the registry. Could permissions (2003 server) be a problem? Anything else? Why would it succeed?  SignatureBrad Eck <a href="http://www.sitesdynamic.com">SitesDynamic</a> <a href="http://www.eternalelement.com">Eternal Element</a> <a href="http://www.basketsetcetera.com">Baskets Etcetera</a> > I have a DLL long running in multiple locations. A new customer, however, is > running into problems. It's always the new customers. <g> > After further investigation, the DLL registration > succeeds but I found there to be no entry in the registry. That's a self-contradictory statement. Registration, by definition, cannot succeed without entries being made in the registry. Get it? Registry <-> Registration? > Could permissions (2003 server) be a problem? Could be. Is the registration being attempted from an Administrators account? > Anything else? Why would it succeed? Define "succeed." Signature.NET: It's About Trust! http://vfred.mvps.org Totally agree. Totally contradictory - yet that's the fact. regsvr32 returns a successful registration but open the registry and do a search and there is no entry. So, success is defined as being regsvr32 "success" response whereas failure is defined to be that the entry is not in the registry. He says he is an admin yet he contually tells me he has fairly limited control so I question it. SignatureBrad Eck <a href="http://www.sitesdynamic.com">SitesDynamic</a> <a href="http://www.eternalelement.com">Eternal Element</a> <a href="http://www.basketsetcetera.com">Baskets Etcetera</a> > > I have a DLL long running in multiple locations. A new customer, however, is > > running into problems. [quoted text clipped - 14 lines] > > Define "succeed." > Totally agree. Totally contradictory - yet that's the fact. regsvr32 returns > a successful registration but open the registry and do a search and there is > no entry. So, success is defined as being regsvr32 "success" response whereas > failure is defined to be that the entry is not in the registry. He says he is > an admin yet he contually tells me he has fairly limited control so I > question it. Eeeewwwww... Sounds like some sort of warped corporate lockdown. I've never heard of such a situation. I suppose you could test accessibility by writing a little applet that creates a few of the keys needed to register this component. Wish I had anything encouraging to add. Signature.NET: It's About Trust! http://vfred.mvps.org >> > I have a DLL long running in multiple locations. A new customer, however, is >> > running into problems. [quoted text clipped - 18 lines] >> ..NET: It's About Trust! >> http://vfred.mvps.org ok. well thank you for the help anyway. SignatureBrad Eck <a href="http://www.sitesdynamic.com">SitesDynamic</a> <a href="http://www.eternalelement.com">Eternal Element</a> <a href="http://www.basketsetcetera.com">Baskets Etcetera</a> > > Totally agree. Totally contradictory - yet that's the fact. regsvr32 returns > > a successful registration but open the registry and do a search and there is [quoted text clipped - 29 lines] > >> ..NET: It's About Trust! > >> http://vfred.mvps.org "Brad" <brad.eck@sitesdynamic.com> wrote... > ok. well thank you for the help anyway. I'm surprised Karl did not mention trying to put the DLL file into a "%programfiles% location. Did you try registering it there? There might be a way to get around the problem with group policies (gpedit.exe on XP, not sure if it exists on a 2003 server). Let us know if this helps at all or if you can tell your "new" customer to try gpedit.exe (might have to dig through all the settings). I don't have access to a 2003 Server so I can not help in that regards. The other thing you might try involves possibly creating the key in the HKEY_CURRENT_USER root instead of HKEY_LOCAL_MACHINE. Just throwing out possible ideas to you. I know very little about Windows 2003. Have just read some things in the distant past. If someone else wants to jump in and add to this so as to help me out, that might help. One last thing, if all else fails, tell the "new customer" to make sure he belongs to the Administrators group through the User configuration tool (lusrmgr.msc for XP). SignatureJim Carlock More Than Five Senses http://www.associatedcontent.com/article/381163/more_than_five_senses.html > "Brad" <brad.eck@sitesdynamic.com> wrote... >> ok. well thank you for the help anyway. [quoted text clipped - 4 lines] > problem with group policies (gpedit.exe on XP, not sure if it exists on a 2003 > server). With group policies, who knows, eh? <shrug> > One last thing, if all else fails, tell the "new customer" to make sure he belongs > to the Administrators group through the User configuration tool (lusrmgr.msc for > XP). That's definitely a given. If they're not doing the regsvr thing as an admin, they're toast. Given the description (an admin with "fairly limited control"?), I'm still betting on that. Signature.NET: It's About Trust! http://vfred.mvps.org |
Reply to this Message |
 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.