Remote stack thinks it is corrupt

[Sivakatirswami]

  In house I serve a lot of stacks from our big XServer on the LAN.

I issue small players to desktops and then call the actual apps for 
production with

I recently updated a stack with  Livecode 4.6 dp7; put it back on the 
server and then call it as usual:

on mouseUp
    go stack url "http://varuna.hindu.org/rev_stacks/KA Media 
Player/KA-Media-Player.livecode"
    put the result
end mouseUp

I'm getting:  stack is corrupted, check for ~ backup file


OK so I wondered if it was 4.6 dp7 and so I made back ups of some other 
stacks, very old (circa 2005-6)

opened them in 4.6 dp7 and "messed around" with a lot of new features, 
graphic effects, added a few behaviors etc.

saved and put one of these back on the server.

stack is corrupted, check for ~ backup file


on mouseUp
    go stack url 
"http://varuna.hindu.org/rev_stacks/KA-Stack-Index.livecode"
    put the result
end mouseUp

well, result is empty, stack opens up just fine.

So this means that this one stack:

KA-Media-Player.livecode

is registering as corrupt if I try to load it with
go stack url "http://varuna.hindu.org/rev_stacks/KA Media 
Player/KA-Media-Player.livecode"


but I have for years opened and worked on stacks across the network and 
in this case if asking go to the server in the finder and double click 
on the copy on the server:

KA-Media-Player.livecode

it opens in 4.6 dp7 just fine.  There is no indication at all that it is 
corrupt.

So, I'm stuck.. I can't deploy this stack with standalone player.  Since 
the stack seems fine, I don't know what to fix.

The only clue could be possibly that there are a lot of open card and 
open stack handlers in KA-Media-Player.livecode stack and a standalone 
made with 4.6 dp7  (i updated the player)  may not like these for some 
reason, where as simple stacks that do not have a lot of initial 
activity on open stack/card, open just fine when called by the same player.

Any insights on how to de-bug this?

Otherwise I don't know what to do other than send the stack to Mark and 
ask him why 4.6 dp7 thinks it is corrupt if called remotely.

Sivakatirswami