Re: XP SP2 ADM errors

From: Wesley Vogel (123WVogel955_at_comcast.net)
Date: 08/10/04 

Date: Tue, 10 Aug 2004 10:53:13 -0600

"The following entry in the [strings] section is too long and has been
truncated" error message when you try to modify or to view GPOs in Windows
Server 2003, Windows XP, or Windows 2000
http://support.microsoft.com/default.aspx?kbid=842933 

-- 
Hope this helps.  Let us know.
Wes
In news:OlIl8QufEHA.3348@TK2MSFTNGP12.phx.gbl,
Kerry Hoskin <kjho@pml.ac.uk>  hunted and pecked:
> I have just installed XP SP2 (been using RC1 for several months) and
> updated the adm files on our w2k3 domain.  When I open a GPO that
> uses the new ADM settings I get loads of errors such as
>
> The following entry in the [strings] section is too long and has been
> truncated.
>
> It then gives the extended description definition as used to explain
> the gpo setting.  It does this for all or most of the new settings
> leading to me having to click about 50 error boxes, grrrrrrrrrrr
>
> Kerry

Relevant Pages

  • Re: Hotfix error?
    ... "The following entry in the [strings] section is too long and has been ... truncated" error message when you try to modify or to view GPOs in Windows ...
    (microsoft.public.windows.server.sbs)
  • GPO errors after upgrade
    ... now everytime I ... open up a gpo I get ... "The following entry in the [strings] section is too long and has been ...
    (microsoft.public.win2000.group_policy)
  • Re: hiding drives
    ... I edited the ITEMLIST and the [strings] for the ... GPO (I know I didn't need to do this but I was getting ... I added an entry to the ITEMLIST and added ...
    (microsoft.public.win2000.group_policy)
  • RE: Group Policy ADM
    ... There is a fix for that behavior, please take a look at the following article: ... "The following entry in the [strings] section is too long and has been ... truncated" error message when you try to modify or to view GPOs in Windows ...
    (microsoft.public.windows.group_policy)
  • Re: Executable enty points incorrectly documented
    ... All these things are correct but this is more specific and related to the .NET Framework than to Windows API and the C++ linker and does not mention the actual entry point signatures either. ... The documentation problem to which you allude is that it is the CRT entry point that calls one of the versions of main / WinMain that is defined in your program. ... This is the signature of the managed entry point that has nothing to do with native executables/DLLs. ...
    (microsoft.public.win32.programmer.kernel)