Error 1720 when installing Cisco VPN client

[aroko56]

I am trying to install Cisco VPN client on a windows XP pro machine, but it
wouldn’t install it (although I’ve installed the same package on other XP
machines many time with no problem) the error is “error 1720 there is a
problem with this windows installer package. A script required for this
install to complete could not be run, contact your support personal or
package vendor) the file is on the local disk and, I tried installing Script
5.6 but no luck, Any idea?

PS I tried different version of the packages, but no luck

 

[Andrew McLaren]

I am trying to install Cisco VPN client on a windows XP pro machine, but it
wouldn’t install it (although I’ve installed the same package on other XP
machines many time with no problem) the error is “error 1720 there is a
problem with this windows installer package. A script required for this

I'd really recommend you contact the Helpdesk for the VPN network you
plan to connect to. The exact answer to your problem will depend a lot
on the exact version of VPN Client you are trying to install; and
whether you had any previous Cisco VPN client software installed. The
Helpdesk guys will probably be familiar with all the common problems;
they can also open a ticket with Cisco Support, if necessary. Debugging
many problems with Cisco client requires access to tools and docs which
you get with the Cisco physical software media, or which you need a
Cisco customer ID to download from the Cisco website (ie, not freely
available).

In general terms ... the 1720 error is a pretty generic MSI Installer
error, it could be caused by many things. If you have an actual MSI
file, you can generate a log file with this syntax:

C:\>msiexec /i <filename.msi> /l*vx somename.log

This will create a text log file called somename.log (or any other name
you want to use). Inspect it using Notepad. It will give more detailed
information about what, exactly, is failing.

However, this only works if you have an MSI file. As I recall, the Cisco
VPN Client comes wrapped up in an EXE file, so you can't easily pass
command-line parameters to the MSI. If you can extract teh MSI from the
EXE wrapper, then you can run it from msiexec, with logging turned on.

Or, um, ask your Helpdesk

Other folks might have extra ideas. Hope this helps a bit,

Andrew

 

[aroko56]

Thanks for the quick reply Andrew, but i am help desk guy my self i
installed the same VPN client on many XP professinal machine, but never seen
of encountered any error messages during the installation, and Unfortunately
i dont have any support contract with Cisco, but maybe i can try to install
it with that syntax and see what happens.

Thanks again

 

[Andrew McLaren]

"aroko56" wrote

Thanks for the quick reply Andrew, but i am help desk guy my self i

Doh!! Don't you just hate it, when that happens?

Anyway I did find some online info at the Cisco site, about how to turn on
Setup logging:

http://www.cisco.com/en/US/docs/sec...pn_client500_501/administration/5vcAch12.html

This is pretty much what I described below but in more detail; and, it
implies that there is (or should be) a vpnclient_en.msi file you can use.

This won't SOLVE the probelm, as such; but the log file will give you a much
better insight into what specifically is failing. And then you can
troubleshoot it from there.

Keep an eye out for standard Windows error codes in the log, such as
0x00000005 (== "access denied") etc. If you see this one, for example, you'd
probably have some kind of permissions problem. And so on.

Good luck, hope you get it solved!

Cheers
Andrew

 

[Cisco_VPN]

Hi.
I had same error (Cisco VPN Client 5.0 error 1720) and find a solution:
check/fix/repair WMI service.
On my friend laptop (XP with SP3) the WMI service crashed, and obviously
Windows Firewall crash too (it depends om WMI service). Actually I spotted
first the firewall/ICS malfunction and later the WMI service problem:
completly missing from list of services!
To fix WMI / reinstall WMI I used all methods posted on
http://windowsxp.mvps.org/repairwmi.htm
and managed to fix my WMI - and as soon as WMI was back I managed to finish
the Cisco VPN install.
It appears that Cisco install uses WMI scripting.
For me only last repairing method worked: the complete one

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

Good luck.

PS: I believe that my WMI crashed as soon as I installed .NET 3.5 (I needed
in order to make PrimoPDF to work). Is just a guess...nothing sure.