CMS - CAST Management Studio on Documentation - V2

CMS - Contacting CAST

Mon, 01 Jan 0001 00:00:00 +0000

Contacting CAST

For Sales, Product Support or General Inquiries, please contact our headquarters or your regional office directly: http://www.castsoftware.com/discover-cast/contact.

CMS - Copyright Notice

Mon, 01 Jan 0001 00:00:00 +0000

Copyright Notice

This publication pertains to the current release of CAST PRODUCTS and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of the agreement. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical or otherwise, without the prior written permission of CAST.

CMS - Limitations

Mon, 01 Jan 0001 00:00:00 +0000

Architecture Models

When using Architecture Models in the CAST Management Studio, all models must be valid before generating a snapshot, whether they are involved in an application or not. If this is not the case, the following error message will be displayed:

No architecture checker model file. Cannot define architecture checker model.

Interdependencies between Applications within the same Analysis Service

Situation:
You cannot run actions such as “Generate Snapshot” or “Run analysis” on an Application if another Application is invalid and both Applications are hosted in the same Analysis Service.

CMS - Windows Debugger Interference

Mon, 01 Jan 0001 00:00:00 +0000

Windows Debugger Interference

When you run an analysis using the CAST Management Studio on a computer where a debugger is installed, Windows is configured to run that debugger for each application that runs into a GPF.

If you launch a Run analysis or a Generate a Snapshot action using the CAST Management Studio, and one step in that action turns into a GPF, then the CAST Management Studio will continue the action, ignoring the fact that one step has actually failed. In this case, the Windows Debugger has intervened to stop the faulting application, however, the CAST Management Studio interprets the intervention as the application terminating successfully.