- This topic is empty.
-
Posts
-
When I do a remote repository sync, the image that is being synchronized will transfer fully from the Main repository to the Remote. When I check the file size on the remote repository, it matches the Main repository. But if you only watch the rapport process, it will error out making it look like it did not transfer completely. When this happens, this error occurs:
Syncronization Failed. Reason:[Error:Not Available] [Ftp socket connection error:could not send data to the server][Ftp error:250 CWD command successful.
Also, if I check the log in the DB, I am getting a lot of errors like this:
Dispatch DB Connect Failed
I dont know if any these errors relate to each other, but when I try to send an image to the remote terminal after the whole file transfers, it dosent even ask if I want to transfer again, the Image sync automatically starts. I have to quickly terminate the repository sync, and then tell WDM not to stop the image job. Once I do this, the terminal images no problem… Weird stuff going on here =S
I can’t comment on the remote repository issues, as I haven’t had the opportunity to play around with them yet. But I can tell you that you can pretty much disregard that Dispatch DB Failed error message. I’ve talked with half a dozen wyse techs and they all tell me to just ignore it. It seems that all instances of 4.5.1 have that message appearing in their logs.
Good to know I’m not the only one that get the Dispatch error… Just wish I could figure out the other error. Anyone know when WDM 4.6 is coming out? lol
You might check if the crc.txt file is present.
Can you get a network trace, filter by FTP and save off the command portions (USER, PASS, CWD, LIST, GET, etc..)It might help identify where its getting an error.
The error message is strange, the last reported response is CWD success (250 is success) This means that it didn’t report success or failure on the transfer.What are the session timeout and Bandwidth values set in your SWREP properties?
-k
session timeout: 200 sec
bandwidth: 10240 KbpsWe have an MPLS network with full T1 running to every site as well.
I bumped the speed down to 1000 Kbps, and now it seems to be working ok now. Haven’t had any errors as of yet. I do notice something in the system logs though… I get a:
Event Type: Warning
Event Source: MSFTPSVC
Event Category: None
Event ID: 10
Date: 10/1/2007
Time: 3:14:12 PM
User: N/A
Computer: NCDRRAPPORT
Description:
User rapport at host 10.100.23.166 has timed-out after 120 seconds of inactivity.any Ideas?
I see the same error message in the event logs of my server. I see it when packages are pushed to clients. I assumed that the client wasn’t closing the connection to the FTP server before it rebooted, so the FTP service was keeping the session open until it timed out.
- You must be logged in to reply to this topic.