Cannot copy files into SPS2003?

[zacca]

Hi there,

Got SPS2003+SQL2000, both on w2k3 server, same domain.

After migration plenty of GB files into SPS in these few days, now I can't move file in at all, no matter via mapped drive \\sps\sites\dept1 or via browser

http://sps/sites/dept1

System prompted "Cannot copy filename: Insufficient system resources exist to complete the requested service"

I found both SPS & SQL server c: got plenty of disk spaces, so dunno what's wrong.

Wondering have you seen this before? Any quick fix?
Many thanks!

 

[Thomas2000]

Hello,

have you checked your eventlogs on the server and see if it has logged anything there? Have you checked the memory usage? Have you also checked so that your SQL databases so that they are allowed to grow and not limited to any particular size? You can also check the SQL server logs from Enterprise Manager and see if you can find any errors there.

Regards,
Thomas

 

[lithiumSPS]

zacca,

Double check the quota templates and maximum download settings in the Virtual Server General Settings area. I also had this error occur when we started moving files over in the Web Folder client and used the drag-and-drop method. The files inside the folders had some issues due to unknow extensions and caused the errors. Wealso found some executables that weren't allowed.

-Rob

 

[zacca]

Hi Rob,

Yeah, exactly the same scenario, during drag-n-drop, it stop at the point when error occurs, error included extension like *.bat, *.exe, *.com, *,hlp, *.shs, *,vbs, etc; filenames contain special chars like ~ # % & etc; filename to long (more than 140+ chars)....

It was really a pain to mirgate tons of files from normal file system into sps file system! X-(

Thx for the info, I'll check those settings to see how it goes! A star for you!

 

[Thomas2000]

Hello,

SharePoint by default block extensions like *.exe, *.bat *.vbs *.com etc. due to security reasons. Those filetypes can contain mailicious code and since it is executable files it is blocked by default. You will manually have to remove those extensions in the SharePoint configuration to be able to upload them.

File and foldernames can not be longer than 128 characters and the and the URL for file and folders can not be longer than 260 characters.

I also found out the hard way when moving data into a new environment. Users for some reason like very very long filenames and loooong folder structures!

Regards,
Thomas

 

[lithiumSPS]

zacca,

You can do what Thomas said but I'm not sure that you want users saving .exe or .bat files to the SharePoint directory. We are creating something called a Knowledge Management Migration Form in which a designated person would review documents and files that resided in shared storage. If the information meets guidelines in the form then that information can be migrated to directories within SharePoint. I also will be starting to code this form in .NET so you can point to a directory and have the program log the files that will not migrate. I don't have this near ready but some of our directories have thousands of documents. This sounds like alot of work but it also gives that group the chance to remove unused documents or files, create file structure, and rename files.

-Rob