cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
DotnetSolutions
Level 5

Microsoft C++ exception: FNPNS::TSM::CDoesNotExistException at memory location ...

Microsoft C++ exception: FNPNS::TSM::CDoesNotExistException at memory location...

What's the cause for this exception? We have this in our native C++ projects using the FNP 11.6 API and Visual Studio 2005 (not causing any crashes). It seems to occur at every API function call.

Edit:
The exception comes from FLEXnet Publisher at every API call and seems to be handled internally by FNP.
Labels (1)
0 Kudos
(2) Replies
DotnetSolutions
Level 5

Ok, since nobody seems to know anything about this I'll post the answer I got from the support:

These exceptions are thrown by design to communicate that an object or section, for example, does not exist in trusted storage. It is often completely valid for such an item not to exist in Trusted Storage.

The ATL exception similarly is thrown by Microsoft design, from memory it is related to our setting ATL security code.

Whilst a concern for the performance impact of exception throwing has historically been an issue, this is regarded as less so nowadays. The time for exception throwing/catching a standard exception is in the region of a 1000th of a millisecond – at least on Windows.
0 Kudos

Is this explanation of exceptions correct now in 2020? Version of FNP is 11.16.

0 Kudos