KeycodeV2.dll not found - QueryInterface for interface CrystalKeyCodeLib.IKeyDecoder failed - Crystal Reports job failed because a free license could not be obtained in the time allocated
From: Erwin (eba_at_iqs.be)
Date: 01/17/05
- Next message: Mona: "Re: Reconnect field to other datasource"
- Previous message: Gareth Sharp: "Legacy.chm"
- Messages sorted by: [ date ] [ thread ]
Date: 17 Jan 2005 03:38:52 -0800
Concerns : deploying Crystal Reports with Visual Studio 2002 - 2003
The messages in the subject are the ones that I got when I tried to
install CR reports for the first time on a deployment server.
I have worked 8 days (night and day) to solve them, but finally I
arrived to create the reports I so badly needed.
In order to give you the chance to avoid the headaches in working with
CR, this is a list that I did. Maybe you can check them, and see if
there is anything you forgot.
First of, I will not offend your intelligence by supposing that you
didn't read the various articles that you find at
support.businessobjects.com. (When you type the error messages above
in the search engine, you'll get some 3 or 4 of them)
Secondly, I suppose you followed the proper routine to register your
product, so that you have a product key (19 digits).
Thirdly, I also suppose that you have followed the routine to create a
Setup project, in which you added the proper Merge Modules, and in
which you have entered the product key.
At this point, you still can have the error messages as mentioned
above. This is where the "support" of support.businessobjects.com
comes to a grinding standstill, and where this article will hopefully
help you.
The points you should check :
I. What is the version of the .Net framework on the production server
? Your Visual Studio application works with a specific Framework
version. Visual Studio only with .Net Framework 1.0, in VS 2003 you
have the choice : 1.0 or 1.1 (latter is default).
If you have developped in VS 2002, and the server has .Net Framework
1.1, there are 2 things you have to do :
a. install the .Net Framework 1.0 on the production server
b. let IIS know what version is to be used for your application. You
can set this with the utility aspnet_regiis.exe. I found a very fine
article here :
http://searchvb.techtarget.com/vsnetTip/1,293823,sid8_gci930036_tax293033,00.html
II. The ASPNET account should have READ & WRITE access to the folder
in which you have saved your reports (embedded or not). This is
because ASPNET writes a temporary file in this folder. If it doesn't
have the rights, it's not able to do that and will return an error.
NOTE : the ASPNET account is different on the various systems ! In
Windows XP Professional (probably your development machine) it's plain
old ASPNET, but on a Windows 2003 production server it's something
called IIS_WPG. (But give the rights also to the ASPNET account, just
to make sure).
III. The ASPNET account also has to have rights to read the Registry !
It's there where the product key is kept, so ASPNET has to have a peek
in there. I found a post somewhere in a message, and I'll just quote
it here :
" Step 1. Start>>Run>> regdit32
Step 2. Select teh window with tittle HKEY_CLASSES_ROOT on Local
Machine
Step 3. Select the Interface folder
Step 4. In the interface folder find:
4A4D268A-DF9B-4FC1-8301-D9FEEEF69F9C and highlight it.
Step 5. Select Security (from top menu)>>Permissions
Step 6. Select "Add"
Step 7. In the "Look in:" combobox at the top, select your local
machine
Step 8. In the listbox, double click ASPNET and click OK.
Step 9. On the previous screen, make sure "Read" is checked as
"Allow"
and click Apply.
Step 10. Now find the Typelib folder under HKEY_CLASSES_ROOT and
find
8D43D0B9-C14E-4577-9E67-A9A1EEF82302 in the typelib folder.
...follow the same steps to change permissions."
At this point, my Crystal Reports worked ! Hallelujah, praise the Lord
!
- Next message: Mona: "Re: Reconnect field to other datasource"
- Previous message: Gareth Sharp: "Legacy.chm"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
