R
Richard
"Anno Domini" wrote:
>
>
> "Robert Aldwinckle" wrote:
>
> > "Tempest" <Tempest@discussions.microsoft.com> wrote in message
> > news:E5267F1C-0EFC-4C66-90CD-4D208FB28E2A@microsoft.com...
> > > Hey, thanks for the help,
> > >
> > > I cannot seem to register one of the DLL's
> > >
> > > regsvr32 qmgr.dll
> > >
> > > it dosent seem to work, it gives me:
> > >
> > > qmgr.dll was loaded, but the DllRegisterServer entry point was not found.
> > > The file cannot be registered
> > >
> > > Any other thoughts ??????
> >
> >
> > What version of that module do you have?
> >
> > Tip: you can use DependencyWalker to check both the properties
> > of that module and whether there is an external entry point of
> > DllRegisterServer in it.
> >
> > If you do have the right version of the module and it does appear
> > to have that entry point a possible explanation for your symptom
> > would be that the error message is bogus and represents an attempt
> > to explain a different unexpected symptom.
> >
> > To test that idea you can also use DependencyWalker,
> > using its profiler tool. In this case what you would do is
> > get it to execute the regsvr32.exe command with the operand(s)
> > that you were using. It will then generate a trace of modules and
> > intermediate return codes. Somewhere in there before the line
> > you see with the prompt for the error message would be a better
> > clue for why you can't register that module. E.g. perhaps there
> > is a permissions problem, missing module, unregistered dependent
> > module, etc.
> >
> > Oh. One more thing. Is BITS running? It would already be using
> > that module if it was and that could perhaps prevent the module from
> > being re-registered while it was in use. It would probably be a good
> > idea to stop BITS before trying the regsvr32 command.
> >
> > After you stop BITS you can check (from a cmd window)
> > if any other task is using that module with:
> >
> > tasklist /fi "Modules eq qmgr.dll"
> >
> > I just did that and that's how I reminded myself about BITS
> > because what that turned up was this:
> >
> > <example>
> > Image Name PID Session Name Session# Mem Usage
> > ========================= ====== ================ ======== ============
> > svchost.exe 860 Console 0 8,804 K
> > </example>
> >
> > Then using the PID from that result I found
> >
> > <example>
> > >tasklist /svc /fi "PID eq 860"
> >
> > Image Name PID Services
> > ========================= ====== =============================================
> > svchost.exe 860 AudioSrv, BITS, Browser, CryptSvc, Dhcp,
> > ....
> > </example>
> >
> >
> > An alternative diagnostic/repair would be to use bitsadmin's
> > new options under the /util category:
> >
> >
> > <extract>
> >
> > /UTIL /VERSION [/VERBOSE]
> > Displays the version of BITS currently active on the system.
> > The switch /VERBOSE prints additional information useful for
> > troubleshooting purposes.
> >
> > /UTIL /REPAIRSERVICE [/FORCE]
> > Attempts to repair a malfunctioning BITS service by inspecting some of the
> > service configuration settings. The switch /FORCE indicates that the BITS
> > service should be deleted and re-created if repairing the settings does not
> > clear the errors in starting the BITS service. Use this command with caution
> > as it is not possible to revert the changes.
> >
> > </extract>
> >
> >
> > Note: I have never tried the /RepairService option
> > and I have never seen a report from anybody trying it either.
> > You could be a trailblazer... <w>
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
> >
>
> All this is real nice, and it's great to see folks trying to help one
> another. I REALLY wish I had something to offer to help troubleshoot or
> resolve this problem, but alas, it's beyond me.... at this point in time.
>
> BUT, speaking of points, I have one that everyone everywhere seems to be
> overlooking. I haven't yet figured out whether it's overlooked because people
> are used to sloppy programming, whether they EXPECT shoddy service, or they
> really don't care how MS treats their customers after they already have their
> money.
>
> The fact of the matter is that THIS issue should never have existed. It is
> purely the result of sloppy progamming and said programming is directly
> related to Micro$oft's overzealous efforts to curb piracy. They're willing to
> F**K every legitimate user of their software to pursue the (maybe) 2% who
> have illegal copies. At $179 per copy of XP Pro, my own feeling is that THAT
> cost is figured in..... so what it amounts to is MS is rendering our systems
> useless (at least temporarily, while they make us run 100% CPU), all so they
> can squeeze a dime until it sh**s pennies. WAY TO GO UNCLE BILL!!!!
>
> You're one terrific geek, pal, but your marketing and PR really sucks.
> Betcha we can find a law firm to do a class action suit. Doesn't matter to me
> that I'll never see a dime.... I just want M$ and all their shareholders to
> pay for being idiots.
>
> If you're gonna be dumb, you better be tough.
>
I agree that MS can make its OS work perfectly and eliminate errors by
spending more time debugging. But, if you think that this is bad, install
Linux. The compatibility problems you will encounter there will make you go
insane. Making an OS is hard and compatibility issues always seem to happen.
But given all the different programs that run on our computers from all the
different companies, I am amazed that more do not occur.
>
>
> "Robert Aldwinckle" wrote:
>
> > "Tempest" <Tempest@discussions.microsoft.com> wrote in message
> > news:E5267F1C-0EFC-4C66-90CD-4D208FB28E2A@microsoft.com...
> > > Hey, thanks for the help,
> > >
> > > I cannot seem to register one of the DLL's
> > >
> > > regsvr32 qmgr.dll
> > >
> > > it dosent seem to work, it gives me:
> > >
> > > qmgr.dll was loaded, but the DllRegisterServer entry point was not found.
> > > The file cannot be registered
> > >
> > > Any other thoughts ??????
> >
> >
> > What version of that module do you have?
> >
> > Tip: you can use DependencyWalker to check both the properties
> > of that module and whether there is an external entry point of
> > DllRegisterServer in it.
> >
> > If you do have the right version of the module and it does appear
> > to have that entry point a possible explanation for your symptom
> > would be that the error message is bogus and represents an attempt
> > to explain a different unexpected symptom.
> >
> > To test that idea you can also use DependencyWalker,
> > using its profiler tool. In this case what you would do is
> > get it to execute the regsvr32.exe command with the operand(s)
> > that you were using. It will then generate a trace of modules and
> > intermediate return codes. Somewhere in there before the line
> > you see with the prompt for the error message would be a better
> > clue for why you can't register that module. E.g. perhaps there
> > is a permissions problem, missing module, unregistered dependent
> > module, etc.
> >
> > Oh. One more thing. Is BITS running? It would already be using
> > that module if it was and that could perhaps prevent the module from
> > being re-registered while it was in use. It would probably be a good
> > idea to stop BITS before trying the regsvr32 command.
> >
> > After you stop BITS you can check (from a cmd window)
> > if any other task is using that module with:
> >
> > tasklist /fi "Modules eq qmgr.dll"
> >
> > I just did that and that's how I reminded myself about BITS
> > because what that turned up was this:
> >
> > <example>
> > Image Name PID Session Name Session# Mem Usage
> > ========================= ====== ================ ======== ============
> > svchost.exe 860 Console 0 8,804 K
> > </example>
> >
> > Then using the PID from that result I found
> >
> > <example>
> > >tasklist /svc /fi "PID eq 860"
> >
> > Image Name PID Services
> > ========================= ====== =============================================
> > svchost.exe 860 AudioSrv, BITS, Browser, CryptSvc, Dhcp,
> > ....
> > </example>
> >
> >
> > An alternative diagnostic/repair would be to use bitsadmin's
> > new options under the /util category:
> >
> >
> > <extract>
> >
> > /UTIL /VERSION [/VERBOSE]
> > Displays the version of BITS currently active on the system.
> > The switch /VERBOSE prints additional information useful for
> > troubleshooting purposes.
> >
> > /UTIL /REPAIRSERVICE [/FORCE]
> > Attempts to repair a malfunctioning BITS service by inspecting some of the
> > service configuration settings. The switch /FORCE indicates that the BITS
> > service should be deleted and re-created if repairing the settings does not
> > clear the errors in starting the BITS service. Use this command with caution
> > as it is not possible to revert the changes.
> >
> > </extract>
> >
> >
> > Note: I have never tried the /RepairService option
> > and I have never seen a report from anybody trying it either.
> > You could be a trailblazer... <w>
> >
> >
> > Good luck
> >
> > Robert Aldwinckle
> > ---
> >
> >
> >
>
> All this is real nice, and it's great to see folks trying to help one
> another. I REALLY wish I had something to offer to help troubleshoot or
> resolve this problem, but alas, it's beyond me.... at this point in time.
>
> BUT, speaking of points, I have one that everyone everywhere seems to be
> overlooking. I haven't yet figured out whether it's overlooked because people
> are used to sloppy programming, whether they EXPECT shoddy service, or they
> really don't care how MS treats their customers after they already have their
> money.
>
> The fact of the matter is that THIS issue should never have existed. It is
> purely the result of sloppy progamming and said programming is directly
> related to Micro$oft's overzealous efforts to curb piracy. They're willing to
> F**K every legitimate user of their software to pursue the (maybe) 2% who
> have illegal copies. At $179 per copy of XP Pro, my own feeling is that THAT
> cost is figured in..... so what it amounts to is MS is rendering our systems
> useless (at least temporarily, while they make us run 100% CPU), all so they
> can squeeze a dime until it sh**s pennies. WAY TO GO UNCLE BILL!!!!
>
> You're one terrific geek, pal, but your marketing and PR really sucks.
> Betcha we can find a law firm to do a class action suit. Doesn't matter to me
> that I'll never see a dime.... I just want M$ and all their shareholders to
> pay for being idiots.
>
> If you're gonna be dumb, you better be tough.
>
I agree that MS can make its OS work perfectly and eliminate errors by
spending more time debugging. But, if you think that this is bad, install
Linux. The compatibility problems you will encounter there will make you go
insane. Making an OS is hard and compatibility issues always seem to happen.
But given all the different programs that run on our computers from all the
different companies, I am amazed that more do not occur.