nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Microsoft Word File Corruption on Import

System

We are on TeamSite 5.5.2 SP3 and use Microsoft Office XP. We have users complaining that their files (specifically Word docs) are getting corrupted within TeamSite. This doesn't happen all the time, but when it does and a user tries to view the doc file, he is prompted by Word to 'convert file from' and things like html, rtf, etc. are options. After choosing that option, the user is prompted to choose encoding (and options are different languages like Japanese, Chinese, etc. but excluding English).

Has anyone else seen anything like this? I don't have enough information right now to know if the files get corrupted upon import or through some other TeamSite process, so I am hoping someone else has had a similar experience to help me narrow things down.

Any feedback would be appreciated.

Find more posts tagged with

Comments

Migrateduser

does this happen when you are trying to import file into Teamsite from local file system?

Migrateduser

What platform is your TS server hosted on?

Migrateduser

Actually with TS 5.5.2 SP2 - we had something similiar happen because we were using an outside process which read the files - is this the case here?

Migrateduser

Thanks for your responses. Let me see if I can answer them all:

- TeamSite is hosted on a Windows 2000 server with the most recent Windows service packs.

- I am not sure yet whether the files get corrupted upon import or after they are submitted, published, etc., but the files are definitely imported from a local file system (either the user's C drive or some shared network drive)

- We are using the out of box import and aren't really ever opening up the files with any scripted processing - the only changes to the files would be made by the user when they open up the files for editing (all of our users use direct editing so Launchpad never opens up).

I think that answered everything. Please let me know if you have any other ideas.

Thanks again-

Migrateduser

You say you aren't using Launchpad, but that the users are accessing the word documents with the mapped directory?

Just making sure I understand the use case.
Regards,

lissa

Migrateduser

We have TeamSite set up for direct editing. I believe that means that they are actually using Launchpad, but the Launchpad window never opens - basically, they never have to deal with the 'edit file', 'upload file', 'remove from list' etc. that comes with the LP interface. When they click 'edit', whatever program they have set up to edit that type of file through Launchpad opens the file and then when they save, it saves right into TeamSite automatically - no uploading.