Solaris boot images fail with bad magic number
hi guys, have had Solaris on boxes for allmost 10 years. I have never installed sol10, and I have a problem
1. I download the zip file, then use winrar to unzip them..
2. burt the image with nero 7
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt
I do boot cdrom
this fails with "bad magic number" I have redown loaded it and reburnt it with nero reinstalled
and also changed out the DVD on SunBlade
3 I found a copy of Solaris 8 and the I got back a 'bitch' where is Solaris 9 so, most likely the drive is OK
HELP
Cris Harrison
Hello Cris,
unfortunately I don't understand your last sentence !
I found a copy of Solaris 8 and the I got back a '*****' where is Solaris 9 so, most likely the drive is OK
If this was a Solaris 8 (7/01 or later) DVD that did successfully boot, your DVD drive firmware (assuming that this is the Sun Toshiba SD-M1401) is up-to-date. If the DVD drive has firmware 1007, an update to 1009 is required to boot from DVD. otherwise you won't be able to boot from DVD (boot from CD works and a DVD can be automounted/mounted).
Partial output of probe-scsi
Before update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
After update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
[*Patch 111649-04 - Toshiba DVD 1401 firmware update*|http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&queryKey5=111649&toDocument=yes]
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt ...
Instead of trying to directly boot, disable auto-boot and retry after a clean power-on.
Break with Stop-A
setenv auto-boot? false
reset-all
boot cdrom
Michael
Similar Messages
-
Ifconfig pcelx0 plumb fails with Bad file number error
Hi,
I installed solaris 8 (x86) on a Toshiba Tecra 8000.
The Tecra uses Neomagic NM2200 chipset for it's display.
Even though it is not supported by the Sun Drivers, getting xfree86 for sun fixed the display problem for me.
Now according to the various sources that guided me in this task seemed to point at a few things that I had to do in order to make the Tecra work okay with Solaris 8 :
1)Change the PCMCIA mode in the BIOS from automatic to PCIC mode
2)Make sure that there were no IRQ conflicts on the system.
3)Install the OS.
Once the OS was installed, I ran prtconf -D and saw that the network instance #0 pcelx0 was showing up under pcic.
I did not have to install the xig init-pcic patch.
But it did not create an entry in /devices or /dev (as a link) with the error
"pcelx0 requested IRQ failed 6".
Also, I suppose that is the reason why when pcelx0 is plumbed, it comes out with the error message:
ifconfig pcelx0 plumb : "bad file number"
Any help will be greatly appreciated.
Thanks,
Dwai.Thanks Alex,
I found out -
ifconfig adapter plumb will fail with Bad File number error when the device file that is being referred to is missing.
I checked and found that the pcelx link is not being made in the /dev directory and the file not created in /devices.
I also found that when /reconfigure is run, it tries to create the device for pcelx but fails with this eror message:
pcelx : RequestIRQ fail 6
I am assuming that there is some IRQ conflict with some other device.
Thanks,
Dwai. -
Fsck fails with bad inode number 0 to ginode
Hi,
I'm trying to repair a ufs filesystem on Solaris 10 but it keeps failing with the message:
bad inode number 0 to ginode
Does anyone know how to get around this issue?
Thanks,
TedI had this identical failure and the only solution I found anywhere was to format the drive, but I tried an alternate strategy which worked..
The inode failure repeated during Phase 3 of fsck. I answered NO, to the Reconnect prompts during that Phase, and answered Yes to the Phase 4 & 5 prompts. After serveral fsck runs, Phase 4 & 5 errors were all fixed. On the next run of fsck, Phase 3 also passed - the bad inode error was gone.
I could then mount the drive READ/WRITE and restore a corrupted library file. The server then booted up clean.
The fix took less than 30 minutes...much better than the nuclear option! -
Image Capture Boot Image Fails with 0xc000000f
I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?Hi,
We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
So far, I found two other posts with exactly the same issue:
1) http://wp.secretnest.info/?p=1474
2)
http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.
So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in
system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
I used BCDEDIT to show the differences between the working and non-working boot images:
Windows Boot Loader
identifier {1d214c07-6892-401c-a762-04647ad38560}
device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
961-85dd-a10f3c46473f}
description Windows 7 Boot Image
osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
-- Second - Non Working disk --
Windows Boot Loader
identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
b86a3a-3651-4f50-a748-34f3e784158c}
description Windows 7 Capture
osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon. -
T6340 cannot boot disk - Bad magic number in disk label
Hi,
I have a shiny new T6340 that I am just setting up.
When I get through the CMM to the SP and onto the EEPROM,
I then try to start the boot process:
{0} ok boot disk1
Sun Blade T6340 Server Module, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 130848 MB memory available, Serial #76313344.
Ethernet address 0:14:4f:8c:73:0, Host ID: 848c7300.
Boot device: /pci@500/pci@0/pci@9/@0/disk@1 File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Evaluating:
Can't open boot device
{0} ok show-disks
a) /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@5/disk
c) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@1/disk
q) NO SELECTION
Enter Selection, q to quit: q
{0} ok boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
Boot device: /pci@500/pci@0/pci@9/LSILogic,sas@0/disk File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Can't open boot device
{0} ok This is a brand new B6000 system and has not been booted before.
Please tell me what I need to do to enable the disks, so I can do the next bit!
rachel@rachel,
In your original post you showed a screen capture of what you tried.
First you typed "boot disk1". ( Why disk1? Why not disk0?)
When that didn't seem to work, you displayed the disks recognized by the system at OpenBoot.
The first of those disks was a device path of
/pci@500/pci@0/pci@9/LSILogic,sas@0/disk{code}
and so you attempted to boot from that but omitted whatever slice might be the boot slice of a factory preinstalled OS. For example...
{code:java}
boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk@0,0{code}
(just guessing at what could be that bootable slice).
What happens if you simply type "*boot*" when you are at OBP? -
JVM issue with applet - Duplicate Key in Parameter Table - Bad Magic Number
Hey, I have Googled this one to death and have seen a few vague references to this problem, but nothing I can relate back as solution.
I wonder if I need to tell the customer to reinstall the OS and, ultimately, the JRE. I'm just looking for a little guidance on what any of you may think. Am I missing a setting or something?
The user is trying to download an applet with IE with 1.3.1_16 and Firefox 1.07 with the Java Embeded Plug-in.
Even though JRE 1.3.1_16, 1.4.2_09 and 1.5 are all installed and Firefox has the JEP also installed, Firefox still wants to use 1.3.1_16 as does IE. I'm guessing that the JEP didn't work.
They can't use Safari which does seem to be using 1.4.2_09 because their RSA ID won't authenticate through it.
On my machine, when I run with the same OS,browsers, and Java 2 plug-ins, I can successfully load the applet.
This is the error that the user gets in the java console is:
Duplicate key in parameter table: code using the htmlAttribute.
first: com.ibm.eNetwork.HOD.HostOnDemand
second: com.ibm.eNetwork.HOD.HostOnDemand.class
java.lang.ClassFormatError: com/ibm/eNetwork/HOD/HostOnDemand (Bad magic number) at java.lang.ClassLoader.defineClass0(NativeMethod)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)...
Would you reinstall the OS and Java? or look at another setting? or look at the JEP installation again?
Thank you.Without reading the full post (sorry for that) my guess is that the applet needed to be fetched through a
proxy, the proxy corrupts the applet because it's signed (finjan is one that does that).
The reason why a proxy would do so is because the default settings of sun jre will ask the user the
"do you trust" question to the user which could result in the user loading an applet that is allowed to do
anything the programmer wants (4us, spyware, nasty stuff).
Try to do the following:
1. create a html file locally with the following content:
rightclick and save target as
2. open the page, right click the link and save the file
3. apen the file with an unzip programm (winzip) and check if the content has changed.
4. If the content has changed than the proxy might have done this, contact the system administrator
It might allso have been done by a firewall installed locally. -
Yet another question about "bad magic number error"
I have acquired a Sun Blade 1000 w/o installed OS and a set of genuine Solaris 10 media. As a Solaris neophyte I'm either being stupid or I've got a real problem and I can't tell which. So help would be greatly appreciated.
With the sparc disc in, if I let the machine start up I get a common error message for used sun kit:
Bad magic number in disk label
Can't open disk label package
Boot device: net File and args:
Timeout waiting for ARP/RARP packet
I stop-a and try to boot from the sparc disc and get the error message:
Boot device: /pci@8,7000000/scsi@6/disk@6,0:f File and args: -s
Bad magic number in disk label
Can't open disk label package
Can't open boot device
Using probe-scsi-all shows the Seagate HDD (LiD: 1 HA: 1 LUN: 0 ...), /scsi@6,1, and the Toshiba DVD-ROM (/scsi@6). If the DVD drive is done in how can I tell and what are the specification I need to look for in a replacement?
nullHello "null",
please check if the data cable to the DVD is properly attached.
Some early versions of the Toshiba DVD drive won't boot from a DVD due to outdated firmware (1007).
Review the version (either 1007 or 1009) in the probe-scsi-all output. If the drive currently uses the old firmware,
the fix is to update the drives firmware (1009), which indeed requires an installed Solaris. The updated DVD firmware is contained in patch 111649-02.
If the firmware is uptodate and you have access to CD media (Solaris 9 or 10) you can the try to boot from
Solaris 9 Software 1 or Solaris 10 CD 1.
If no CD media is available, just download the image file of CD 1 from the download center and burn a CD (slower burning speed recommended). Boot from this CD into single-user mode (boot cdrom -s). If this succeeds, download the other CD images and use them to install Solaris.
As a replacement drive any SCSI DVD that can be jumpered to 2048 byte blocksize works.
Michael -
Sun Ultra 25 - Bad magic number in disk label
I have a Sun Ultra 25 SPARC that is booting fine to it's 80GB SATA drive. Solaris 10, OpenBoot 4.22.19.
Here's what I did:
I installed a 2TB Western Digital SATA drive into the HDD1 slot.
I formatted the disk in the HDD1 slot via the format command, labeled the disk, and divided it into partitions.
I then used newfs to build the ufs on all partitions.
I mirrored the disk in HDD0 to the disk in HDD1 using ufsdump for all partitions. The data is accessible and looks ok.
After this was done I did an installboot to /dev/rdsk/c1t1d0s0 (the / partition of the HDD1 slot).
I then did a fsck on every partition to verify that they are okay.
I then took the hard drive in HDD1 and put it in the HDD0 slot, now wanting to boot off that disk.
At the reboot:
Bad magic number in disk label
Can't open disk label package
If I do a probe-scsi:
MPT Version 1.05, Firmware Version 1.08.03.00
Target 0
Unit 0 Disk ATA WDC WD20EADS-00R0A01 3907029168 Bocks, 2000 GB SATA device PhyNum 0
As far as I can tell disk0 is the correct devalias which is:
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/disk@0,0
I just don't understand how the fsck is okay, but the boot give bad magic number in disk label?
The 80GB drive in HDD slot 0 works fine with the boot disk0 command, all I'm doing is swapping a larger disk with the same data for the smaller disk.if it is like any other Sun product, it needs to go through the format command and get a volname.... it is just a label, but it needs to be done.
haroldkarl -
Bad magic number in super-block while trying to open /dev/sda2
hello,
So I've a linux partition, and then I wanted to install a Windows copy. I've only 1 HDD with differents partition into it:
sda5 (swap)
sda6 /user
sda7/var
sda8 / (which contain the boot and root of course)
sda3 /home
sda2 NTFS (windows xp)
So, as I had linux installed before windows, I had to make my sda2 NTFS (87) under my cfdisk. Then, I went to install windows, everything worked fine, windows booted with his boot system, but I had to restore grub with my archlinux live cd:
grub> find /boot/grub/stage1
grub>root (hd0,7)
grub>setup (hd0)
everything worked successfully, my grub loaded till while booting archlinux I got this error:
couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What I tried is to run the e2fsck -b 8193 /dev/sda2 but right after that, I thought about it, this isn't linux partition so of course, the superblock isn't the same as they are ntfs type from widnows?
I've read on some forum but unfortunately didn't solve my problem, if anyone has any suggestion before I format the NTFS partition, I'd really appreciate it.
best regards, mazwhat I think it happened, is that after installing windows your partitions numbers got twisted a bit. What you have to do is to edit /etc/fstab, and check out your linux and swap partitions mounting entries, I believe you just have to change the number of /dev/sda[number] coresponding to your linux partition in fstab
If you can't solve it, post the output of
fdisk -l
and
cat /etc/fstab
Last edited by I'mGeorge (2011-07-21 20:53:31) -
Bad Magic Number in Disk Label & DiskSuite
Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the disks has bad magic number in its disk label. The slice was in a mirror. DiskSuite has hot spares and one of them took over the failed slice. I am trying to figure out how to get it back to where it was.
I think I should use 'format' to recover the disk label from the backup label. However, once the label is recovered, how do I make it stop using the hotspare and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new to Sun/Solaris and I just took over the E450.
Thanks,Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the
disks has bad magic number in its disk label. The
slice was in a mirror. DiskSuite has hot spares and
one of them took over the failed slice. I am trying to
figure out how to get it back to where it was.
I think I should use 'format' to recover the disk
label from the backup label. However, once the label
is recovered, how do I make it stop using the hotspare
and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new
to Sun/Solaris and I just took over the E450.
Thanks,Since the host spare took over then you're free to repair/replace the bad drive. In this case you could check the drive using format and partition to view the partitions. If the label is bad then I would suspect the drive is still good and a simple format>label and save command would repair the label. Then once this is done if all goes well then the system should rebuild the drive and the hot spare will not longer be used. The system should regonize the drive as a replacement and rebuild it then stop using the hot spare.
Michael -
OCFSV2 : mount.ocfs2: Bad magic number in inode
Hi everyone,
DUe to high load I/O, i can't mount my ocfsV2 partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information
marge:~# fsck.ocfs2 /dev/sdc1
fsck.ocfs2: Bad magic number in inode while initializing the DLM
The disk is an iscsi device, there are no block damaged.
I try to modify the signature with bvi but the result is the same.
The disk containt image file created with dd (Virtual machine).
Do you have a software or a workaround to recover my vm's ?
Or i must consider to format my parttion ?
Thank youI know , i wan't to switch to Linux forum but how to do that ? :-)
marge:~# modinfo ocfs2
filename: /lib/modules/2.6.26-2-xen-amd64/kernel/fs/ocfs2/ocfs2.ko
license: GPL
author: Oracle
version: 1.5.0
description: OCFS2 1.5.0
srcversion: C692B48692BFC8597E4D7A7
depends: jbd,ocfs2_stackglue,ocfs2_nodemanager
vermagic: 2.6.26-2-xen-amd64 SMP mod_unload modversions Xen
I created the filesystem with debian :
mkfs.ocfs2 /dev/sdc1
By default it create 4K cluster size. And it make 6 backup off superblock.
But recover superblock doesn"t work :
marge:~# fsck.ocfs2 -r 1 /dev/sdc1
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup block#262144? <n> y
fsck.ocfs2: Bad magic number in inode while initializing the DLM
marge:~# debugfs.ocfs2 -R stats /dev/sdc1
Revision: 0.90
Mount Count: 0 Max Mount Count: 20
State: 0 Errors: 0
Check Interval: 0 Last Check: Thu May 7 16:26:37 2009
Creator OS: 0
Feature Compat: 1 BackupSuper
Feature Incompat: 16 Sparse
Tunefs Incomplete: 0 None
Feature RO compat: 1 Unwritten
Root Blknum: 5 System Dir Blknum: 6
First Cluster Group Blknum: 3
Block Size Bits: 12 Cluster Size Bits: 12
Max Node Slots: 4
Label:
UUID: 3677066B5C7B424BB79FE30764552B57
Cluster stack: classic o2cb
Inode: 2 Mode: 00 Generation: 3020404948 (0xb407b8d4)
FS Generation: 3020404948 (0xb407b8d4)
Type: Unknown Attr: 0x0 Flags: Valid System Superblock
User: 0 (root) Group: 0 (root) Size: 0
Links: 0 Clusters: 52432135
ctime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
atime: 0x0 -- Thu Jan 1 01:00:00 1970
mtime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
dtime: 0x0 -- Thu Jan 1 01:00:00 1970
ctime_nsec: 0x00000000 -- 0
atime_nsec: 0x00000000 -- 0
mtime_nsec: 0x00000000 -- 0
Last Extblk: 0
Sub Alloc Slot: Global Sub Alloc Bit: 65535
debugs say superblock is ok but unable to mount the partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information -
E2fsck: Bad magic number in super-block
e2fsck: Bad magic number in super-block while trying to open /dev/hda1
Yup, a very tricky one this is. I did the following:
[root@(none)~]#e2fsck /dev/hda1
e2fsck 1.40.2 (12-jul-2007)
/dev/hda1: clean, 310310/4702208 files, 8118002/9396009 blocks
What can I do to fix the super-block? I unable to boot up my system right now, and I can't afford to format my disk.
I have systemrescuedisk with the TestDisk application at hand(if needed?).B wrote:There is a backup superblock every 8192 blocks if i'm correct. So the next one is at 8193. Try telling e2fsck to use that to fix your partition.
I've tried that, with no luck I'm afraid. So I've gotten more serious and.
With Testdisk I managed to indentify these superblocks.
[Superblocks] where * means it has been e2fsck'ed
0, blocksize=4096*
32768, blocksize=4096*
98304, blocksize=4096*
163840, blocksize=4096*
229376, blocksize=4096*
294912, blocksize=4096*
819200, blocksize=4096*
884736, blocksize=4096*
1605632, blocksize=4096*
2654208, blocksize=4096*
umount /dev/hda1
e2fsck -b 32768 /dev/hda1
/dev/hda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
<4 minutes later>
I get the question:
Free inodes count wrong for group #1 (ie. 32254, counted=231)
Fix<y>? y
This question got repeated #286 times, where I answered the same (y) each time.
/dev/hda1: ********* FILE SYSTEM WAS MODIFIED ************
/dev/hda1: ********* REBOOT LINUX **************
/dev/hda1: 310310/4702208 files (1.5% non-contiguous), 8118002/9396009 blocks
So i rebooted... but still the same error occurs during kernel boot. So now I figured I had
to do the same with 98304 and so forth. YUP! I was right, this superblock was dirty too.
e2fsck -b 98304 /dev/hda1
answer yes to all. Reboot, and repeat with 162840. Until your kernel manages to mount
your disk cleanly and hopefully boot up.
Sadly when I e2fsck -b 98304 /dev/hda1 yet again just to check, it still claims to be dirty.
Now I'm kinda back to where I started.
I will look further into if testdisk can provide some automagic solution to my problem.
Pointers is apprecieted! -
Bad Magic Number error trying to deploy WAR file from Netweaver Studio
We hae an application that runs fine as a WAR in both Tomcat and Weblogic and we are trying to deploy it on Netweaver. I tried both to use the External deployment archives and the Workspace Deployable Archives. In both cases, the deployment fails with error:
Bad magic number, found 0x80CCF1C3, expected 0xCAFEBABE.
I know the server is working because I can deploy a very simple test application with no errors. The server is a new installation of 7.1.
Any help on how to get past this error or how to troubleshoot further is appreciated.Looks like it's complaining about a missing shared library. Check weblogic.xml for library-ref elements and make sure the domain you are deploying to has those libraries deployed.
-
I have an applet that i am trying to load in a JSP
<applet name="MyTestApplet" code="mypackage.MyTestApplet.class" >
</applet>
mypackage/MyTestApplet.class is under the approot/pages directory and the jsp is also in the same directory.
whenever the jsp is called and applet does not get inited and the error i see is a ClassFormatError: Bad magic number
Please help.. this is extremely urgent.
Thanks in advance for any input anyone may have.
The appserver i am using is SunONEFirst the <applet tag is depreciated, you should use <object instead (w3c has depreciated applet for quite
some time now).
When I see the tag you don't use a jar package (archive is missing) so let's pretend the url to your page is
http://mysite/mypage.jsp
the mypage.jsp contains the applet so the url to the applet is:
http://mysite/mypackage/MyTestApplet.class
can you download the file using a browser?
you can do this by saving the following line in a html file and right click it then sava target
right click and save target as
After downloading is the file the same as the file on the web server?
The reason I ask this is because I got the bad magic number when a jar was loaded through a proxy.
The proxy did something with the jar file making it corrupt. I think your problem has something to do with
the way your web server is serving the applet or (proxy) something between the client and the server. -
We recently updated all of our servers with the new ZDM7NWSP1IR4HP1. We distributed the zenworks update through our zenworks for servers so we downloaded the CPK files. Updates were successful except now we have lost our reimage on next boot functionality on all servers. We get the message "imaging failed with error 175". We downloaded and tried the Zenworks Imaging Driver Update for October 2009. We tried this on one server in our environment that we use for testing purposes. This did not fix the problem.
Can anyone help us? We don't see anything additional on the support site to patch.Originally Posted by spond
Busytech710,
could you please
1) boot to ZENworks maintenance mode
2) export DEVELOPER_LOG=a
3) perform the imaging task and send me the imglog
spond at novell dot com
Shaun Pond
I will be glad to try this and send you the log. I too tried installing the service pack with winsetup.exe and found that also worked for me as far as making image on next boot work. We really want the CPK method to work as we have so many servers and we were able to update them all in one day versus weeks using winsetup.exe. I'll respond back with info you need as soon as possible.
Maybe you are looking for
-
Importing songs from a library on the same computer
i have 2 itunes libraries on one computer, is there a way to add songs from one library to another without burning a cd?i know you can add folders to libraries, is there a way to make a folder? thanks in advance
-
Can someone help please
-
Database Error while refreshing webi report
Hi, I am getting following error while refreshing webi report. And also all my scheduled webi reports are getting failed because of same issue. What would be the reason for this error. Regards, PRK
-
Hi, I'm having the following configuration: K8Dmaster F, dual AMD opteron 1,60 GHZ, 1 GB RAM, serial ATa Adaptech 1210 SA card, Seagata 110 GB, CDROM. When I try to install Win2000/XP, after I format the partition from setup, I got the same error alw
-
Purchased ProCam XL 2 online this afternoon. Filled in all the boxes. Clicked OK. No download. No app. No confirmation. No email. Help.