PDA

View Full Version : Once again, the warning doesn't resemble the docs



FiniteSolutions
07-12-2005, 07:39 PM
I'm getting 65 or so of these out of my build:

ISDEV : warning -6204: The imported registry information for component MatListFiles conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{66337FB0-B315-4537-9508-FB5EE8DA0892}\InprocServer32] Value: ThreadingModel Data: Both

The KB reports that -6204 has this text: "An error occurred importing %1 for Component %2. Make sure the file exists in the specified location and that the file is a valid REG file."

So I'm more than a little confused. I'd like to get rid of the warning, but there appears to be no information on how to get rid of *this* warning, since the index number points to an entirely different thing.

RobertDickau
07-12-2005, 08:37 PM
Judging from the warning message: do you have a component with the REG File to Merge at Build setting, and also duplicate information in the Registry table (one of the Registry views)?

FiniteSolutions
07-13-2005, 01:37 PM
All of the components are extract-at-build for registry settings. Nothing extra exists in the registry view.

RobertDickau
07-13-2005, 07:38 PM
Hmmm... If there's nothing in the Registry table, perhaps the same file was included in two different components?

mark.ka
07-14-2005, 09:41 AM
Hi,

I also encouner such problem with all .NET assemplies, included in my project. It didn't happen with IS 10.5. Components don't have REG file to merge and files are included only once in project.

SGorman
07-14-2005, 11:35 AM
I'm also getting these messages. No there are no .reg files to merge, only .NET assemblies.

FiniteSolutions
07-15-2005, 05:50 PM
My configuration is the same in this respect to Mark's.

I have two issues:

1 -- The documentation doesn't describe *THIS* error message, which is d*** frustrating, especially for the money you're asking for this product.
2 -- I have no idea how to eliminate the warning itself.

I also have no idea how a software company with national or worldwide reach can *close its doors* at 3:00 p.m. Pacific Time. Maybe this package isn't for me on those grounds alone, but if there's a Macrovision person there willing to take ownership of this before my eval runs out, well, hey, there might be a *sale* in it for y'all...

kferree
07-18-2005, 04:01 PM
Just upgraded my 10.5 projects to 11 today, and now I too am getting this warning when compiling my project. It is in reference to a .NET assembly.



ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32] Value: ThreadingModel Data: Both
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32] Value: Class Data: Itron.EE.DAQi.Plugins.ServiceModeMV90Xi.Interfaces.COM.COMInterface
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32] Value: Assembly Data: IEECOM, Version=0.1.0.0, Culture=neutral, PublicKeyToken=166970f2905a0574
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32] Value: RuntimeVersion Data: v1.1.4322
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32] Value: CodeBase Data: file:///[#ieecom.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F]
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32\0.1.0.0] Value: Class Data: Itron.EE.DAQi.Plugins.ServiceModeMV90Xi.Interfaces.COM.COMInterface
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32\0.1.0.0] Value: Assembly Data: IEECOM, Version=0.1.0.0, Culture=neutral, PublicKeyToken=166970f2905a0574
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32\0.1.0.0] Value: RuntimeVersion Data: v1.1.4322
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32\0.1.0.0] Value: CodeBase Data: file:///[#ieecom.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F]
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\Implemented Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}] Value: + Data:
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\InprocServer32\0.1.0.0] Value: + Data:
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\CLSID\{33EA2F3E-3274-4F92-A2B5-4402FE3F2BA9}\ProgId] Value: + Data:
ISDEV : warning -6204: The imported registry information for component IEECOM.dll.1AC83D5A_302A_4F3F_9700_0474220EFC4F conflicts with existing registry information in your project. Key: [HKEY_CLASSES_ROOT\Itron.EE.DAQi.Plugins.ServiceModeMV90Xi.Interfaces.COM.COMInterface\CLSID] Value: + Data:


None of these registy values exist in the registry table so I don't know what it's complaining about.

Bruno Walter
08-03-2005, 08:10 PM
Add me to the list of people that upgraded from 10.5 to 11 and was greeted by a whole slew of these warnings. Anyone figure out how to make them go away yet.

Graham Douglas
08-17-2005, 05:11 AM
I was encountering this problem as well. But I think I may have stumbled across a solution. If you clear the Key Files for the components which have the warnings, then the warnings disappear. I've not tested the resultant installer yet, so I'm not sure how well this'll work. I'll try and post back once I've tested it!

Let me know if this works for any of you guys!

Thanks,
Graham

SGorman
08-17-2005, 09:16 AM
Yes, clearing the key file flag got rid of the problem for me. However, if you add the key file flag back the error messages come back too.

Ron Schaeffer
08-26-2005, 10:43 AM
I'm trialing an upgrade from DevStudio 9 to InstallShield 11 and I've encountered this on one of my projects (so far). I have a component for which the single .NET assembly DLL is the key file; .NET Scan at Build is set to Properties Only; COM Extract at Build is No; there is no REG File to Merge at Build. What I have found is that I can "turn off" the warnings if I turn off the .NET COM Interop setting; turn it back on again and the warnings re-appear.

In a way this makes some sort of sense - the .NET COM Interop setting description says it will create registry entries at installation, so it might be obtaining some of this info at build time.

Unfortunately, turning off the .NET COM Interop property probably isn't an option for me (my developers tell me specifically that they need this feature on this DLL).

I'd be interested to know Graham's results from his test installs after ignoring these warnings.

Ron

SuXskiz
09-20-2005, 10:42 AM
My experience with IS11 (I've upgraded from a 7.04) indicate that all assemblies with property .NET Com Interop = Yes during compilation fall in this warning.
In my project I couldn't find registry keys indicated by warning, not even on my pc registry.
Deleting the old .reg file (generated by preceeding builds) on source directory not resolve the problem, only setting .NET COM Interop = No the warning disappear.

I also tried to clear Key file on my assembly components (1 file associated for component) but the build process stops with a 7104 error. :confused:
Note that I have already deployed setups built with this warning without any problems.
What the point of view of installshield's developers????

Thanks at all.
Bye.

furrymcmonst
10-06-2005, 04:53 PM
Just converted to version 11 from version X today and am getting the same error.

InstallShield, will you please post a response to this?

OzzyBee
10-26-2005, 04:47 AM
Guys

I have managed to get Installshield to give me a fix ! They've given me a new version of ISMsiEntity.dll which lives in program files\installshield 11\system.

I'd attach the link but the zip file seems corrupt - 2 copies of same file in a zip file ?? File does get rid of errors but am unsure if it's totally OK.

If I can get a link to a decent file will post !

furrymcmonst
11-01-2005, 03:10 PM
InstallShield,

Please post the dll somewhere so we can fix this irritating problem. My registry entries have bloated from 2000 to 4000 because of this bug. Don't make us pay $100 to call support to get a fix for this bug. It is your fault, not ours! Please.

SGorman
11-03-2005, 09:21 AM
This fixed my problems!

furrymcmonst
11-03-2005, 06:23 PM
SGorman,

Thanks very much! This cured the problem and my registry table now has 2453 less entries.

I'm curious to know how you acquired the substitute dll. It's a shame that InstallShield itself wouldn't answer the request to post it.

Thanks again.

SGorman
11-04-2005, 09:08 AM
I have a support agreement with InstallShield so once I heard there was a resolution, I called them and just asked for the DLL. They sent it right away.

Gilesey
11-29-2005, 07:06 AM
Thank you Gorman, this has solved my error.

The only thing now that concerns me is, that this is not an issue that should only be reserved for those with support agreements, this is a typical 'service pack'. Also, as a software developer, it horrifies me to see companies giving out DLL's to end customers, that's really really insane.

Regardless of the insanity, thanks for getting rid of the hundreds of warnings I had. Although not worthy of a hotfix, it would be good if they could provide this as a download via the CORRECT knowledgebase article for the error 6204, or at least some reassurance that this was not a warning one should be concerned with, and that it is safe to proceed.

gmurdock
11-29-2005, 12:35 PM
This also resolved my issues. Any idea when this DLL will be distributed through normal channels?

Galen Murdock
Veracity Solutions

rawytsch
11-30-2005, 07:37 AM
Hi,

I have encountered the same warning -6204 for all registry files in my project which are marked in a component of Organization/Components for
"REG File To Merge At Build", i.e. IS reports over 5000 :eek: warnings!

These warnings arised as soon as I converted my ism project file from
IS 8 resp. 9 to InstallShield 11, i.e. I did not change any settings in my
project, in IS 8 resp. 9 everything was ok so just running the same
(successfully converted) project under IS 11 brings IS to report my
head off with these warnings :confused: !

I also tried to add a totally new component but this warning comes up with every registry entry of a reg file to be merged at build time.

As the registry files may alter quite often the alternative way of importing
the registry files once into the project using the wizard is not applicable since I do not have the time to check all 5000 registry entries for each daily build (and we build several projects with approximately 5000 registry entries each every day :eek: !). Thus these warnings must be classified as a severe bug which should be fixed by InstallShield hopefully quite soon!

Please help, fix the bug or tell me an applicable workaround!

Peter Rawytsch

--
Peter Rawytsch
Installations of Signal Generator Family firmware
Rohde & Schwarz GmbH & Co KG
Munich, Germany

rawytsch
01-16-2006, 06:21 AM
Hi Folks,

by chance I encountered this release note for InstallShield 11.5:

1-1B3TRP
Using the REG File To Merge At Build option no longer causes build warning 6204; in addition, extra registry entries are no longer created in the built .msi package

This means:

Luckily they fixed the bug!
Luckily I have chosen to order 11.5 instead of 11 although I did not knew that the bug was fixed for 11.5 (The German version was available only in Version 11 at the time of order, so luckily I understand English :rolleyes: )
These warnings were no kind of individual imagination or hallucination, it really was a bug!
Macrovision obiously knew very well about this bug but didn't so much as reply to this or any other similar thread to tell the customers that they're working on it to fix it. No reaction at all
I am not amused about such a customer relationship. :(


Peter Rawytsch

--
Peter Rawytsch
Installations of Signal Generator Family firmware
Rohde & Schwarz GmbH & Co KG
Munich, Germany