Save in IE to network share never completes

[NCRick]

"save" in IE never finishes. Eventually the IE (6) pops up saying a
script is causing IE to run slowly, abort? and whether I say yea or
nay it never completes.

I have put the location (a network share) into Trusted Sites. I have
enabled all the scripting controls and reduced all the security
restrictions I can find. This is on a company workstation in a highly
locked-down environment. At the moment I can use Firefox to update my
tiddlers and it works fine, but most of my compatriots do not have
Firefox access and they might take it away from me some day too.

So, not likely Trusted Sites issue, think I've enabled all the
scripting and ActiveX I can find, what other stuff can I check into?
If the tiddly is stored on the local hard drive (C:\temp for example)
saving works fine. Could be a workaround but clunky.

Where else would you look?

[FND]

> "save" in IE never finishes. Eventually the IE (6) pops up saying a
> script is causing IE to run slowly, abort? and whether I say yea or
> nay it never completes.

Might this be a file-permissions issue on the file server? (Unlikely, of
course, since Firefox works.)

Do you have any plugins installed - please give us some more details:
http://www.tiddlywiki.org/wiki/Troubleshooting

-- F.

[Wulfy]

Try opening the TiddlyWiki as a file URL in a browser, not a file in
explorer.

Eg: file:///E:/Blah/ProjectLog.html

This has stumped me for a while, but googling this group produced a
result! (I am just reposting a solution!)

[NCRick]

No plugins, very vanilla - for my tests I've used a nearly new
tiddly. Writing to the server (in my directory) is one aspect that is
not locked down. Don't think Windows has ways of controlling "what
program" writes to a directory. I have opened the file from IE (in
fact that's how I usually open it) as a filename (r:\Mywiki.html) and
as UNC path, makes no diff. Put the directory and the tiddly
specifically in my Trusted Zone. Though that update doesn't always
"stick" so maybe there's a group policy that prevents me from updating
it - though sometimes it seems to "take".

Guess I'll just have to live with copying it to my c:\temp directory
and back to edit it. Thanks for thinking about the question ...

[FND]

> Put the directory and the tiddly specifically in my Trusted Zone.
> Though that update doesn't always "stick" so maybe there's a group
> policy that prevents me from updating it

That's very odd.
I'm afraid I have no idea what's going on here.
I know many people use TW on a network share - do you have a home
network you could test this on?

-- F.

[NCRick]

Oh it works great at home. Something about how IE is configured.
Don't suppose the support people are interested in anything so end-
user-enabling (if it can't be done in Excel, Word, or Powerpoint then
it shouldn't be done, is their motto).

[Wulfy]

Ah forget it... Didnt work afterall.

I started looking at the Java code, it seems that some file paths are
not returned at all on the network making the wiki fail on saves.
However, I am not Java coder so Im staying away from any concrete
conclusions.

All I have to say I have the same problem.

Saves ok on local drive.
On a network it either says "Cant save with this Browser ..."
or it just times out.

All plugins disabled, IE configured so lose that if it was any loser
it would be jailed for soliciting.

[Marc Stober]

I was having the same problem and discovered that I had this error
when I saved to the root of a network share, while everything worked
when I saved to a folder within the share. For example:

H:\myWiki.html // "a script is causing IE to run slowly" error and
machine would hang if I didn't abort

H:\myFolder\myWiki.html // success

If TiddlyWiki developers are here, it looks like the script is going
into an infinite loop in the ieCreatePath() function because
fso.GetParentFolderName("H:\") returns an empty string.

- Marc

[FND]

> I was having the same problem and discovered that I had this error
> when I saved to the root of a network share, while everything worked
> when I saved to a folder within the share.

Most interesting - thanks for letting us know (and even supplying a
detailed analysis)!
We'll look into this.

-- F.