ASA firmware upgrade from console - tftp error

Have an asa 5510, trying to upgrade the firmware via console.
I have a tftp program installed on my PC but get an error running the command, any idea what I'm doing wrong?
asa# copy tftp flash
Address or name of remote host [142.xx.xx.xx]? ------------> IP of my PC
Source filename [asa912-k8.bin]?
Destination filename [asa912-k8.bin]?
Accessing tftp://142.xx.xx.xx/asa912-k8.bin...
%Error opening tftp://142.xx.xx.xx/asa912-k8.bin (No such device)

Hi,
You really cant upload files through the Console connection. Its not a network connection.
Your PC might have an IP address configured but that would be configured in its network interface card which has nothing to do with the console cable connection.
So you will have to configure one of the ASAs network interfaces with IP address and other basic settings. Then you need to configure the PCs network interface cards settings to match the IP address/subnet configured on the ASA. Then you will have an connection between the ASA and the PC and should be able to load the software to ASA.
For example
interface Management0/0
nameif management
security-level 100
ip address 10.10.10.1 255.255.255.0
no shutdown
and the configure the PC with IP address 10.10.10.100 and mask 255.255.255.0 for example and then load the software from the PCs IP address of 10.10.10.100.
- Jouni

Similar Messages

Firmware upgrade from 2.1(3a) to 2.1(3b).

I don't find any documentation on the web for firmware upgrade from 2.1(3a) to 2.1(3b)..
is it wise to follow this link http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/upgrading/from1.4/to2.1/b_UpgradingCiscoUCSFrom1.4To2.1.html
Any best practices ?

I would consult
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/firmware-mgmt/gui/2.1/b_GUI_Firmware_Management_21.pdf
Cisco UCS B-Series GUI Firmware Management Guide, Release 2.1First Published:
Last Modified: July 12, 2013November 16, 2012

SPA112 firmware upgrade from 1.0.1 to 1.2.1 kills the SPA

I took a brand-new, unconfigured SPA112 out of the box, plugged it into DHCP-enabled network, noted it was running v1.0.1 firmware and attempted a firmware upgrade to 1.2.1 via the web management utility.
After reporting a successful upgrade there was no further response from the SPA112 to HTTP requests, neither was there any response to pings. ARP requests are responded to successfully. The IVR works (as well as the IVR ever works) until I selected to perform a factory reboot at which point the IVR stopped responding as well. Holding the reset button for 20sec does nothing useful. It's dead, Jim.
I've had this experience on another SPA112 as well under similar circumstances although there is nothing in the Release Notes for v1.2.1 to say that such an upgrade does not work.
My questions:
1)Is there any way of recovering these devices or do I need to send them back to Cisco?
2) How am I supposed to perform such a firmware upgrade?

Hi Matthew,
I tried upgrading the firmware upgrade from v1.0.1 to v 1.2.1 and I had the same problem. The device just stopped responding. I tried that in a lab and I figured out what exactly to do when you get in to a problem like that. So lets start off once again.
Snce SPA112 must get an IP first through a DHCP on WAN port. Connect the SPA 112 device according to the instructins told in this article till the step 3.
http://www6.nohold.net/CiscoSB/Loginr.aspx?login=1&pid=4&app=search&vw=1&articleid=2775
Once you access the web GUI of SPA112 follow the contents of the following article and upgrade the firmware
http://www6.nohold.net/CiscoSB/Loginr.aspx?login=1&pid=4&app=search&vw=1&articleid=2676
In your case I believe the window got stucked at the point when it says "The upgrade is successful" and then there was no further response to HTTP requests.
Restart the device and see if it works or not. If it does not then log in to the router web GUI and navigate to the ARP table and see what are the VLAN assigned to the IP address.
NOTE: Both the router and SPA should be in the same VLAN. This way only the device will respond to the HTTP requests. If they are in a different VLAN's, navigate to the VLAN and disable the LAN memberships. For example there are two VLAN ID 1 and 100. Disable the LAN ports for the ID 100 and only enable it for 1.
Navigate to the ARP table again and refresh it. Both the IP addresses should be in the same VLAN. If yes. Access the SPA112 with an IP address assigned to it again and navigate to Administration > Firmware Upgrade. You will see the firmware of the device has been upgraded.
(optional) Upgrade the firmware again. This time, it will go through and the device will restart.
Let me know if you still need any help.

WRK54G firmware upgrade fails: file pattern error.

When I attempt to upgrade the firmware in my WRK54G router, the upgrade fails with this error message:
Upgrade action is not finish!!
Upgrade file pattern error.
The linksys download page says the file size is 1.10 MB.
The size of the file I downloaded (WRK54Gv2_1_00_1) is also 1.10 MB (1,160,036 bytes). So it appears the file was downloaded successfully.
I had no problem upgrading the firmware to version 1.1.
Please advise.
Thank you

What is the hardware version of your router? Is it version 1, version 1.1 or version 2? Where did you download the firmware of your router? Is it from the US website.
On the US website you have 3 wrk54g, one is version 1, version 1.1 and v2.
"When love and skill work together, expect a masterpiece."

ASA Firewall Upgrade from 8.2,8.4, to 9.0

Dear All ,
we have five firewalls with the following details:
First Firewall
Hardware:   ASA5550, 4096 MB RAM, CPU Pentium 4 3000 MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
    my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
Second Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.2(3) ,Device Manager Version
6.2(3)
my question can i upgrade ASA IOS 8.2(3) to 9.0 directly without any issues also can i upgrade Device manager 6.2(3) to 7.0 without upgrading the       ASA IOS itself
Third Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
Fourth Firewall
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.4(3) ,Device Manager Version 6.4(7)
my question can i upgrade ASA IOS 8.4(3) to 9.0 directly without any issues also can i upgrade Device manager 6.4(7) to 7.0 without upgrading the       ASA IOS itself
fifth Firewall:
Hardware:   ASA5520,2048 MB RAM, CPU Pentium 4 2000MHz, Flash 256MB , BIOS Flash1024KB , ASA IOS 8.2(3) ,Device Manager Version 6.2(3)
my question can i upgrade ASA IOS 8.2(3) to 9.0 directly without any issues also can i upgrade Device manager 6.2(3) to 7.0 without upgrading the       ASA IOS itself
please help i am doing the upgrading remotely using the ASDM and i don't want to do any upgrade could result disconnectivity.
Best regards

Hi Basel,
Honestly, I wouldn't suggest a direct upgrade from 8.2 to 9.0. This is a *major* upgrade. The recommended path to reach 9.0 would be from 8.2-->8.4-->9.0
Here are the release notes for 9.0:
http://www.cisco.com/en/US/docs/security/asa/asa90/release/notes/asarn90.html#wp690047
Per above document:
If you are upgrading from a pre-8.3 release, see also the Cisco ASA 5500 Migration Guide to Version 8.3 and Later
for important information about migrating your configuration.
Once you are on 8.3/8.4 (I would suggest 8.4 as a lot of issues were fixed post 8.3 as that was a huge transition from 8.2) upgrade to 9.0 is fairly simple.
Major part is upgrade from 8.2 to 8.4 as configuration changes and few things can be broken as a result. I would highly recommend you to check these docs before attempting an upgrade and also do it with some maintenence window so as to correct things in case they broke:
Following doc talks about 8.3 but it is applicable to direct upgrade to 8.4 as well:
https://supportforums.cisco.com/docs/DOC-12690
Release notes for 8.4:
http://www.cisco.com/en/US/docs/security/asa/asa84/release/notes/asarn84.html
Sourav

ASA 5520 upgrade from 8.4.6 to 9.1.2

Dear All,
I am having ASA 5520 in Active Standby failover configuration . I want to know if I can upgrade it from 8.4.6 to 9.1.2 using the zero downtime upgrade process mentioned on cisco site .
Below is the process :
Upgrade an Active/Standby Failover Configuration
Complete these steps in order to upgrade two units in an       Active/Standby failover configuration:
Download the new software to both units, and specify the new image to           load with the boot system command.
Refer to           Upgrade           a Software Image and ASDM Image using CLI for more           information.
Reload the standby unit to boot the new image by entering the           failover           reload-standby command on the active unit as shown           below:
active#failover reload-standby
When the standby unit has finished reloading and is in the Standby           Ready state, force the active unit to fail over to the standby unit by entering           the no           failover active command on the active unit.
active#no failover active
Note: Use the show             failover command in order to verify that the standby unit             is in the Standby Ready state.
Reload the former active unit (now the new standby unit) by entering           the reload command:
newstandby#reload
When the new standby unit has finished reloading and is in the           Standby Ready state, return the original active unit to active status by           entering the failover           active command:
newstandby#failover active
This completes the process of upgrading an Active/Standby Failover       pair.
Also after upgrade are there any changes required after IOS migration ( i.e are there any changes in the command line of 8.4.6 and 9.1.2 )
It is mentioned on cisco site that
Major Release
—You can upgrade from the last minor           release of the previous version to the next major release. For example, you can           upgrade from 7.9 to 8.0, assuming that 7.9 is the last minor version in the 7.x           release.

Hi Tushar,
The steps you mentioned are perfectly fine. There is no major difference in the commands of the 2 versions, it's just that in access-rule from 9.1 you have to any4 instead of any for ipv4 and any6 for ipv6. During conversion it will get convert automatically.
Also, please refer to the following document (release notes of 9.1.2) for viewing the new features added in that version:
http://www.cisco.com/en/US/docs/security/asa/asa91/release/notes/asarn91.html#wp685480
- Prateek Verma

Listener actually up as seen from backend but from console gets error

Hi
My SCAN listener is shown running from backend but is shown down from console.
response for listener shows below error.
Any suggestions/hints
Thanks
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 06-JUNE-2011 11:44:54 Copyright (c) 1991, 2010, Oracle. All rights reserved. Welcome to LSNRCTL, type "help" for information. LSNRCTL> Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1))) TNS-12541: TNS:no listener TNS-12560: TNS:protocol adapter error TNS-00511: No listener Linux Error: 2: No such file or directory LSNRCTL>

Thank you for your help.
I am using a RAC database and this is the status
srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabled
SCAN listener LISTENER_SCAN1 is running on node oradb123
SCAN Listener LISTENER_SCAN2 is enabled
SCAN listener LISTENER_SCAN2 is running on node oradb124
SCAN Listener LISTENER_SCAN3 is enabled
SCAN listener LISTENER_SCAN3 is running on node oradb124
srvctl config scan_listenerSCAN Listener LISTENER_SCAN1 exists. Port: TCP:1730
SCAN Listener LISTENER_SCAN2 exists. Port: TCP:1730
SCAN Listener LISTENER_SCAN3 exists. Port: TCP:1730
[ oradb469:/home/oracle ]
srvctl config scanSCAN name: oemcrsp-xyz.net, Network:
1/10.180.5.0/255.255.255.0/eth0
SCAN VIP name: scan1, IP: /oemcrsp-xyz.net/10.180.5.186
SCAN VIP name: scan2, IP: /oemcrsp-xyz.net/10.180.5.187
SCAN VIP name: scan3, IP: /oemcrsp-xyz.net/10.180.5.185

Running package programmactically from console causes error if package uses connection in Connection Manager.

Hello my friends:
I attempted to run a few packages programmatically using the code and solution on this page:
http://msdn.microsoft.com/en-us/library/ms136090.aspx
I observed that the script and process failed when I use the connection in SSIS/SSDT connection Manager in Visual Studio 2013. Meaning if I create a Connection for the Project in the Connection Manager and use it on tasks.
However, the project and packages will run just fine if I simply add individual connection to each task where needed and do not use the Connection manager.
If I use the Connection Manager, I get this error: This only happens when I run the package programmatically,
if I run the package directly from Visual Studio, I get no errors.
Error Message:
Error in Microsoft.SqlServer.Dts.Runtime.Package/ : The connection "{0E6E938E-B0
84-45E6-9110-0D532BD61787}" is not found. This error is thrown by Connections co
llection when the specific connection element is not found.
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/SSIS.Pipeline : Cannot find th
e connection manager with ID "{0E6E938E-B084-45E6-9110-0D532BD61787}" in the con
nection manager collection due to error code 0xC0010009. That connection manager
is needed by "SQL Server Destination.Connections[OleDbConnection]" in the conne
ction manager collection of "SQL Server Destination". Verify that a connection m
anager in the connection manager collection, Connections, has been created with
that ID.
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/SSIS.Pipeline : SQL Server Des
tination failed validation and returned error code 0xC004800B.
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/SSIS.Pipeline : One or more co
mponent failed validation.
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/ : There were errors during ta
sk validation.
Connection Manager Screenshot:
I am using that connection in an SQL Server Destination Task:
And here is the code:
class Program
class MyEventListener : DefaultEvents
public override bool OnError(DtsObject source, int errorCode, string subComponent,
string description, string helpFile, int helpContext, string idofInterfaceWithError)
Console.WriteLine("Error in {0}/{1} : {2}", source, subComponent, description);
return false;
static void Main(string[] args)
string pkgLocation;
Package pkg;
Application app;
DTSExecResult pkgResults;
MyEventListener eventListener = new MyEventListener();
pkgLocation =
@"C:\Users\Administrator\Desktop\ExampleConnectionMgr\DataExtractionB.dtsx";
app = new Application();
pkg = app.LoadPackage(pkgLocation, eventListener);
pkgResults = pkg.Execute(null, null, eventListener, null, null);
Console.WriteLine(pkgResults.ToString());
Console.ReadKey();
Thank you everyone!

I have confirmed that this problem, at least on the surface is caused by the lack of reference to the Connection in the Connection Manager as indicated by the error message.
The solution here will require that the Connection is set directly within each task.
If I simply set the connection in each task then the page runs just fine programmatically:
I am also able to convert the Connection in the Connection Manager to Package Connection as shown in the screen shot below. This will override all references to the Connection Manager and make the connection local within each package or package
task.
Is there any other solution out there?
Thanks again!
Synth.
This is exactly what I asked for in my previous post. Sorry if it wasnt clear.
I guess the problem is in your case you're creating connection manager from VS which is not adding any reference of it to packages which is why its complaining of the missing connection reference
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page
Hi my friend:
Do you know how I can include the connection programmatically in code?
I found this article but it is not very clear to me:
I do not want to create a package in code, just the connection so that the program can run.
Here is the article:
http://msdn.microsoft.com/en-us/library/ms136093.aspx
Thank you so much.
Patrick

How the heck do i get a firmware upgrade from my computer to the router?

I went to this site here to try and make my router work. It is a WRT54GS wireless router, and I saw where i could download some firmware upgrade, so I clicked on it and saved it to my desktop. It is a .bin file. Now how do I get that file to the router?????
The router was working until today and now it isn't sending out a wireless signal. However, it is still connecting my computer to the internet through its wire (modem to router, router to computer with cable). But when I open the Easylink software, it says that the internet connection is not working, even though the little green light is on for "wireless" on the front of the router.
But anyway, how do I get this downloaded file onto the router??? There isn't any usb ports on the router to connect to it. There isn't anything in the Easylink software that gives me that option, or if there is they hid it pretty good. They really should explain how to do this, or do they expect everyone to have a degree in networking or computers or something? I need some help here

As sabretooth suggested,Open an Internet Explorer browser page on a computer hard wired to the router...In the address bar type - 192.168.1.1...Leave the Username blank & in Password use admin in lower case...Click on the 'Administration' tab- Then click on the 'Firmware Upgrade' sub tab- Here click on 'Browse' and browse the .bin firmware file and click on "Upgrade"...
Wait for few seconds until it shows that "Upgrade is successful" After the firmware upgrade, click on "Reboot" and you will be returned back to the same page OR it will say "Page cannot be displayed".
Now,Press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...

Firmware upgrade from Verizon has caused errors.

I am unable to see contacts or use the phone. Contacts: application people (process com.android.htc contacts) has stopped unexpectedly. Phone: process android.process.acor has stopped unexpectedly.

Hard Reset is suggested....
http://community.vzw.com/t5/Android-Apps/After-the-Update-Somthing-to-consider/td-p/642367

ASA 5520 Upgrade From 8.2 to 9.1

To All Pro's Out There,
I have 2 x ASA 5520 in Active/Standby state (Routed, Single context) running 8.2(3) image. They are working great and everybody is happy. Now it's time for us to upgrade to the latest and greatest version: 9.1 and as you know there are some architectural changes Cisco made to NAT statements and Access Lists. As one can tell, we have a monster environment in terms of NAT statements and access list that are currently configured on the appliances.
In order to make the upgrade process "less" painful, I was able to find a loaner ASA 5520 device so I can practice the upgrade process offline and if needed, I use it in production (in conjunction with existing Primary and Secondary devices) should it be helpful. I currently don't have any plans on how to move forward with these 3 devices and put together an smooth upgrade. I am asking advice from experts that perhaps have done this in the past and know some Do's and Don’ts and can provide me some options toward getting best result: Minimum downtime and Smooth upgrade.
I appreciate all the help in advance.

Hi,
My personal approach from the start has been to learn the new NAT configuration format on the ASA CLI and manually convert the configurations for the new ASA software. I am under the impression that the automatic conversion that the ASA does by rebooting straight into a new software level causes quite a lot of configurations and they arent really optimal.
In your case it seems that you have a pretty much better situation than most people that dont have the chance to use a test device to test out the setup before actually putting it in production.
What you can basically do is
Insert the 8.2 configuration to the test ASA and boot it straight to the higher software levels and see what the conversion has done to the ASA configurations.
You can use "packet-tracer" command to test if correct NAT rules are still hit after the conversion
So far I have been lucky in the sense that most of the upgrades I have done have involved new hardware which has basically let me configure everything ready and just switch devices for the customer. So far everything has went really well and there has been only a 1-2 mistakes in NAT configurations because of misstyping some IP address or interface name which basically resulted from a lot of copy/paste when building the configurations. And these couple of mistakes have been from around 150 firewall migrations (of which most from FWSM Security Context to a ASA Security Context)
If you have time to put into this then I would suggest you try to learn the new NAT format and write your NAT configurations yourself. Converting the existing configurations should essentially give you the tools to then maintain that firewall configuration easily in the future and apply that knowledge elsewhere.
If you want to read a bit about the new NAT configuration format then I would suggest having a look at the NAT 8.3+ document I made:
https://supportforums.cisco.com/docs/DOC-31116
My personal approach when starting to convert NAT configurations for the upgrade is
Collect all NAT configurations from the current ASA including any ACLs associated with the Policy type NATs and NAT0 configurations
Divide NAT configurations based on type
Dynamic NAT/PAT
Static NAT
Static PAT
NAT0
All Policy Dynamic/Static NAT/PAT
Learn the basic configuration format for each type of NAT configuration
Start by converting the easiest NAT configurations
Dynamic NAT/PAT
Static NAT/PAT
Next convert the NAT0 configurations
And finally go through the Policy NAT/PAT configurations
Finally go through the interface ACLs and change them to use the real IP address as the destination in all cases since the NAT IP address is not used anymore. In most common screnarios this basically usually only involves modifying the "outside" interfaces ACL but depending if the customer has some other links to external resourses then its highly likely that same type of ACL changes are required on those interfaces also.
The most important thing is to understand how the NAT is currently working and then configure the new NAT configuration to match that. Again, the "packet-tracer" command is a great tool to confirm that everything is working as expected.
One very important thing to notice also is that you might have a very large number of Identity NAT configurations between your local networks interfaces of the ASA.
For example
static (inside,dmz) 10.10.10.0 10.10.10.0 netmask 255.255.255.0
In the new software you can pretty much leave all of these out. If you dont need to perform NAT between your local interfaces then you simply leave out all NAT configurations.
Naturally you can also use these forums to ask help with NAT configuration conversions. Even though its a very common topic, I dont personally mind helping out with those.
So to summarize
Try out the ASAs automatic configuration conversion when simply booting to new software levels on the test ASA you have
Learn the new NAT configuration format
Ask for help here on CSC about NAT configuration formats and help with converting old to new configurations.
Personally if I was looking at a samekind of upgrade (which I will probably be looking at again soon) I would personally do the following
Convert the configurations manually
Lab/test the configurations on an test ASA
During Failover pairs upgrade I would remove the Standby device from network, erase its configurations, reboot it to new software, insert manually written configurations.
Put the upgraded ASA to the device rack and have cables ready connected to the customer devices if possible (or use existing ones)
Disconnect currently active ASA running 8.2 and connect the new ASA to the network while clearing ARP on the connected routers to avoid any problems with traffic forwarding.
Test connectivity and monitor ASAs connection and xlate tables to confirm everything is working
Will add more later if anything comes to mind as its getting quite late here
Hope this helps
- Jouni

BEFW11S4 v4 firmware upgrade from 1.45.3 to 1.52.02 failing

I've been having some problems with my router resetting so I decided to upgrade the firmware. I'm currently on version 1.45.3, Jul 1 2003 and I wanted to update to 1.52.02 4/07/2005. I downloaded befw11s4_v4_v1.52.02_000_FCC_code.bin from Linksys' site and selected it at http://192.168.1.1/Upgrade.htm. The progress bar will start to move and when it reaches about 75% I'm redirected to http://192.168.1.1/Upgrade.cgi which is a blank white screen . If I go back to http://192.168.1.1/ and check the firmware version I see 1.45.3 still. Does anyone have any idea what is going wrong?
Solved!
Go to Solution.

So I just went ahead and called the dreaded customer service.....turns out the filename just needs to be changed. There are 3 easy steps to fix this problem.
1. If its on your desktop the name should appear as BEFW11S4-v4_v1.52.02_fw,0 change it to befw11s4_v4_1.52.02_000_FCC_code.bin
2. Go to your upgrade firmware screen, click browse to get the file with the new name
3. Click upgrade and be happy that it worked!!

CF8 upgrade from Cf7 causing error

Okay, i've done plenty of CF7 to CF8 upgrades and I have
never seen this issue. I run the autoplay,.exe and InstallAnywhere
launches and I make it to the language select screen and click
okay, About 3/4 of the way through the next status bar. I get a
Fatal Application Error pop-up box stating This Application has
Unexpectedly Quit. Invocation of theis Java Application has caused
an InvocationTargetException. This application will now exit (LAX).
The details button then states this:
java.lang.NumberFormatException: For input string: "wo"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.valueOf(Integer.java:526)
at java.lang.Integer.decode(Integer.java:918)
at ZeroGia.a(DashoA8113)
at
com.zerog.ia.installer.util.magicfolders.JavaHomeMF.b(DashoA8113)
at
com.zerog.ia.installer.util.magicfolders.MagicFolder.initializeAllMagicFolderPaths(DashoA 8113)
at com.zerog.ia.installer.LifeCycleManager.j(DashoA8113)
at com.zerog.ia.installer.LifeCycleManager.h(DashoA8113)
at com.zerog.ia.installer.LifeCycleManager.a(DashoA8113)
at com.zerog.ia.installer.Main.main(DashoA8113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.zerog.lax.LAX.launch(DashoA8113)
at com.zerog.lax.LAX.main(DashoA8113)
The installation log shows this: (no errors)
Fri Jul 18 08:49:14 CDT 2008
Free Memory: 9485 kB
Total Memory: 27388 kB
java.class.path:
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData\IAClasses.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jdglue.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData\Execute.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\InstallerData\Execute.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData\Resource1.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\InstallerData\Resource1.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\InstallerData
ZGUtil.CLASS_PATH:
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData\IAClasses.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jdglue.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData\Execute.zip
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\InstallerData
sun.boot.class.path:
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\resources.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\rt.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\sunrsasign.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\jsse.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\jce.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\charsets.jar
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\classes
java.ext.dirs:
C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre\lib\ext
C:\WINDOWS\Sun\Java\lib\ext
java.version == 1.6.0_01 (Java 1)
java.vm.name == Java HotSpot(TM) Client VM
java.vm.vendor == Sun Microsystems Inc.
java.vm.version == 1.6.0_01-b06
java.vm.specification.name == Java Virtual Machine
Specification
java.vm.specification.vendor == Sun Microsystems Inc.
java.vm.specification.version == 1.0
java.specification.name == Java Platform API Specification
java.specification.vendor == Sun Microsystems Inc.
java.specification.version == 1.6
java.vendor == Sun Microsystems Inc.
java.vendor.url ==
http://java.sun.com/
java.class.version == 50.0
java.compiler == null
java.home == C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows\resource\jre
java.io.tmpdir == C:\DOCUME~1\SCHOOL~1\LOCALS~1\Temp\1\
os.name == Windows 2003
os.arch == x86
os.version == 5.2
path.separator == ;
file.separator == \
file.encoding == Cp1252
user.name == school%world
user.home == C:\Documents and Settings\school%world
user.dir == C:\Documents and Settings\school%world\Local
Settings\Temp\1\I1216388864\Windows
user.language == en
user.region == null
Nothing was installed.
Installed by InstallAnywhere 8.0.1 Enterprise Build 3080, by
Macrovision
User Interactions
Summary
Installation: Successful
This is a client's server so I have limited knowledge of
configuration that isn't obvious. I did notice that outbound port
80 seems to be blocked as I can't hit web pages from the server,
but DNS resolution works. Inbound port 80 is obviously open because
the current sites running on this server are reachable. I also
noticed FuseTalk is installed Any pointers as to what the issue
might be would be very helpful.
Thanks

booster94 wrote:
> Any pointers as to what the
> issue might be would be very helpful.
>
> Thanks
The first suggestion is to check the Actual File Size and MD5
Checksum
of the file. Assuming you are installing from a download file
as is
common, the file may be incomplete.
The ColdFusion Download page provides the expect values.
http://www.adobe.com/cfusion/tdrc/index.cfm?product=coldfusion

Doesn't Upgrade from 6.16: Error 1603

Hi, I am using windows 7, and I keep on getting message to upgrade to new version of skype, but when I does Error message appears
THE OLDER VERSION OF SKYPE 6.16 CANNOT BE REMOVED. CONTACT YOUR TECHNICAL SUPPORT. installing skype failed code 1603
Solved!
Go to Solution.

techfreak wrote:
mark2adw wrote:
I have the same problem & I'm running Windows XP Pro.
My Skype version is 6.11.0.112 & will NOT update,
The MS Fix It can not resolve the issue.
I never had any issues or upgrading problems with Skype until Microsoft took control of Skype.
Microsoft owning Skype has never affected any of my installs any differently, so I struggle to see any direct correlation. If you are unable to upgrade you should be able to safely uninstall 6.11 then install the latest version and that should not affect anything. I occasionally have had to do this with Skype releases old and new. It generally stems from the various builds that come out (msi, exe, business msi, etc.) sometimes making a direct upgrade impossible.
If after uninstalling 6.11, traces of Skype remain, the Microsoft Fix it tool should be able to help.
Skype 6.16
http://download.skype.com/msi/SkypeSetup_6.16.0.105.msi
Thanks, but your download will not open, see attached screen shots.
Skype "Help / About", says that I am running version 611.0.102,
But when I run MS Fix It, the installed Skype version is 6.6 that cannot be uninstalled.
When I open "Add Remove Programs", I can not remove or uninstall Skype manually.

NAC firmware upgrade from 4.1.3 to 4.7 or 4.8, anyone?

I currently have 1 CAS 3310 Failover Bundle for Wireless user, and 1 CAM Lite Failover Bundle for management.
ACAS, CAM and Clean Access Agents are running 4.1.3. We are considering an upgrade in particular because some end-users machine are soon to be Windows 7. Our authenticaion for users is provided by AD SSO.
I would like to know your experience when doing such a major jump (4.1.3 to 4.8.1). Looking for gotchas and known issues. Also what the incremetal upgrade path look like.
I was thinking we can go 4.1.3 -> 4.6.1-> 4.8.1. Any other way or recommendation. CIsco is highly recommending we go to 4.8.1 if all possioblem.
I am also aware that we need to create new root certificates.
Appreciate input.
Thanks,
Rosa

Hi,
Yes, that is the correct upgrade path: 4.1.3 -> 4.6.1 -> 4.8.1.
I would recomend you to go through the Release notes for 4.6.1 and 4.8.1 for all the known gotchas and detailed upgrade process.
Gotchas/changes/upgrade process for 4.6.1: http://www.cisco.com/en/US/docs/security/nac/appliance/release_notes/461/461rn.html#wp65900.
Gotchas/changes/upgrade process for 4.8.1:http://www.cisco.com/en/US/docs/security/nac/appliance/release_notes/48/481rn.html#wp65900.
Regarding the certificates, you should not use the self signed certs due to security reasons, and they should only be used for lab purposes.
This means that it still works with the self signed, but you need to import the CAS cert into the CAM trusted certification authorities and vice-versa, so that the CAM trusts the CAS cert and vice-versa.
HTH,
Tiago
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

ASA firmware upgrade from console - tftp error

Similar Messages

Maybe you are looking for