Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


bbusse
2011-07-26T15:20:14Z
I am using VisualCron 5.7.5 on a 2008 R2 SP1 Virtual Server(Vmware ESX 4i). I have the client also installed on another 2008 R2 SP1 physical machine (my personal desktop machine) that I use to manage the VC Server.

So, I open the client on my machine and go to add a new Execute task, though i don't think it matters what type of task. For the command, I click the browse button which brings up the REMOTE VC Server's list of drives. I expand drive C:, click on Windows. It 'sometimes' locks up when I click on windows. But if it doesn't, I can click the plus sign and expand Windows to then select System32 and this 100% of the time, locks up the client on my machine. I have to close it. The VC Server is not affected, I merely re-open my client on my own machine and can try again.

I'm sure this has something to do with the large number of files in the Windows and/or the Windows\SYSTEM32 directory and its causing some sort of overflow on a remote client, but I thought i'd at least mention the issue.

I have a screenshot

Let me know your thoughts. This does NOT happen when i run the Client locally on the VC Server. Just when its a client viewing the VC Server's drives/folders.

Brian / ChevyNovaLN
bbusse attached the following image(s):
Sponsor
Forum information
Support
2011-07-27T15:02:35Z
The information you request, a list of files on a remote server is sent between client and server using another technique than locally. Simply because that technique is not available on cross server communication.

I guess the information sent is rather large. Do you have Compression on in the remote server connection?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
bbusse
2011-08-08T15:54:32Z
Yes i do have compression turned on. The amount of data (the number of files at least) is quite large in either c:\windows\ or c:\windows\system32\

On my system, there are 2800 files in c:\windows\system32\ so i assume there is a choking point, maybe hitting a buffer limit of some sort using whatever method is being used to list the files/folders ?

Brian
Scroll to Top