Skip to main content
A
Anonymous
March 26, 2013
Question

s1000dMenu.jsxbin error in FrameMaker 11

  • March 26, 2013
  • 2 replies
  • 1258 views

I have read a discussion about this error message elsewhere in the forum, but it did not seem exactly pertinent to our issue.

To make updates easier to role out to our users, have our Structure directory in a location that is outside the FrameMaker installation directory. With the move to FrameMaker 11, this error message began to proliferate in our console logs:

Script Error :

Error Message      : csdp is undefined

Script, Line#   : C:\Program Files (x86)\Adobe\AdobeFrameMaker11\startup\s1000dUtilities.jsxbin,  107

We have no need of S1000D, but the workaround is to recursively copy the S1000D directory into the proper location in our external Structure directory. I can live with this less-than-elegant solution but it would be better if we didn't have to clog up disk space with a large number of unnecessary files.

Anyone have a suggestion on how we can get FrameMaker 11 to ignore S1000D?

Thank you,

--larry0

This topic has been closed for replies.

2 replies

C
craigede
Participant
March 28, 2013

I, too, began getting messages regarding s1000dUtilities.jsxbin starting a couple of days ago. But I am still on Framemaker 10 and have done nothing to alter my installation (except for the automatic updates). Here is what I am getting:

Error Message      : undefined is not an object

Script, Line#   : C:\Program Files (x86)\Adobe\AdobeFrameMaker10\startup\s1000dUtilities.jsxbin,  111

Script Error :

Error Message      : undefined is not an object

Script, Line#   : C:\Program Files (x86)\Adobe\AdobeFrameMaker10\startup\s1000dUtilities.jsxbin,  182

Obviously, something has changed, but who know what?

Thanks.

Craig

Ian Proudfoot
Ian Proudfoot
Legend
March 27, 2013

Larry,

If you move the s1000dUtilities.jsxbin file, it will still be registered at its original location.

Try this:

  1. Open the Script Catalog.
  2. Select "Registered" from the view scripts options.
  3. If there is a reference to s1000dUtilities.jsxbin in the registered scripts list, select it then click Unregister.

Ian

A
Anonymous
March 27, 2013

Thank you, Ian.

This is a partial solution. The flood of messages in the FrameMaker console log is gone. We still have an initial error message upon FrameMaker startup, which users have to dismiss before continuing. I'd rather have the extraneous S1000D files installed than make our writers do that every time they start up.

Or, I could convince my company to get into an industry where S1000D is required.

--larry0

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices