Video Screencast Help

Altiris 7.5, Unable to create Windows 7 Ent. x64 image

Created: 14 Oct 2013 • Updated: 14 Oct 2013 | 40 comments

Hello;

 

Last week I upgrded from Altiris 7.1 to version 7.5 and now I am having issues capturing Windows 7 image.  My captures fails with the following error:

"ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP status 500. Invalid data received in HTTP response. Expected 3441 bytes, received 0. Error Description is utilCSMPPackagecallDSPSInfoOperationService. Value of Windows error code = 183 and message is Cannot create a file when that file already exists."

 

Not sure at this point.

 

Any ideas?

 

Thank you

 

Operating Systems:

Comments 40 CommentsJump to latest comment

HighTower's picture

I moved this thread to the Deployment forum.

burndtjammer's picture

Is your source machine a VM?  Im running in to a similar issue (error text at bottom).  I dont have time to wait for support so I mapped a network share in PE and ran ghost64 with the cmd line that the capture image task had in the ghsterr files.

 

The logs are in the following directory, they will have more details that can maybe help you or support

 x:\program files\symantec\deployment\logs

so i did

net use w: \\networkserver\share

then

x:\program files\symantec\deployment\ghost\ghost64.exe -z3 -batch -sure -clone,mode=create,src=1,dst=w:\cache\win7_entp_x64_10152013.gho

 

I will then use the resource import tool to bring it in. I am not sure sure why the compression is z3.  I told the task to "optimize for size" which should have used -z9 (at least thats what id use when using straight up ghost 5 years ago).  Maybe ill run it again with -z9 and see if it creates a smaller image file.

 

 

ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File Tcube_ClientCaptureImage.cpp at Line No 829. Type of exception is ClientCaptureImageException. Error Description is Child Process returned an error. The exit code from process is 1. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

burndtjammer's picture

-z3 gave me an image that was 12.6GB and -z9 gave me a 12.3 image.  Not a huge size difference considering how big it already is because of the WoW features added to an x64 image.

jpellet2's picture

This is how we do it all the time. I don't understand why the built-in tasks can't handle UNC paths even now. We have broken both the create image and deploy image tasks apart and capture and deploy manually to UNC paths so we don't have to have the disk images sitting on the NS or a package server or anywhere else. The command-line that you have used is the one that we also use.

Zagrosman's picture

Well, I am new to Altiris.  I am switching over from KACE KBOX to this software.  So, not sure why I have to do all this to make an image to work!

I under stand you are doing this manually and the import part.  But, is there a hotfix or a patch or something that could be done to correct this issue?

 

And, thank you everyone for replying and giving me your ideas.  :)

 

burndtjammer's picture

It should be working as engineered and shouldnt rely on workarounds. Sadly, I think both of us need to open up support cases.  Not only will it fix our issue(s) but it could also lead to hotfixes or updates being released for everyone if they see it to be a widespread issue. I have other projects to work on and higher ups dont understand that you have people or teams dedicated to indivdual areas.  Having to spend time on the phone with support ruins 2-3 days that can be spent on other projects. This is not a problem exclusive to symantec, just me venting.  Thank you.

 

If the workaround works for you let support know. Keep in mind it may not and you have to look through your logs to see if it points to something specific.  I really wish they had kept deployment shares like they were in 7.1 but i do like the increased capabilities, options and logging.

Thomas Baird's picture

There are a couple of possibilities you may want to uh - peek at.

 

1) if you're not in a .COM environment, we may have problems with HTTP imaging.  Note that we'll fail-over to UNC, unless you're required to be secure and/or have UNC blocked and/or have UNC codebases not being returned via the console.  We have a known issue around domains that are NOT .Com.

2) There's a possibility that the site server / package server is missing the Deployment virtual folder.  Check to be sure it's there.

 

We are short a bit of info in this thread.  What kind of task?  UNC or HTTP for instance?  If the above information doesn't help. you may want to supply us with a bit more information to try and help.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

burndtjammer's picture

What is the location of the deployment virtual folder?

Zagrosman's picture

Hello;

 

The .com was not an issue when we were using Altiris 7.1, however once we upgraded to 7.5 this issue started.  Now, we are not a .com.  We are an education system, so we are a .k12.us.ga.us . We cannot change that.  Not everyone is a .com.

The package server appears to be fine. 

As far as UNC or HTTP; I am not capturing or doing anything manually.

I am using Altiris automation tasks to do a simple oporation and that is:

1. Prepar for image capture; which works fine.

2. Create an image!  This is where it does not work.

Not sure why...

 

 

 

 

 

 

 

 

Thomas Baird's picture

Perfect information.

Do you know if, in the console, you have done anything to restrict the codebases sent to package servers for packages?  Forget Deployment for a moment - there is a page in the console where you can return UNC & HTTP codebases to all clients.  By default, both are selected.

 

After the Create Image task, are you performing a Reboot to Production task?  If so, what happens if you remove it?

 

Does Ghost run at all when you attempt this task?  That is, if you're watching the system, does Ghost at least start and run, even if for only a while?

 

Finally, where does this error appear - which log or on the screen?

 

Thanks!!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

Zagrosman's picture

Hello again;

 

There are no other tasks after create an image task.  Ghost does not run at all!

The error appears in "Task Instance Details" of the machine that I am trying to capture. This is the complete error:

ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP status 500. Invalid data received in HTTP response. Expected 3441 bytes, received 0. Error Description is utilCSMPPackagecallDSPSInfoOperationService. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

 

Thank you

 

Thomas Baird's picture

Well.  I'm sorry - I don't know that one.  Not that I really want to, but you may need to call it in.  <sigh>

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

Zagrosman's picture

Yeah, I called support.  Let's see what happens.

Tony.Richmond's picture

Did you get anywhere with support on this issue?

Tony.Richmond's picture

Zagrosman,

Did you contact support and if so did they come up with a soluition to this?

 

I have exactly the same issue. I'm getting really tired now of upgrading Altiris to resolve existing issues only to find that is stops previously working tasks from working again.

I've gone from 7.0 to 7.1 to 7.1 SP2 and now 7.5.

 

If it wasn't for the fact that 6.9 didn't like Windows 7 / Server 2008 and above I would have stuck with that as at least it worked correctly. I also had to manuualyy install the SBS (Symantec Boot services) as it wouldn't deploy at all from the consoles Site Servers settings and that took soem digging around on here to find the solution.

 

Might have to call Support again myself but I really can't be bothered to fight all the problems with this product. Hopefully when we come round to renew we can look at other offerings from other vendors, there has to be something more reliable out there!

ocastaneda's picture

Has anyone made any progress on this?

Thanks.

Oscar H. Castañeda

Technical Solutions Consultant

XCEND Group Inc. -- Symantec Platinum Partner

ocastaneda's picture

I noticed my error is a bit different that the one that is listed here.

ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP status 401. Invalid data received in HTTP response. Expected 1293 bytes, received 0. Error Description is utilCSMPPackagecallDSPSInfoOperationService. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

Any thoughts?

Thanks.

Oscar H. Castañeda

Technical Solutions Consultant

XCEND Group Inc. -- Symantec Platinum Partner

Zagrosman's picture

Hello Everyone;

 

My issue has been resolved.  After talking with Symantec Support, we found out Altiris on my NS was using .net 4!

Basically, Altiris still uses .net 2! We changed IIS setteings to use .net 2.  Once we did that, it all started working.

 

The crazy thing I don't undestand is; While I was using 7.1, everything was working.  After we upgraded to 7.5 it started using .net 4.

Something to look at.

 

I hope this helps

 

Thank you

ocastaneda's picture

I attempted to verify if this was the same issue I had encountered but it seems we were already using .Net 2 and .Net 4 was not installed at all.

Curious if anyone else has encountered this issue and resolution as well?

Thanks,

--Oscar

Oscar H. Castañeda

Technical Solutions Consultant

XCEND Group Inc. -- Symantec Platinum Partner

Thomas Baird's picture

I remeber that .NET call.  Fascinating.

Keep bringing those issues into support for now.  We need to document these messages, get them into KB's, and get them into DEV.  I know that for most of us out here in the forums, NOT calling in is the goal, but it helps us, especially with you "early adopters" of the upgraded product.

Thanks!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

Tony.Richmond's picture

In my case the app pool is still using .net v2 so there has been no change there.

I have already made sure the Altiris site is using the 'Classic .NET AppPool' rather than the 'DefaultAppPool' as it was after the upgrade and also got it running under a new AD service account.

Just wondering if trying to run it under .NET 4 instead of 2 (the reverse of the previous posts) would change anything??

Thomas Baird's picture

BTW, a 401 status is "access denied" indicating a problem with security.  I'm... thinking that's not the problem, or is indirect, but it could be.  Custom certificates maybe?  Modified SSL settings (e.g. not using port 443)?  I don't know.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

James Machamer's picture

Same here issue here when trying to capture an image:

 

ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP status 404. Invalid data received in HTTP response. Expected 1547 bytes, received 0. Error Description is utilCSMPPackagecallDSPSInfoOperationService. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

Richard Hosking's picture

Getting the same error. Any progress on this?

I did try switching to RapiDeploy and it worked with that tool.

Thomas Baird's picture

Almost always, this error happens because the DSPS (Deployment Solution Package Services) are not properly installed on the target package server for the image.  I'm trying to get a KB launched on this right now, so stay tuned and watch the Recommended Reading list for the update today or tomorrow.

 

Sorry for the delay.  We're starting to get caught up.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

AMilbut's picture

Getting the same issue.  I am from a NON .com environment.  Using .Net 2 not 4.

Using RDeploy works.

Thomas Baird's picture

I repeat - we can easily dup the 183 error by pulling the stuff in IIS added by the DSPS site server components. There maybe other iterations of this but it all comes down to an IIS problem with the DSPS components.

We are working on a KB for this.

We have some issues we are chasing along those lines where they may not install correctly but show installed in the agent. Check for these under the altiris/ps folder in IIS. If they are not added or not working (eg .net problem) then you will get a 183 error. Look for the KB.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

BPaulson's picture

We were seeing the same or similar error in our environment and it turned out to be a bad driver reference in the DeployAnywhere database.

Every time we tried to run a OS install task we would see the following error in the failed task status:

ErrorMessage: Exception has occured in File SMPPackage.cpp at Line No 679. Type of exception is GeneralError. Error is HTTP error 404 Not Found. Error Description is utilCSMPPackageGetMultiplesFileFromHTTP. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

We looked at the DSTasks.log (x:\program files\altiris\deployment\logs\) on the computer where the task was failing and found this in the log:

[2013/11/26 15:41:12.302 1228:236 2] tcube::ClientSOI::ExecuteCommand:1008 Result of excution of X:\Program Files\Symantec\Deployment\Ghost\DriverManager64.exe with command line :  /ddb="C:\DS_SOI\Symantec\Deployment\DriversDB" /list="X:\program files\Symantec\Deployment\driver_list.txt" /cout="C:\DS_SOI\Symantec\Deployment\DA_Eval_List.xml" /format=xml
[2013/11/26 15:41:12.302 1228:236 2] apps\DeploymentClient\clientsoi\tcube_clientsoi.cpp:1030 ExecuteCommand returned 
[2013/11/26 15:41:13.325 1228:236 0] common\util\SMPPackage.cpp@678: Error in downloading file from HTTP.source :http://<notification-server-fqdn>/Altiris/PackageShare/pkggroup_uabhdgv2h3563ykdzc5redxvrn4eoul7/DriversDB/Intel_Corporation.igfx.9.17.10.3040/GfxUI.exe.config and dest :C:\DS_SOI\Symantec\Deployment\DriversDB\Intel_Corporation.igfx.9.17.10.3040\GfxUI.exe.config. The COM error = HTTP error: 404 Not Found
[2013/11/26 15:41:13.325 1228:236 0] File:common\util\ExecuteCommand.cpp,Line:4303 ERROR: Exception has occured in File SMPPackage.cpp at Line No 679. Type of exception is GeneralError. Error is HTTP error: 404 Not Found. Error Description is  "util::CSMPPackage::GetMultiplesFileFromHTTP". Value of Windows error code = 183 and message is " Cannot create a file when that file already exists.
"
 
When we browsed to the URL (http://<notification-server-fqdn>/Altiris/PackageS...) we found that the directory existed, but the "GfxUI.exe" file did not actually exist.

We removed that driver (Intel_Corporation.igfx.9.17.10.3040) from our DeployAnywhere database and now the OS Install task is working correctly.

Not sure if this is entirely related or a fix or others here who have the same error message, but this seemed to work for us.

jimmy.cartrettenewwowrk's picture

I just ran into the same... GfxUI.exe.config 404 error. It turns out IIS will content filter certain extensions (such as a .config file). I went into IIS and removed .config from blocked extensions, and it was happy.

Thomas Baird's picture

All of these finds are excellent.  I hope everyone reading this thread is discovering the need and value of actually reading the DSTasks log client-side, because often only the generic error is returned to the console and we need to see the full issue in that log.

 

Thanks everyone!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

Richard Hosking's picture

I was able to solve this for my environment. The DSTasks log had these errors

[2013/11/27 08:24:52.254 1672:1288 2] Function Name is util::CSMPPackage::callDSPSInfoOperationService(),file name is common\util\SMPPackage.cpp and Line no 211.Reuest XML is https://<site server fqdn>:443/Altiris/PS/Deployment/DSPSPackageInfo.aspx?xml=<request><CreatePackageFolder><inputFolderGuid>{051d8448-aa5c-45b0-8dc7-94a36a533795}</inputFolderGuid></CreatePackageFolder></request>
[2013/11/27 08:26:54.291 1672:1288 2] callDSPSInfoOperationService()have failed. Function:util::CSMPPackage::callDSPSInfoOperationService(),File:common\util\SMPPackage.cpp and Line:217. Return XML is =
[2013/11/27 08:26:54.291 1672:1288 0] File:common\util\ExecuteCommand.cpp,Line:4303 ERROR: The Exception have occured in Client Imaging Task.

Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP Request Failed: Unknown error 0xFFFFFFFF. Error Description is  "util::CSMPPackage::callDSPSInfoOperationService". Value of Windows error code = 183 and message is " Cannot create a file when that file already exists.
"

I noticed that the only attempt to create the package folder was via an HTTPS command. The default site for that site server was not setup for HTTPS protocol. All I had to do to resolve the issue was create a certificate for this site server and bind it to the default site.

 

Robert McArthur's picture

Hi

I'm trying to capture a backup image on DS 7.5.  

I'm seeing the following error in DSTasks.log

Exception has occured in File SMPPackage.cpp at Line No 222. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = HTTP status: 404. Invalid data received in HTTP response. Expected 1547 bytes, received 0. Error Description is  "util::CSMPPackage::callDSPSInfoOperationService". Value of Windows error code = 183 and message is " Cannot create a file when that file already exists.
"
 
Right before I can see it trying to create a folder
 
Function Name is util::CSMPPackage::callDSPSInfoOperationService(),file name is common\util\SMPPackage.cpp and Line no 211.Reuest XML is https://<server fqdn>:443/Altiris/PS/Deployment/DSPSPackageInfo.aspx?xml=<request><CreatePackageFolder><inputFolderGuid>{8688796B-F6D3-4DDB-AC59-E0B217A79A0F}</inputFolderGuid></CreatePackageFolder></request>
 
We have a HTTPS enabled and a valid certificate in place and I've been creating images with no issue for the last week.  I see a few other with a similar issue.  has anyone gotten to the bottom of this?
cscottrun's picture

I was struggling with this problem since upgrading to 7.5, and support helped me fix it last night.  Thomas is right that it is an IIS problem, but I did not know enough to determine WHAT was wrong with IIS.  Here's the troubleshooting that they took me through:

  1. In Automation, after the image fails to create, find DSTasks.log. In our PXE automation it was at X:\Program Files\Symantec\Deployment\Logs\DSTasks.log
  2. In DSTasks.log, find the error that is occurring - I searched the text for "exception" and found the same cryptic error that was showing up in the task result.
  3. Find the URL immediately before the error in DSTasks.log.  It includes XML code and a GUID.  Mine was:

    http://[...Site Server...]:80\Altiris\PS\Deployment\DSPSPackageInfo.aspx?xml=<request><CreatePackageFolder><inputFolderGuid>[...GUID...]</inputFolderGuid></CreatePackageFolder></request>. 
     

  4. Copy this whole URL including the XML into a browser.  If you do this on the site server running IIS you should see the detailed IIS error message and THIS is where we found an indicator of what was actually broken.  Ours showed a problem with MIME types.
  5. The solution in our particular case involved duplicate MIME types defined in web.config for the Default website in IIS.
Sally5432's picture

nevermind going to start a new thread.

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

Victor Lopes's picture
Thank you cscottrun, your tip was really valuable.
 
In my case the problem was the Deployment Package Server Components that was not actually installed on the notification server itself, so the directory "Deployment" wasn't available inside the the http://smpserver/Altiris/PS/ path in the IIS.
 
In my scenario I migrated from the 7.1 version and this could be the cause for this Deployment Package component not being installed.
 
I simply used the "Deployment Package Server Components - Install" policy (Settings > Agents/Plug-ins > Deployment and Migration) to install the proper components on the target notification server.
 
Another issue is, if you are using a preboot image with HTTP only (instead of HTTPS) you might want to check if the "PS" directory is set to "Require SSL" in the IIS (IIS > website > Altiris > PS - click "SSL Settings" in the Features View). If the SSL is required on this path the PECTAgent on Windows PE won't be able to access it trough HTTP. Preboot environments in SMP 7.1 versions don't support SSL, so if you upgraded from a earlier version you might cross this.
 
cslingerland's picture

1.if you're not in a .COM environment, we may have problems with HTTP imaging.  Note that we'll fail-over to UNC, unless you're required to be secure and/or have UNC blocked and/or have UNC codebases not being returned via the console.  We have a known issue around domains that are NOT .Com.

Is there a way to force UNC path? We are using a .org environment and would like to try and rule this out as the possible cause. Where can we change this in the console or on the server?

Thomas Baird's picture

There is no way I know of to "force" UNC, though before leaving Symantec I had asked for that as an option to be added as a possible work-around for scenarios "like" this.

So unless someone has added an option in the last week, no, there's no way to "force" DS 7.5 to use UNC instead of HTTP.  Once it get's it's mind set on HTTP, it uses it.  :P  Well, at least in 7.5.  7.1 is always UNC.  I figured I'd clarify that for any passing by reader.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

jimmy.cartrettenewwowrk's picture

Thomas,

A lot of people are getting 404 based HTTP errors. I believe the issue is that default IIS settings are blocking certain files (.config, .resources are the two I've run into) from downloading, so when using HTTP vs UNC, HTTP gives a 404 while UNC will give the file. I resolved the issue by removing file blocking for .config and .resources . Particularly, Intel's igfx drivers have these files. In case you wanted information for a KB article on this.

Cesar Americo's picture

I was trying to capture a backup image and  got this same error in my SMP 7.5 lab " Value of Windows error code = 183 and message is Cannot create a file when that file already exists."

I applied full access to everyone in deployment folder and aftert that worked fine.

Thanks

Scott Bowman's picture

We where unable to capture images. After a lot of tinkering we could capture but Deploy Anywhere wouldnt work and our processes where riddled with errors.

Support found there where a LOT of missing files following our upgrade to 7.5 from 7.1. We upgraded to 7.5sp1 and this fixed everything.