Hey guys,
Got a weird one.
The setup:
SQL Server repository, 13.5.1352 clients. Recently upgraded from 11.1, where everything worked.
Browser script (VB) which calls an MDG Technology-deployed script to generate a document. Templates in same MDG Technology.
Security enabled with Windows authentication. All users have both Run and Edit Script permissions.
For some users, the script fails when it hits the first call to
DocumentGenerator.DocumentElement().
Previous
DocumentGenerator calls all seem to work just fine. They are, in order:
DocumentGenerator.SetStyleSheetDocument("Numbered Headings - Black")
DocumentGenerator.NewDocument("")
DocumentGenerator.InsertLinkedDocument(linkedDoc)Then comes
DocumentGenerator.DocumentElement elementID, 0, "The template"... and that's all she wrote. The script breaks on that line, popping an error dialog which contains the line number but no error code or message.
If the user hits F8 and selects the same template, the generation works fine.
This is consistent:
Some users cannot run the script at all, other users can run the same script repeatedly without any problems.
For users who can't run the script, if they log in as admin (which has the full set of permissions), the script still breaks the same way.
In a different repository, the problem persists: the same users can't run the script.
Any bells ringing?
Could it be related to my zombie
custom-script-fragment-doesn't-work-when-invoked-through-the-API bug?
The template in this case does include a fragment, although this time it's a regular SQL fragment.
Is
DocumentGenerator fundamentally broken in 13.5?
/Uffe
