Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Error and Event Messages

Visual Studio 2008

Visual Studio Team System Architecture Edition informs you about successful and unsuccessful operations by displaying error messages and event messages. Some error messages and event messages have unique ID numbers. These numbers have the format VSnnnn.

The explanations for these errors or the suggested actions for resolving these errors will be updated on the TechNet Events and Errors Message Center as new information becomes available. To find the latest information, visit the Events and Errors Message Center at http://go.microsoft.com/fwlink/?LinkId=67617 and search for the error message ID or message text.

The following table lists Architecture Edition error and event messages that have unique ID numbers. The table lists these messages in ascending numeric order.

Message

ID

VS1000: The distributed system designers encountered an error with the assembly {0}.

VS1000CouldNotInstantiateProviderManager

VS1001: The distributed system designers encountered an error with the assembly {0}.

VS1001InvalidAssembly

VS1002: The distributed system designers encountered an error with the assembly {0}.

VS1002WrongVersion

VS1003: The distributed system designers encountered an error with the assembly {0}.

VS1003NoClass

VS1004: The distributed system designers encountered an error with the assembly {0}.

VS1004NoCtor

VS1005: The distributed system designers encountered an error with the assembly {0}.

VS1005WrongType

VS1006: The filename specified, '{0}', is not a valid System Definition Model (SDM) filename. A valid SDM filename cannot: 1) contain more than 255 characters 2) contain Unicode control characters or Surrogate characters 3) contain any of the following characters: / : \\ ~ && % ; @ ' " ? < > | # $ * }} {{ , + = 4) start with an underscore ( _ ) 5) start or end with a period ( . ) Change the filename to a valid format, or contact the provider of the component.

InvalidSdmFileName

VS1007: The Application Designer cannot set the component {0} as implemented. Try the action again. If the problem persists, contact the provider of the component.

CannotSetComponentAsImplemented

VS1008: The Application Designer cannot set the port {0} as configured. Try the action again. If the problem persists, contact the provider of the component.

CannotSetPortAsImplemented

VS1010: Visual Studio cannot import the selected file. It is not a compatible prototype file. Select a compatible prototype file.

InvalidPrototypeFile

VS1011: Cannot find the prototype file for this toolbox item: {0}. To fix this condition, drag the toolbox item to the diagram, add the item from the diagram to the Toolbox, and export the item again.

ToolboxItemMissingFile

Warning: VS1012: Visual Studio might not implement this application. To implement applications that run using Internet Information Services (IIS) on a remote server, you must have administrator privileges on that server.

ConfirmProjectCreationDialogIISRemoteWarning

VS1020: Visual Studio cannot import the selected file. The prototype in the file has already been imported.

PrototypeSourceIsDest

VS1021: The prototype file already exists in the Toolbox: {0}. To overwrite this file, click OK.

OverwritePrototype

The following table lists Architecture Edition error and event messages that do not have unique ID numbers. The table lists these messages in alphabetical order.

Message

ID

The application diagram and any open system or deployment diagrams will be saved and closed. To close this diagram without saving, first close any system or deployment diagrams.

ForceCloseDiagramsFromACD

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.