Page 1 of 1

Hanging updating Note

Posted: Mon Feb 23, 2015 2:11 pm
by jhicks
I just downloaded the app to try it out. When I try to create a Note the application hangs and becomes unresponsive. At first I thought it might be related to special characters like : or = in the note text but that doesn't seem to be the case. Started new blank help file, added note, and tried to save with the default text. No go.

All other elements seem to work just fine.

Windows 8.1 x64.

Reopened file and ran validation. Got this message:

Validation Status: FAILED

Parser Errors:

MS Parser reported this error:
Code = 0xc00ce014
Source = Line : 11 Char : 18
Error Description = Element '{}verb' is unexpected according to content model of parent element '{}details'.
Expecting: {}synonyms, {}copyright.

Source text where the error occured:


Hanging updating Note

Posted: Mon Feb 23, 2015 2:11 pm
by SAPIEN Support Forums
This is an automated post. A real person will respond soon.

Thank you for posting, jhicks.

Did you remember to include the following?
  • 1. Product, version and build (e.g. Product: PowerShell Help Writer 2015, Version & Build: 1.0.9. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
    2. Specify if you are running a 32 or 64 bit version
    3. Specify your operating system and if it is 32 or 64 bit.
    4. Attach a screenshot if your issue can be seen on the screen
    5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***

Re: Hanging updating Note

Posted: Mon Feb 23, 2015 2:18 pm
by jhicks
As a followup, I imported comment based help from a module (very nice), updated the Note property and didn't have any problems.

Re: Hanging updating Note

Posted: Mon Feb 23, 2015 4:19 pm
by davidc
These issues will be resolved in the next service release.

Thank you for reporting them.