Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codejock Errors in File Section #9

Closed
jpbro opened this issue Aug 29, 2016 · 5 comments
Closed

Codejock Errors in File Section #9

jpbro opened this issue Aug 29, 2016 · 5 comments

Comments

@jpbro
Copy link
Collaborator

jpbro commented Aug 29, 2016

I'm stuck on version 1.0.6 because in the latest version I keep errors regarding Codejock controls. I occasionally get the same error in 1.0.6 but retrying the same command always seems to work to "skip" the error. In the latest version, the error is constant on every run of UMMM. Any ideas?

Here's my UMMM ini:

Identity C:\XXX\FIVE.exe StatsLogSoftware.FIVE "FIVE by StatsLog"
Dependency ComCtl
File C:\XXX\Codejock.ChartPro.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.CommandBars.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.Controls.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.DockingPane.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.Markup.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.PropertyGrid.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.ReportControl.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.SkinFramework.Unicode.v16.2.6.ocx
File C:\XXX\Codejock.TaskPanel.Unicode.v16.2.6.ocx
TrustInfo 0 0
DpiAware 1
SupportedOS vista
SupportedOS win7
SupportedOS win8
SupportedOS win81
SupportedOS win10

Here's the command line:

ummm.exe c:\XXX\ini\five_manifest.ini c:\XXX\FIVE.exe.manifest

Here's the error output:

warning: coclass GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E245C475-92F4-4AF7-9231-F158D1A035C3}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({EEE5C475-92F4-4AF7-9231-F158D1A035C3}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({79EB54C2-BDD4-4257-8CF4-A2AB1674C51E}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1DC3FB95-9808-4CBF-BAC2-F2455C8C8A46}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass
GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E245C475-92F4-4AF7-9231-F158D1A035C3}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({EEE5C475-92F4-4AF7-9231-F158D1A035C3}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({79EB54C2-BDD4-4257-8CF4-A2AB1674C51E}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1DC3FB95-9808-4CBF-BAC2-F2455C8C8A46}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({
BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB
55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({1232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({E232C4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.CommandBars.Unicode.v16.2.6.ocxwarning: coclass GUID is duplicate of ({BDDDB4DB-8C00-4F05-AF87-9F05BCB55475}) in C:\five\bin\common\Codejock.ChartPro.Unicode.v16.2.6.ocx

@Carlos-Rocha
Copy link

Carlos-Rocha commented Aug 30, 2016

I'm getting warnings with Codekock.CommandBars.Unicode.15.3.1.ocx too, but the generated manifest works fine. I guess they are displayed only as a reference for debugging, probably in case comInterfaceExternalProxyStub entries are required?

In fact most of the referred GUID are not even included in the manifest - I only found an entry with another control, but not from codejock.

@jpbro
Copy link
Collaborator Author

jpbro commented Aug 31, 2016

Hi Carlos, thanks for the reply. It's good to know the generated manifest is OK even when these warnings appear.

It would be great if the messages didn't appear though - I have a custom built automated build script that stops on any unexpected return values from any calls out to processes like UMMM, resource replacers, inno setup, etc... With 1.06, I can just have my script automatically retry after getting a "bad" result, and usually the next run doesn't have any warnings. This is a bit of a hack, but it works well enough.

@wqweto
Copy link
Owner

wqweto commented Aug 31, 2016

@jpbro The weird behavior is if it "works" the second run. The warning is there when the same COM class is implemented in multiple OCXs. Control vendors do this sometimes for utility classes, like DataSource etc. which gets included in all OCXs that need these. Even MS does it on a couple of coclasses.

I'll check if these are PublicNotCreatable and silence the warning.

My build scripts depend on utils return value (0 - ok, else - error) and just forward output to a log file that eventually gets mailed with build status.

(I'm currently on vacation so this has to wait couple of weeks)

@jpbro
Copy link
Collaborator Author

jpbro commented Aug 31, 2016

Thanks for the response Vladimir.

I can't explain the 1.0.6 retry behaviour, but I just tried my build script again while watching it closely and indeed the first pass produced the warning message, at which point my script waits 2 seconds then retries the exact same command (confirmed by stepping through and watching the variables), and then the second pass succeeds without any warnings.

The idea to check the return value is a good one, except that I have an application call in my script for a poorly behaving application that can return 0 even when there was an error (catchable by testing for an error message result). This is why I switched to an "expected result text" approach. I can certainly rework my screipt to only check return value for UMMM while checking the result text for the problematic application.

Anyway, there's certainly no rush on this, so have a great vacation :)

@wqweto
Copy link
Owner

wqweto commented Sep 12, 2016

Just pushed 1.0.10 -- should fix this issue

@wqweto wqweto closed this as completed Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants