thirtysomething
asked on
Cannot find KeycodeV2.dll, or invalid keycode
Hi all,
We have several web application running on a windows 2000 server. Some of these were developed in VS2002 and some in VS2003. We have decided to move the websites to a new server which is running Windows 2003. I coppied all the folders and set them up in ISS but any projets that reference crystal get the following error when you try view them in a browser
Cannot find KeycodeV2.dll, or invalid keycode
I have searched on eth web and have created the merge modules and also allowed access to the specific registry keys but still have the issue.
Any help would be appreciated.
We have several web application running on a windows 2000 server. Some of these were developed in VS2002 and some in VS2003. We have decided to move the websites to a new server which is running Windows 2003. I coppied all the folders and set them up in ISS but any projets that reference crystal get the following error when you try view them in a browser
Cannot find KeycodeV2.dll, or invalid keycode
I have searched on eth web and have created the merge modules and also allowed access to the specific registry keys but still have the issue.
Any help would be appreciated.
ASKER
Hi, Thanks for the reply.
These are web forms so thats why I just copied them.
Obviously for the merge modules I created a MSI and installed and the KeyCodeV2.dll was registered correctly.
An update on this is that I uninstalled the merge modules and recreated the merge modules form a machine running VS2002, deployed this to the server, changed all virtual directorys to run using >net 1.1 as opposed to .Net 2.0 and this resolved the issue.
However this is not the perfect solution as I may need to run in .NET 2.0. Any ideas.
These are web forms so thats why I just copied them.
Obviously for the merge modules I created a MSI and installed and the KeyCodeV2.dll was registered correctly.
An update on this is that I uninstalled the merge modules and recreated the merge modules form a machine running VS2002, deployed this to the server, changed all virtual directorys to run using >net 1.1 as opposed to .Net 2.0 and this resolved the issue.
However this is not the perfect solution as I may need to run in .NET 2.0. Any ideas.
I don't think VS2002 and 2003 apps are compatible with .Net2.0 at least with Crystal. Crystal had to patch Crystal to handle .Net 2.0
mlmcc
mlmcc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also ensure you have given the proper permissions to the dCystal directoies.
mlmcc