Deployment Solution

Hello, We seem to be getting a very unexplained problem with altiris. When trying to copy files, scripts and even wise packaging to client machines all the data shows as 0KB.

Restarting Services doesn't work and restarting the server doesn't work. It seems like a bug more then anything because we have had it working off and on when it wants to. Anyone have any

ideas?

Hallo jdill

Have you tried making a copy to another library than c:\ it seems as though this is what you are trying to accomplish.
And it also seems like you are runningn windows 7, there are other security settings on the root of the C:\ drive, and this may very well be the root of your problem.

Kind Regards
Morten Leth

Maybe test on one system where you turn UAC off and see if that changes anything.  A lot of times, UAC will "prompt" for something and you never see it.  Most jobs in DS 6.9 run as System, and if you don't run as the currently logged on user, any "prompt" will never be seen.  If the system is prompting, then I would expect a 0KB file as it "waits" for you to approve the data-stream.  It's a place-holder or market - similar to what we create prior to an image being made.

Anyway, between security and UAC, maybe you can find the issue.  GL!

Thanks for the replies. It's definatly not UAC. And i cant see anything wrong in the antivirus cause i have tried disabling it.

[11/21/2010 22:42:46.784 600 0] RequestSendFile.cpp:624 - CRequestSendFile::DoReceiveFile: caught CIPCError exception
    SocketIPC.cpp:253 - CSocketIPC::Read Timed Out
    
[11/21/2010 22:42:46.784 600 0] RequestSendFile.cpp:464 CRequestSendFile::HandleMessage : Error Receiving file. DoReceiveFile() returned false.
[11/21/2010 22:43:10.448 6044 0] RequestSendFile.cpp:624 - CRequestSendFile::DoReceiveFile: caught CIPCError exception
    SocketIPC.cpp:253 - CSocketIPC::Read Timed Out
    
[11/21/2010 22:43:10.448 6044 0] RequestSendFile.cpp:464 CRequestSendFile::HandleMessage : Error Receiving file. DoReceiveFile() returned false.
[11/21/2010 22:45:29.885 1944 0] RequestSendFile.cpp:624 - CRequestSendFile::DoReceiveFile: caught CIPCError exception
    SocketIPC.cpp:253 - CSocketIPC::Read Timed Out
    
[11/21/2010 22:45:29.885 1944 0] RequestSendFile.cpp:464 CRequestSendFile::HandleMessage : Error Receiving file. DoReceiveFile() returned false.
[11/21/2010 22:47:2.477 3020 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
[11/21/2010 22:47:2.477 3020 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
[11/21/2010 22:47:2.508 3028 0] apps\dsagent\agent\LogEventThread.cpp:57 - CLogEventThread::Run CLogEventError
    Thrown from apps\dsagent\agent\LogEventThread.cpp:113 -message = CLogEventThread::ReadLogEvent() - Shutting down.
    SystemError Value = 0x00000000
    
[11/21/2010 22:47:2.508 2328 0] DsAgent.cpp:392 About to serialize objects
[11/21/2010 22:47:2.508 2256 0] main.cpp:780 - Leaving Main()
[11/21/2010 22:47:5.082 2216 0] bootstrap.cpp:1114 - Error reading input file.
[11/21/2010 22:47:5.534 2216 0] bootstrap.cpp:450 GetCfgFilename(): strName = C:
[11/21/2010 22:47:9.153 4804 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
[11/21/2010 22:47:9.153 4804 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
[11/21/2010 22:47:9.184 4408 0] apps\dsagent\agent\LogEventThread.cpp:57 - CLogEventThread::Run CLogEventError
    Thrown from apps\dsagent\agent\LogEventThread.cpp:113 -message = CLogEventThread::ReadLogEvent() - Shutting down.
    SystemError Value = 0x00000000
    
[11/21/2010 22:47:9.184 2216 0] DsAgent.cpp:392 About to serialize objects
[11/21/2010 22:47:9.184 2496 0] main.cpp:780 - Leaving Main()
[11/21/2010 22:47:11.789 2176 0] bootstrap.cpp:1114 - Error reading input file.
[11/21/2010 22:47:12.070 2176 0] bootstrap.cpp:450 GetCfgFilename(): strName = C:
[11/21/2010 22:47:18.076 892 0] ReplyUpdateComputer.cpp:171 - Error removing registry value.
[11/21/2010 22:47:18.076 892 0] ReplyUpdateComputer.cpp:247 - Error reading logevent status from registry.
[11/21/2010 22:47:35.266 1236 0] RequestSendFile.cpp:624 - CRequestSendFile::DoReceiveFile: caught CIPCError exception
    SocketIPC.cpp:253 - CSocketIPC::Read Timed Out
    
[11/21/2010 22:47:35.266 1236 0] RequestSendFile.cpp:464 CRequestSendFile::HandleMessage : Error Receiving file. DoReceiveFile() returned false.

Could be useful to see the screen grabs from an actual task which is copying the files and failing (and anything configured in the advanced button).

And, is the result the same on XP/Vista/Windows7?

If XP works, but the Vista/7 flavours don't then that could point to local security policies on the client perhaps preventing the file download (if the client is accessing the source directly).

On the client, fire up secpol.msc,
Local Policies -> Security Options -> Network Security: LAN Manager Authentication Level

Try changing the default option to send LM and NTLM response

I also have a nasty habit of firing up wireshark at the first sign of trouble with DS. Can often be a very fast way of diagnosing whether something is environmental (especially when security is concerned).

Kind Regards,
Ian./

but I don't have anything definitive.  You may want to call in to support, frankly.

HOWEVER

When we looked at logs that looked a lot like this in the past, what it looked like was network connectivity issues with the DS.  For instance, we know that networks will often sever the connection between the client and the DS without warning because it perceives the open port as a threat.  Other kinds of network issues can have similar effects, whether it be routing problems, or a bad port on a switch, or things like that.  You may want to verify that the clients are able to reliably stay connected, and that nothing on your network is causing issues.

Again, that's what the logs "look" like on initial inspection (that the client appears to have connectivity issues), but that's just an initial look, and you may need a deeper diagnosis.  Check out the network for some "interesting" policies and then I guess let us know.  :D

Nice suggestions btw ian.  Wireshark is wonderful, and actually might point to the same things.  :D