TeamSite slow and copying files to Y drive give error when completed.

My users have been copying files through a mapped drive to our TS server. Yesterday they reported that it was very slow and that they were receiving the following error, "Cannot copy xxxxx: the specified network name is no longer valid". The file will copy, but tends to hang the open explorer window on their desktop and takes at least a minute to start. Copying to a local drive on the server works fine without these issues.

I have restarted the entire server and also ran iwfsch -d which found no errors.

I also did an RDP session to the server and copied a local file to the Y: drive and was very slow to start, but eventually copied. It was a small file, under 1 MB.

I have a support case open, but since this is production does anyone have any suggestions while I wait for a reply back?

Find more posts tagged with

Comments

mart2001

Have you looked at iwserver.log and iwtrace.log? Do those logs contain any useful information? Also, check the events log to see if there is any error messages.

cesarecastro

Besides checking the usuall Teamsite logs, I would also check the server performance. Check cpu or disk performance when doing a copy to the server. Even your virus scanning will cuase your file copies to be a bit slower.

Migrateduser

CPU and memory are fine.

Here are a few things I found out yesterday.

One of our users uploaded over 3000 files totaling over 18GB on Monday. I suspect this has something to do with it.

Small files copy fine, but the larger the file the more chance of getting the error and the longer it takes to begin copying.

Copying from TeamSite Y drive to my local computer or to a local drive on the TS server runs at normal speed. Copying to the TeamSite Y drive is slow. So, essentially writing to the TeamSite share is slow, reading from it is fast. This is with McAfee enabled or disabled. I find this the most interesting but still don't know what to do.

Logs

10 mb file

[Wed Jan 12 07:16:24 2011] corporate\aalgaat master DestroyFSE \default\main\Partnerpage\WORKAREA\Service \attachments\Copy of SMTPSVC1.zip
[Wed Jan 12 07:16:24 2011] corporate\aalgaat master SyncDestroy \default\main\Partnerpage\WORKAREA\Service \attachments\Copy of SMTPSVC1.zip FILE

300mb file

[Wed Jan 12 07:16:34 2011] corporate\aalgaat master DestroyFSE \default\main\Partnerpage\WORKAREA\Service \attachments\aaa.zip
[Wed Jan 12 07:16:34 2011] corporate\aalgaat master SyncDestroy \default\main\Partnerpage\WORKAREA\Service \attachments\aaa.zip FILE

Migrateduser

I have now tried another test.

I stopped TeamSite, created a new empty store and tried copying to it. Same results. At least the rules out the store or workflows as the issue.

I plan on moving to a new server in the next month anyways, so hopefully this issue goes away with a newer OS and a newer version of TeamSite.

nipper

Have you changed the cache settings in iw.cfg ?

How much memory is on this server ?

Anything of interest in the event viewer ?

Migrateduser

Nothing of interest in the logs. Nothing was changed in the iw.cfg. It's a case of "it was working last week" but now has this issue. Server guy says nothing was changed (no windows updates, etc)

3GBs of ram

cachesize=45000