I admit this isn't ISA related specifically, but I hope some of you have some good SharePoint experience and might have run into this before.
The problem I'm having is that my ISA 2006 config is setup so that all HTTP requests are redirected to use HTTPS. Works fine, with the exception of Word. If you browse to the SharePoint site and select Share Documents\New, this opens Word. Type in some garbage and select File\Save As.
It is supposed to show the Share Documents site in the Save As dialog but you receive the error
--------------------------- Error --------------------------- Documents in this folder are not available. The folder may have been moved or deleted, or network problems may be preventing a connection to the server. --------------------------- OK ---------------------------
I took a network sniff from my client and Word is sending the trafic out as 'plain ol HTTP' and when ISA redirects the request to use the HTTPS site, Word doesn't retry the request, hence the failure.
Have any of you ever seen this, or know of some good SharePoint sites that may cover this? My Google Kung-Foo is weak and I couldn't find anything. Still looking though.
Yeah, we added it into the Trusted Sites list but had the same problem. We just can't quite figure out if it's a SharePoint Access Mapping issue or just Word being lame and not following the redirect.
There are 3 requests that Word makes - an OPTIONS, PROPFIND and a POST. These all receive a 302 response but Word doesn't chase the redirect. If we set ISA to not redirect to SSL, Word works correctly and the SharePoint site shows up in the Save As dialog box.
It appears that Word just retries it as HTTP because when we sniff the traffic when ISA doesn't redirect to SSL, Word only makes these 3 calls one time. When ISA redirects to SSL, Word appears to retry 3 times.
< Message edited by ClintD -- 7.Jul.2009 11:11:42 PM >
I'm not too savvy with the SharePoint side so I don't know what you mean by 'Standard Document Library'. It's a basic SP site - no customization. Does that answer your question?
What version of Office did you use? My Word version is 'Microsoft Word 2002 (10.6850.6845) SP3.
Apparently, it doesn't happen in Word 2007. I was on the horn with MS Support and he could only reproduce it in Office XP (yeah, we're lame and that's the version we have deployed). I'll update the thread when/if we find anything.
Thanks for offering Jason - I'll take you up on your offer if it gets any more weird. lol
Posts: 4663
Joined: 30.Jul.2002
From: United Kingdom
Status: offline
quote:
ORIGINAL: ClintD
Apparently, it doesn't happen in Word 2007. I was on the horn with MS Support and he could only reproduce it in Office XP (yeah, we're lame and that's the version we have deployed). I'll update the thread when/if we find anything.
Thanks for offering Jason - I'll take you up on your offer if it gets any more weird. lol
Looks like it's going to be a hotfix for this one. I'm somewhat surprised about this - the redirect to SSL should be an assumed and not too rare. Not sure why Word can't handle it.
The MSFT SharePoint support folks had me use TTracer on the client and sent the results off to the Word support team. They had me configure anonymous access to /vti_inf.html* and /vti_bin/*, but we still had the same issue.
They're triaging (if that's a word) the hotfix now.
AAM issue. 5 months and it took the Office Integration guy from MSFT 5 minutes to figure this out. I had about 4 months with the SharePoint guy and he checked the AAM config the first day I opened the case and he confirmed it was correct, which it obviously wasn't.