When running the Altiris Resource Generator, an error is returned:
Errors prevented resource exploration from being completed. The wizard cannot continue.c:\Documents and Settings\Administrator\Local Settings\Temp\a4-j07uc.0.cs(34695,16) : error CS0246: The type or namespace name 'Unknown' could not be found (are you missing a using directive or an assembly reference?)
The following error is placed into the Logging and Configuration Tool:
Application Name: LogicBase.Tool.Generator.exe
Process ID: 4004
Date: Aug-14-2008 08:37:38 AM
Log Level: Error
Log Category: Symantec.Workflow.Generators.ResourceComponents.WizardUI.NSConfigurationPage
Machine Name: KINGWF
Message: Compiling intermediate resource service failed: The type or namespace name 'Unknown' could not be found (are you missing a using directive or an assembly reference?)
The following error is into the Notification Server's a.log:
Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a35.log
Date: 8/14/2008 8:37:52 AM
Tick Count: 19724468
Host Name: KINGNS
Process: w3wp.exe (2940)
Thread ID: 3008
Description: The specified GUID does not refer to a item (GUID: 27d97657-77d9-4ebf-8076-618e2771562b)
Also have seen the following error with the resource generator:
Errors prevented resource exploration from being completed. This wizard cannot continue.
C:\Documents and Settings\Admin\Local Settings\Temp\1\mkldsfyx.0.cs(29,6): error CS1001: Identifier expected
could not read in object
Exception has been thrown by the target of an invocation.
Value cannot be null.
Parameter name: str
The Altiris Resource Generator will perform a search for all resource types and data classes, then will create a .net data type for them to be used with Workflow Solution. If a resource type contains an "unknown" child resource type name the generator will produce this error.
This problem appears with Inventory Rules. These rules (objects) can be used in Application Metering, Application Monitoring, Patch Management, Wise Package Studio Integration, and Inventory Solution.There are a number of combinations of solutions in Notification Server 6.0 that can cause it to become unparseable by the Workflow 6.x Resource Generator. These are highly environmental and typically cannot be easily transferred to another system for duplication.
Issues with the Resource Generator have been addressed in Workflow 7.
Notification Server 6.0
Workflow Solution 6.0Workflow Solution 6.5