I have developed an msi package of the Oracle8i client 8.1.7.0.0
But when I install the msi file I get an errormessage at the end of the installation about the sqresus.dll, followed by the statement that the Oracle ODBC driver could not be installed.

Any ideas how to tackle this problem?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

1
Just a Guess but see if the dll is in the selfreg table. If so remove it as it is not a registerable file and is no required to be registered.

Regards,
Answered 11/20/2003 by: Robo Scripter
Orange Senior Belt

Please log in to comment
1
Previously when I created an MSI for Oracle 8.1.7, I had trouble using the proper ODBC tables to create the ODBC DSNs etc.

I think the problem was that the windows installer engine actually loads the ODBC driver to process the ODBC tables. In the case of the Oracle package, the process that the Oracle ODBC driver is loaded into does not have the Oracle bin directory in its path, so the driver cannot be loaded properly. A chicken and the egg sort of problem.

I resorted to setting up the ODBC by writing directly to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC - it is not as elegant but it worked.
Answered 02/05/2004 by: mrtap
Senior Yellow Belt

Please log in to comment
1
Greetings all!

(Windows 2000, Oracle 8.1.7)

I, too, had the problem of the my MSI created for depoying Oracle 8i barfing when it came time to install the Oracle ODBC driver.

(Barfing = showing an error saying that it could not find a resource dll - sqora32.dll and/or sqoras32.dll).

I solved it by updating the PATH before deploying the package.

I added "C:\Oracle\Ora81\Bin" to the beginning of the path variable.

A reboot was NOT necessary.

On W2K, when I tried to update the path from within the MSI, no matter HOW I tried to do it (Custom Action, etc.), while the path DID get updated, the MSI itself would not see the change.

It's as if the MSI gets the value of the PATH variable at the very beginning of its execution, and never looks at it again to see if it gets updated.

At first, I just wrote a quickie little pre-launch MSI that updates the path, but for the ease of use of the install techs, I'll write a little Wise Script exe that does the same thing and which then launches the proper MSI (we want to make this as easy as possible for our techs, yes?)

Hmmnn - I think I'll paste that script in here... if you're using Wise, just copy and paste the following into a blank Script Editor.

You can use this as a stand-along script or to create a Custom Action.

If you see ways to improve this script, by all means, paste a reply with the changes! :)



item: Remark
Text=Initialize Variables
end
item: Set Variable
Variable=CURRENTPATH
end
item: Set Variable
Variable=NEWPATH
end
item: Remark
end
item: Remark
Text=Get current path
end
item: Get Registry Key Value
Variable=CURRENTPATH
Key=SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Value Name=Path
Flags=00000100
end
item: Remark
end
item: Remark
Text=Set path to lowercase (for matching)
end
item: Set Variable
Variable=CURRENTPATH
Value=%CURRENTPATH%
Flags=00011100
end
item: Remark
end
item: Remark
Text=Add to path if entry does not already exist
end
item: If/While Statement
Variable=CURRENTPATH
Value=c:\oracle\ora81\bin
Flags=00000011
end
item: Set Variable
Variable=NEWPATH
Value=C:\oracle\ora81\bin;%CURRENTPATH%
end
item: Edit Registry
Total Keys=1
Key=SYSTEM\CurrentControlSet\Control\Session Manager\Environment
New Value=%NEWPATH%
New Value=
Value Name=Path
Root=2
end
item: End Block
end
Answered 03/04/2004 by: sean_c_roberts
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity