Applied Users Forums

General Topics => Helpline => Topic started by: Andrew Carrick on January 25, 2010, 03:32:54 AM

Title: Dec Page Editing problem
Post by: Andrew Carrick on January 25, 2010, 03:32:54 AM
I'm getting an error message "Invalid semaph 400" when trying to access a Dec Page for editing. Anybody know how to fix this please? I don't get the error message when using Citrix but would rather connect directly with PC for other reasons. Someone suggested a WINTAM INI setting but I can't see the difference between the PC and Citrix INI files.
Title: Re: Dec Page Editing problem
Post by: Bloody Jack Kidd on January 25, 2010, 08:23:15 AM
you could try some of the basics:

- rename the local c:\wintam dir to c:\wintamold and re-run asupdate /rr
Title: Re: Dec Page Editing problem
Post by: Andrew Carrick on January 25, 2010, 08:33:32 AM
No joy with that I'm afraid  :(
Title: Re: Dec Page Editing problem
Post by: Bloody Jack Kidd on January 25, 2010, 09:45:22 AM
try running the tblutil utility... I think that's in the wintam dir.
Title: Re: Dec Page Editing problem
Post by: Andrew Carrick on January 25, 2010, 09:56:32 AM
Still no good, but thanks for playing!
Title: Re: Dec Page Editing problem
Post by: Jim Jensen on January 25, 2010, 02:44:23 PM
How about display settings? If you alter the display settings, like using Windows XP Style the custom decs won't open properly. Perhaps when using Citrix it's applying those properties differently.
Title: Re: Dec Page Editing problem
Post by: Andrew Carrick on January 26, 2010, 03:31:13 AM
Aaahhh... thanks, that seems to have worked. Strange because I could open the Apps at policy level anyway without problem, it was just editing that I couldn't get to. My display properties showed Modified Theme so I changed to Windows Classic (but got rid of that horrid blue background) and all working now. Cheers Jim.
Title: Re: Dec Page Editing problem
Post by: Jim Jensen on January 26, 2010, 09:16:50 AM
Quote from: Andrew Carrick on January 26, 2010, 03:31:13 AM
Aaahhh... thanks, that seems to have worked. Strange because I could open the Apps at policy level anyway without problem, it was just editing that I couldn't get to. My display properties showed Modified Theme so I changed to Windows Classic (but got rid of that horrid blue background) and all working now. Cheers Jim.

You can change the background, but you can't change the theme. Don't know why this is an issue. Don't think I've ever met another program that care what theme you use.