Crystal Report - Error 2705
Hi,
I was trying to package Crystal Reports XI Release 2 using Wise. Everything goes smoothly. I able able to create the MSI without any errors.
When I try to install from the MSI , i get an error - "Internal error 2705 : Directory". I looked up in the help index and found that error 2705 is due to invalid table. It did not make any sense to me.
Could any one of you shed more light to the problem. Thanks in advance.
Regards,
Nilo
I was trying to package Crystal Reports XI Release 2 using Wise. Everything goes smoothly. I able able to create the MSI without any errors.
When I try to install from the MSI , i get an error - "Internal error 2705 : Directory". I looked up in the help index and found that error 2705 is due to invalid table. It did not make any sense to me.
Could any one of you shed more light to the problem. Thanks in advance.
Regards,
Nilo
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
(sigh) Google, anyone? Search term "windows installer" +2705 produces this http://support.installshield.com/kb/view.asp?articleid=Q107991 as the first hit .
You have an entry in the Directory table which is referencing a non-existent entry in that or a related table. Your authoring tool is probably able to highlight the error in some way. Wise, for example, has 'Setup Editor' view, in which you can view the tables directly. It displays cells in error in red.
You have an entry in the Directory table which is referencing a non-existent entry in that or a related table. Your authoring tool is probably able to highlight the error in some way. Wise, for example, has 'Setup Editor' view, in which you can view the tables directly. It displays cells in error in red.
Posted by:
AngelD
16 years ago
If I'm not misstaken, "Crystal Reports XI Release 2" is already in the MSI format.
Use a transform for any modification if required.
Use a transform for any modification if required.
Posted by:
Coriolus
16 years ago
Aye, don't repackage this one. Do a silent install and all should be fine.
Posted by:
sumitsingh1984
16 years ago
Hi All,
Even i have repackaged this application .
when i install the msi(repackaged one) it gives error 1935.
Since the msi which is present in the setup.exe dont install all the shortcut as well it does not take /qb! command .
Also when i try to install using ADDLOCAL=ALL property it gives some minmit30.dll issue.
Thats why i have gone for repakaging this app.
Any suggestion is appreciated..
Thanks and regards
sumit
Even i have repackaged this application .
when i install the msi(repackaged one) it gives error 1935.
Since the msi which is present in the setup.exe dont install all the shortcut as well it does not take /qb! command .
Also when i try to install using ADDLOCAL=ALL property it gives some minmit30.dll issue.
Thats why i have gone for repakaging this app.
Any suggestion is appreciated..
Thanks and regards
sumit
Posted by:
nilo
16 years ago
Hi,
Thank you all for your feedback. I have been able to solve the Error 2705. It indeed had a wrong reference in the Directory table.
But I am facing another issue. I get an Error 1911. It seems to be a registry problem.
I have packaged this app using Wise Package Studio. Please provide your feedback.
Regards,
Nilo.
Thank you all for your feedback. I have been able to solve the Error 2705. It indeed had a wrong reference in the Directory table.
But I am facing another issue. I get an Error 1911. It seems to be a registry problem.
I have packaged this app using Wise Package Studio. Please provide your feedback.
Regards,
Nilo.
Posted by:
Coriolus
16 years ago
It probably doesn't take the /qn or any other MSI switches becuase you are not using the correct command line syntax:
InstallShield with MSI Recent versions (7 and above) of InstallShield's tools are able to produce MSI files. Read InstallShield's documentation for full details. These MSI files may be shipped alone or with a setup.exe installer. These installers in turn come in two flavors, called "InstallScript MSI" and "Basic MSI". InstallScript MSI uses the traditional InstallShield switches. Basic MSI is another story. To perform an unattended installation using a Basic MSI installer, you provide the /s /v"..." switches, where ... represents any additional switches you want to pass down to msiexec. These should include the /qb (or /qn) switch to make the installation non-interactive, so a minimal invocation would be: setup.exe /s /v"/qb"
InstallShield with MSI Recent versions (7 and above) of InstallShield's tools are able to produce MSI files. Read InstallShield's documentation for full details. These MSI files may be shipped alone or with a setup.exe installer. These installers in turn come in two flavors, called "InstallScript MSI" and "Basic MSI". InstallScript MSI uses the traditional InstallShield switches. Basic MSI is another story. To perform an unattended installation using a Basic MSI installer, you provide the /s /v"..." switches, where ... represents any additional switches you want to pass down to msiexec. These should include the /qb (or /qn) switch to make the installation non-interactive, so a minimal invocation would be: setup.exe /s /v"/qb"
Posted by:
anonymous_9363
16 years ago
I have packaged this app using Wise Package Studio.WHY? It's already an MSI. How many times - don't, don't, DON'T re-package MSIs!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.