Hedie1 Absent Member.
Absent Member.
2890 views

[SCEM] send failure, -1, 2

08/13/09 08:59:55 -- [CW] send failure, 4440, 0, -1, 2
08/13/09 08:59:55 -- [PCGI] done, PROXY_CMD_GET_IMAGE
08/13/09 08:59:55 -- [SCEM] send failure, -1, 2
08/13/09 08:59:55 -- [LC] close connection, xxx.xxx.xxx.xxx
08/13/09 08:59:55 -- [ECC] CS

I get this EVERY time i try to restore an image.

I took the image without hustle but now i get this after about 10minutes, its at the same time every single time i try it.

I tried 2 computers at the same time just now, i got different times, 2:49 on PC1 and about 4:30 at PC2.

I use ZCM 10.2 with the June update to Preboot.

ZCM Webinterface says: Novell.Zenworks.Prebootwork.ERRMSG_IMGERR_IMAGE_FILE_INACCESSIBLE
Labels (2)
0 Likes
7 Replies
Hedie1 Absent Member.
Absent Member.

Re: [SCEM] send failure, -1, 2

I found another line in the that might be useful:
08/14/09 11:25:24 -- [CW] send failure, 4440, 0, -1, 2

It would be most useful to hear from ppl that are having the same problem.

Ive tried to rollback to the PXE Evironement before the june update, still the same problem BUT 08/13/09 08:59:55 -- [SCEM] send failure, -1, 2 becomes 08/13/09 08:59:55 -- [SCEM] send failure, -1, 0.

Ive changed the timeout for packets in TFTP settings. not helping.
This morning i got to about 90% of restoring a computer then it happened again.

Ive tried 2 different images on 2 different computers (same model tho, HP 6730b) which ends up with the same error.

What should i do?
0 Likes
Hedie1 Absent Member.
Absent Member.

Re: [SCEM] send failure, -1, 2

I tried to take an image today and it was successful. No problems at all.

But i cant restore and image.


No one else has this problem?
0 Likes
Knowledge Partner
Knowledge Partner

Re: [SCEM] send failure, -1, 2

Hedie;1841924 wrote:
I tried to take an image today and it was successful. No problems at all.

But i cant restore and image.


No one else has this problem?


We have imaged (Windows XP) many HP 6730b without any problems. What OS do you try to image?

Thomas
0 Likes
Hedie1 Absent Member.
Absent Member.

Re: [SCEM] send failure, -1, 2

Windows XP SP3 - the image is about 6,5GB
0 Likes
Knowledge Partner
Knowledge Partner

Re: [SCEM] send failure, -1, 2

Hedie;1841939 wrote:
Windows XP SP3 - the image is about 6,5GB


Okay ours are bare WINXPSP3 about 1GB.

You could try going into bios and disable all power saving stuff and also enable FAN when connected to AC and see if it helps.

Thomas
0 Likes
Hedie1 Absent Member.
Absent Member.

Re: [SCEM] send failure, -1, 2

After addind the IP of the zenworks server into the configfiles instead of the standard answer and a reboot of all the services, we successfully restored an image.

However, restoring the image to another 6730b did not work. same error as before.

Gonna try the powersaving stuff now.
0 Likes
Hedie1 Absent Member.
Absent Member.

Re: [SCEM] send failure, -1, 2

Hedie;1840358 wrote:
08/13/09 08:59:55 -- [CW] send failure, 4440, 0, -1, 2
08/13/09 08:59:55 -- [PCGI] done, PROXY_CMD_GET_IMAGE
08/13/09 08:59:55 -- [SCEM] send failure, -1, 2
08/13/09 08:59:55 -- [LC] close connection, xxx.xxx.xxx.xxx
08/13/09 08:59:55 -- [ECC] CS

I get this EVERY time i try to restore an image.

I took the image without hustle but now i get this after about 10minutes, its at the same time every single time i try it.

I tried 2 computers at the same time just now, i got different times, 2:49 on PC1 and about 4:30 at PC2.

I use ZCM 10.2 with the June update to Preboot.

ZCM Webinterface says: Novell.Zenworks.Prebootwork.ERRMSG_IMGERR_IMAGE_FILE_INACCESSIBLE



After a bright idea from a collegue (he just came back from vacation), we checked the switches and noticed a large amount of CRC errors on a forwarding port. This can, in our case, be cause by a faulty configured port. The thing here was that the switch was set to Auto-speedsense which can cause problems on the model of switches we use.

Setting the port to 100 FDx fixed the problem! We have restored alot of images since we changed this and all have been successful.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.