CliffordEvans
asked on
"Invalid export DLL or export format".
Getting the same error as has been previously reported: "Invalid export DLL or export format". Hhave a VB.NET web site exporting CrystalReports to PDF on on a Windows2003 server. Now trying to also deploy exact same thing to a Windows2000 server. Site works fine apart from this bit. Have copied msvcp60.dll to c\winnt\system32, installed CrystalReports SP2, tried differnt formats but made no difference. Urgent help/suggestions needed - please !!!
cj
PS.Framework 1.1, .VET 2003
cj
PS.Framework 1.1, .VET 2003
Interesting that this article states to put it where he did.
http://support.businessobjects.com/library/kbase/articles/c2013333.asp
Did you register it?
mlmcc
http://support.businessobjects.com/library/kbase/articles/c2013333.asp
Did you register it?
mlmcc
That is interesting - especially considering both articles site the same exact version number of Crystal...
I would say to at least try it in the application directory since putting it in sys32 didn't seem to help - but given the contradictory information that's just a guess.
frodoman
I would say to at least try it in the application directory since putting it in sys32 didn't seem to help - but given the contradictory information that's just a guess.
frodoman
ASKER
Have copied to the website bin directory too but no difference.
msvcp60.dll does not register - "This file cannot be registered"
cj
msvcp60.dll does not register - "This file cannot be registered"
cj
How about moving it to:
C:\Program Files\Common Files\Crystal Decisions\2.0\bin
I haven't seen anything saying to do this, however some of the other export dll's need to go here and obviously B.O. already has wrong info so it may be worth a shot...
C:\Program Files\Common Files\Crystal Decisions\2.0\bin
I haven't seen anything saying to do this, however some of the other export dll's need to go here and obviously B.O. already has wrong info so it may be worth a shot...
ASKER
It already got deployed to C:\Program Files\Common Files\Crystal Decisions\1.0\bin.
Rapidly losing my hair over this one !
Rapidly losing my hair over this one !
Do you have a 2.0\bin folder already? I was under the impression that the crystal components with VS 2003 when into the 2.0 folder and the the 1.0 folder was from VS 2002.
Could be wrong but we upgraded in the past and I've got the dll in both my 2.0 and 1.0 folder...
Could be wrong but we upgraded in the past and I've got the dll in both my 2.0 and 1.0 folder...
ASKER
No. Even on development PC (VS 2003) only have 1.0\bin, 1.1\Managed and a Patches directory.
Interestingly just noticed a new crxf_pdf.dll in the patches\files directory. Will try to copy this across to the remote server hosting the new website but have exceeded Remote Desktop logins (damn!). Must have been forgetting to logout each time.
Will get back to you once I can get hold of some remote support to reset the server.
Interestingly just noticed a new crxf_pdf.dll in the patches\files directory. Will try to copy this across to the remote server hosting the new website but have exceeded Remote Desktop logins (damn!). Must have been forgetting to logout each time.
Will get back to you once I can get hold of some remote support to reset the server.
How are you doing the export? Is this through a viewer or code?
If code show the code.
mlmcc
If code show the code.
mlmcc
ASKER
The code works fine on development PC and on another web server (Window2003), just having problems deploying to a second web server (Windows2000) although I don't think this is specifically OS related - more likely DLL related. If you still would like to see code though let me know.
cj
cj
ASKER
Sorry, should have mentioned that this is through the CRReportViewer.
If I rename crxf_pdf.dll on the 'working' web server I can produce the same error. Have therefore tried putting the same DLL in all suggested places on the 'non-working' server but still no good.
If I rename crxf_pdf.dll on the 'working' web server I can produce the same error. Have therefore tried putting the same DLL in all suggested places on the 'non-working' server but still no good.
ASKER
Solved this myself by using ADO OleDB instead of ODBC RDO !?!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
According to the documentation I've read this dll should be copied into the application directory not the sys32 directory (http://support.businessobjects.com/library/kbase/articles/c2013247.asp)
frodoman