Possible Problem With Version Number

Started by pepsisc, November 30, 2008, 04:30:11 PM

Previous topic - Next topic

Randem


Randem

Try this, change this line in your run section:
 
Filename: msiexec.exe; Parameters: /package {tmp}CRXI_RDC_Redistribution.msi /passive; WorkingDir: {tmp}; Flags: skipifdoesntexist
 
to
 
Filename: msiexec.exe; Parameters: /package {tmp}CRXI_RDC_Redistribution.msi; WorkingDir: {tmp};
 
See if you can see the CR msi file being installed. That seems to be the problem. I don't think that this completes successfully.

pepsisc


pepsisc

Randem:
 
I will do what you requested.  
I wanted to let you know, I think I might have found the problem. File craxdrt.dll , I don't think is being registered.
 
When you install my SETUP file on a system that does not have Crystal Reports installed, that's when the problem occurs. If you install it on a system that does not have C:\Program Files\Common Files\Business Objects\3.0\bin, the application does work.
 
Here is a post a put out on a VB/Crystal Report forum:
----------------------------------------------
Regsvr32 Problem
OS = Windows XP SP3 Professional
 
I have a weird problem. I copied a file called craxdrt.dll to c:\windows\system32
I then tried to register it. I tried all 4 of these variations.
Code:
 
regsvr32.exe c:\windows\system32\craxdrt.dll
regsvr32.exe c:\windows\system32\craxdrt.dll
regsvr32 c:\windows\system32\craxdrt.dll
regsvr32 c:\windows\system32\craxdrt.dll
 
Each time I got the following error:
Quote:
LoadLibrary(file path and file name) failed. The specified module can not be found.
I don't understand the reason for the error. The file is there--I SEE IT. Could it be a bad copy even though I tried copying it several times?
Attached Thumbnails
Click image for larger version Name: system32.jpg Views: 2 Size: 59.1 KB ID: 753  
__________________
Thanks,
Sam

 
(Message edited by pepsisc on December 20, 2008)

Randem

Negative on email or private messages. This forum is designed for help andt all other contact is a paid service. If you would like that service please let me know.
 
About your installation, I see that the CR msi file is being run but does it finish? That may be the reason the files are not registered. I see from the log that an attempt to register the files happens but they are not in the proper location or on the computer at all.

pepsisc

randem:
 
Is there a way I can get in touch with you (through e-mail or Private Message)?
 
Do you have access to members profile. Can you access my e-mail address and let me know?
 
Thanks,
Sam

Randem

Replace your Crystal Reports.tpl file with this one
There is one line difference and you can just edit your script to change it in your script then regenerate the installation.
 
 
 
This line was replaced
 
     Location := 'Not Registered !!!'   #13#10   'Possible Wrong Crystal Reports Version Installed on Source Machine or '   #13#10   'Wrong CRystal Reports Merge Module Installed on Target Machine'   #13#10;
 
with this one
 
     Result := 'Not Registered !!!'   #13#10   'Possible Wrong Crystal Reports Version Installed on Source Machine or '   #13#10   'Wrong CRystal Reports Merge Module Installed on Target Machine'   #13#10;

Randem

Also on the system you installed your application go to the location where crviewer.dll is installed and attempt to register it then see if you can run your app. I want to see if you register it manually does it work or does your app still complain.

Randem

One difference that I can see is that you are not deploying all of your reports. Another thing is I checked te merge modules for CR 9, 10 and 11 and your files seem to be in between versions 9 and 10. Version 10 files are from 2005 and yours are from 2004. Version 9 files are from 2002-2003, so where did you get your files? You possibly have multiple versions installed along with a update or two but your files do not match any merge module for Crystal Reports.
 
My question has to do with the reports themselves. When you developed them you had to use something to attach to the database in the reports, was that code for the connection string used in the development of the reports?

pepsisc

Randem:
 
I'm not sure if I understand your question however, I am using ADO
Here is the code for my Connection string:
Public Sub OpenConnections()
On Error GoTo ErrorHandler
If OpenConnectionsFlag Then Exit Sub
Set pconSports = New ADODB.Connection
pconSports.ConnectionString = Provider=Microsoft.Jet.OLEDB.4.0;Data Source= & c:\Program Files\Ultimate_Sports_Pool & \Sports.mdb & ;Persist Security Info=False
ReportPath = App.Path
pconSports.Mode = adModeReadWrite
pconSports.Open
Exit Sub
ErrorHandler:
ANS = MsgBox(The database is not available. Ultimate_Sports_Pool will now close. & vbCrLf & _
    Err.Description, vbCritical, Database Error)
End
End Sub
 
I have also experimented by doing the following: I used MS Package and Deployment Wizard and tried to install the output of that. It did install and everything worked including the reports.
I am now going to compare the CAB files against the LOG file. I am sending you a snapshot of the contents of the CAB file. Maybe between you and I we can see what is different. The only problem is this list does not show version numbers.

Randem

No, I am not getting annoyed with your questions. That is the purpose of this forum, to help.
 
Now about your reports... Inside your rpt file how are you accessing the database with the report. That may be where the problem resides. Are you using connection strings? if so what are they. Are they using DAO or ADO etc...
 
As far as the script and the log, everything is happening as it is supposed to crviewer.dll is being registered. My fear is that in your reports you may be referencing a different version of crviewer and that may be the issue.
 
Now with the versions, don't use auto-increment. It will be far simpler.

pepsisc

Randem:
 
To answer your questions: In my VB application, I am using ADO. I have a form that has the CrystalReportActiveViewer. In the Form_Activate event, I have a series if IF...ELSEIF...End statements that look like this (followed by the code I use to call the report viewer.
------------------------------------------
Set craxreport = craxapp.OpenReport(ReportPath & \ & ReportName)
If ReportName = PlayerPick2.rpt Then
        craxreport.FormulaSyntax = crCrystalSyntaxFormula
        craxreport.RecordSelectionFormula = {GamePlayers.WeekNumber} =  & HoldWeekNumber &  and {WeeklyGame.TeamType} = ' & HoldTeamType & '
    ElseIf ReportName = WinningTeam.rpt Then
        craxreport.FormulaSyntax = crCrystalSyntaxFormula
        craxreport.RecordSelectionFormula = {WinningTeam.WeekNumber} =  & HoldWeekNumber &  and {WinningTeam.TeamType} = ' & HoldTeamType & '
    ElseIf ReportName = PoolWinners.rpt Then
        craxreport.FormulaSyntax = crCrystalSyntaxFormula
        craxreport.RecordSelectionFormula = {WeekWinners.TeamType} = ' & HoldTeamType & '
 
    End If
 
DoReport:
    DoEvents
    Screen.MousePointer = vbHourglass
    crViewer1.Refresh
    crViewer1.Zoom 100
    While crViewer1.IsBusy
        DoEvents
    Wend
    crViewer1.ReportSource = craxreport
    crViewer1.Refresh
    crViewer1.ViewReport
    crViewer1.Refresh
    Set craxreport = Nothing
    Screen.MousePointer = vbDefault
End Sub
----------------------------------------------
Attached is the LOG file
 
 
When I mention OUTPUT, I meant to say the OUTPUT DIRECTORY which contains install .exe file
 
As you can see, I am still having a problem with the version. I am using Build 19
I haven't bothered you about it because I got the feeling you were getting annoyed with me.
 
I want you to know, I DO APPRECIATE YOUR HELP.
 
Sam

Randem

Ok, now how are you calling CR in the report? Are you using ADO code or the bound data controls?  
 
BTW, what do you mean take the output file to another PC? Are you installing your app on the other computer? If you are installing it, install it with the /LOG parameter from the command prompt then post the log file that gets generated.
 
/LOG
Causes Setup to create a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.
 
The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
 
The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice.
 
/LOG=filename
Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.

pepsisc

Randem:
 
I am using InnoScript and InnoSetup. I have the following problem when I take the OUTPUT file to a user's PC. The user's PC does not have Crystal Reports or VB on it.
 
The application does install however when they try to access any one of the reports, they are getting the following error:
QuoteRun Time Error 339
Component crviewer.dll or one of it's dependencies not correctly registered: file is missing or invalid.

project file
UltimateSportsPool.pjt (3.1 k)

Randem

If you compile your exe with auto-increment on the version number will increment to the next version. Now when you run InnoScript it will read your VB project file and it will see the next version number (auto incremented) and will use that one. We don't use auto increment for that reason.
 
If you want to use auto increment you will have to re-open the VB project and reduce the number before generating your script with InnoScript (thereby rendering auto-increment useless).
 
Our procedure here is to not use auto increment and after script generation with InnoScript we then open the VBP file and bump the version number after deploying the installation.  
 
It's all in the process you want to use...
 
There was a bug in build 18 and you should upgrade to build 19 to fix the issue with version numbering.