WiseComCapture doesn't create reg file
Updated: 22 May 2010 | 9 comments
This issue has been solved. See solution.
I'm using WiseComCapture (WPS 7 SP3) to create a reg file for registering C:\windows\system32\capicom.dll. The command-line is the following: WiseComCapture /r C:\Windows\System32\capicom.dll /u C:\Temp\capi.reg.
According to the TaskManager, WiseComCapture runs for a moment and then finishes, but it's not creating the appropriate reg file.
Has anyone encountered this as well? I was using WiseComCapture successfully several times before...
Thanks
discussion Filed Under:
Comments
Does capicom.dll have any registration information to capture?
Before we go any further, have you checked that Capicom.DLL has any registration information internally for WiseComCapture to export?
Not all DLL files require registration, or contain registration information.
The quick way to check is to try registering the file with regsvr32.exe. If there is no registration information, regsvr32.exe will tell you in an error message, so run this check from a command line so that you can see what regsvr32.exe returns.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Even though the DLL is
Even though the DLL is register, WiseComCapture has got no information regarding capicom.dll.
I copied capicom.dll to the VM that has WPS 7.0 SP3 installed on it. I tried registering capicom.dll then i tried with WiseComCapture. The tool looks running under processes but there is no REG file created. I looked for REG file even after WiseComCapture finished execution.
No trace of REG file. So i tried creating REG file for MSI.DLL. I can see the REG file and registry content. If WiseComCapture can capture for MSI.DLL then it should capture info for capicom.dll alo. I used the following commandline:
"c:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WiseComCapture.exe" /r c:\WINDOWS\system32\capicom.dll c:\capi.reg
This is the first time i came accross this issue with WiseComCapture.
Thanks,
Eshwar
How do we move any further here
Thank you guys so far for your great help.
As Eshwar mentioned, yes, capicom.dll needs to be registered. I tested this before as well.
So, the issue is reproducable? Great.
Do we need to log an issue here?
And how do I solve this issue on the short hand?
WCC is tempremental
WCC is tempremental sometimes. My WCC-runner script is set up such that, if no .REG is created, to try and switch the path from where WCC is run to the actual DLL location instead. Thus, in effect, it tries this first:
CD "C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor"
WiseComCapture /r C:\WINDOWS\system32\capicom.dll %temp%\capicom.reg
then tries:
CD C:\WINDOWS\system32
"C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WiseComCapture /r capicom.dll %temp%\capicom.reg
I am, however, left wondering what sort of build you have where a core file needs to be re-registered.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Very interesting...
VBScab, thanks for your detailed answer. I'm going to try your workaround with changing the path.
Good question. This is a package which we distribute to other companies as well. In-house it works absolutely fine, but the other companies encountered errors and needed to reregister capicom.dll to make the app work. So I planned to add those registry keys to the package to help them. Great info, wasn't aware that it is a core file.
Hmmm...adding fixes for
Hmmm...adding fixes for broken builds to your package is the road to hell and not one I'd follow. I would simply provide information to clients that if error 'x' occurs, it's because CAPICOM.DLL registration is broken, along with information about how to re-register it.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
What about capturing changes when DLL is registered through CMD?
What about capturing changes when DLL is registered through CMD?
Why not just run REGSVR32.EXE as a custom action?
Both REGSVR32.EXE and CAPICOM.DLL are system files, so why struggle to come up with the required registry keys when it is so simple to re-register the DLL by running regsvr32.exe with the /s silent switch.
Otherwise, unless you remember to include the registration information in a permanent component, uninstalling your application will also effectively unregister capicom.dll
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Good point on the uninstall,
Good point on the uninstall, Ed.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Would you like to reply?
Login or Register to post your comment.