SmartAssembly 6

The error report is not associated with a valid project ID

This page describes what to do if the error message 'The error report is not associated with a valid project ID' is displayed when viewing an error report. 

Possible causes

Error reports contain a unique project ID, which associates the error report with a particular build of your assembly. The project ID is used to define which map file SmartAssembly should use to de-obfuscate the stack trace in the error report.

This error message can be shown for four main reasons:

How to fix

The appropriate fix depends on the exact cause:

You have moved your copy of SmartAssembly

If you moved your copy of SmartAssembly from another computer, but you did not move the database and/or map files, the map file might not have been found.

See About map files for information on how to move the map files.

SmartAssembly was invoked from Visual Studio not running as administrator

When invoked from Visual Studio, administrator privileges are required for SmartAssembly to update the database table which maps project IDs to map files.

Rebuild your assembly, ensuring that you run Visual Studio as an administrator.

You built the assembly on one computer and you are trying to open the error report on a different computer

The error report cannot be opened unless the computer where you are opening the map file has access to the map file.

Ensure that you set a network location to store the map files, which both computers have access to.

For more information, see Configuring reporting on multiple computers.

The assembly was not marked as released (SmartAssembly 6.2 and earlier)

In order to avoid useless map files taking up disc-space unnecessarily, SmartAssembly 6.2 and earlier deleted map files automatically 180 days after the last report relating to the associated assembly was received. SmartAssembly assumes it was a test build and is no longer used.

If you did not mark the assembly as released, and the map file has been deleted, you cannot view new error reports for that build.

This behavior was changed in SmartAssembly 6.5.

If you continue to experience problems, please contact Redgate support.

Didn't find what you were looking for?