Cannot find KeycodeV2.dll, or invalid keycode.

  • Thread starter Thread starter john bailo
  • Start date Start date
J

john bailo

Running a webForm with a crystal report on a webserver,

Cannot find KeycodeV2.dll, or invalid keycode.

Appears.

I have added the regwiz.msm to my Setup Project and
added the License Key and re-installed.
 
0. Added regwiz.msn
1. Added what I think is the license key to MergeModuleProperties.LicenseKey
2. Compiled the *.msi
3. Deployed
4. Installed.

As far as Merge Modules, I have read so many 'solutions' that I put them all
in,
including:

Crystal_Database_Access2003.msm ( it uses Sql server )
Crystal_Database_Access2003_enu.msm
Crystal_Managed2003.msm
dotNETFXRedist_x86_enu.msm
Managed.msm
regwiz.msm
Primary output from marlookup (Active)
Content Files from marlookup (Active)
 
Did you install for Everyone or just the current logged in user (Even if
administrator)? Something is probably running as LocalSystem and does not
have access to the registry keys.
 
You license key is probably incorrect.
john bailo said:
0. Added regwiz.msn
1. Added what I think is the license key to MergeModuleProperties.LicenseKey
2. Compiled the *.msi
3. Deployed
4. Installed.

As far as Merge Modules, I have read so many 'solutions' that I put them all
in,
including:

Crystal_Database_Access2003.msm ( it uses Sql server )
Crystal_Database_Access2003_enu.msm
Crystal_Managed2003.msm
dotNETFXRedist_x86_enu.msm
Managed.msm
regwiz.msm
Primary output from marlookup (Active)
Content Files from marlookup (Active)
Click to expand...
 
Crystal_Database_Access2003.msm ( it uses Sql server )
Crystal_Database_Access2003_enu.msm
Crystal_Managed2003.msm
dotNETFXRedist_x86_enu.msm
Managed.msm
regwiz.msm
Primary output from marlookup (Active)
Content Files from marlookup (Active)
Click to expand...


Howdy,

You have a mix of merge modules from VS.NET 2002 and 2003. Review the
CR.NET Deployment doc at:

http://support.crystaldecisions.com/communityCS/TechnicalPapers/crnet_deployment.pdf.asp
Especially the grid on page 5.

Also, make sure you are using the 19-digit license key from VS.NET, not the
10-digit registration key. I've seen this wrong in a lot of guides.

HTH,


Sean G.
 
Back
Top