There is a technote posted here to address an issue with DOORS Word export throwing error

POS SHAPE NO LAB MOVEWINDOW FAILED - 1400

http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI37067

For some reason the article is not accessible by folk without certain priviliges.

Can anyone access the link and post the solution?

Sean

Re: POS SHAPE NO LAB MOVEWINDOW FAILED - 1400
knobutan - Thu Apr 28 02:05:06 EDT 2016

I am not sure what the issue exactly is, but here is local fix information.

1. Open Tools > Options > Settings

2. Disable the following options.

- Open last displayed folder or project on startup
- Prompt to open all modules from last session on startup
- Remember size, position and splitter width for Database Explorer window

Hope it helps.

Re: POS SHAPE NO LAB MOVEWINDOW FAILED - 1400
DOORSguy - Thu Mar 09 10:11:17 EST 2017

A user showed me that they were having this problem this morning. First time I've seen it.

One other "after effect" of this error is that the user could not exit DOORS, so I had them end the task in the Task Manager, and re-launch DOORS.  I noted that the Welcome window appeared after login. When the user tried to open the same module that they had when they first saw the error, the error occurred again, and I got a look at the full diagnostic log and errors in the dxl interaction window.

Having not yet seen this post and the APAR record, the only "interesting" thing that I noticed from either the diagnostic log or the dxl errors was the following in the dxl interaction window:

Backtrace:

<config/baseWindowCalbacks.inc:1823>

<wizard/welcome/welcomewiz.dxl:706>

I had the user end the DOORS task again (because we had triggered the error again). When they logged back in, I had them uncheck the "Show this screen at startup" check box in the Welcome window.  They tried, again, to open the module that seemed to "cause" the error, and the error was gone.

I have no idea if there is any causal link here or just dumb luck.

No need to respond; I just thought I'd add this data to the knowedgebase. FYI, the user is running DOORS 9.6.1.4 on Windows 7 Enterprise v6.1.

Bill Adelman

Re: POS SHAPE NO LAB MOVEWINDOW FAILED - 1400
Mar1ja - Thu Oct 11 04:59:47 EDT 2018

Hello all,

I can see that this is a long-forgotten topic, but please let me know if there is a new information regarding this DOORS behavior?

Best regards,

Marija BLAGOJEVIC

Re: POS SHAPE NO LAB MOVEWINDOW FAILED - 1400
Sven Schubert - Fri Oct 12 06:20:51 EDT 2018

If you can reproduce this at will, please open a support ticket, so that DOORS support and DOORS development can work with you to gather more details on the issue and find a fix.

Re: POS SHAPE NO LAB MOVEWINDOW FAILED - 1400
DRAMANESANGARE - Tue Jul 09 07:30:24 EDT 2019

Hello @DoorsXLAustralia,

Here is the answer found in the link you have shared :

APAR status

• OPEN

   

Error description

• Under certain scenarios, DOORS Client brings up a DOORS Report
  error "pos shape no lab MoveWindow failed - 1400".
  
  Clicking on OK, doesn't take the error away.
  
  This is also accompanied with DXL Interaction Window
  'EXCEPTION_ACCESS_VIOLATION' along with a DOORS Diagnostic log.
  
  DXL Interaction window error is added here for reference:
  ---------------------------------------
  -R-E- DXL: <config/baseWindowCallbacks.inc:1560> An unexpected
  error has
  occurred: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in
  module
  doors.exe at 000000004058C9A2
  
  Backtrace:
   <config/baseWindowCallbacks.inc:1818>
  -R-F- DXL: <config/baseWindowCallbacks.inc:1560> internal error,
  please
  submit a bug report
  Backtrace:
   <config/baseWindowCallbacks.inc:1818>
  -----------------------------------------
  
  This behavior can occur soon after logging into DOORS or when
  opening Modules.
  
  The only way to overcome this issue is to kill the DOORS Client
  session from the Task Manager.
  

   

Local fix

• After disabling the 3 (Three) options under DOORS Explorer
  Window - Tools - Options - Settings - "Miscellaneous" section,
  the aforementioned behavior was not seen.
  

   

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

Hope it will be helpful for other users too.

Regards,