FIX: The error messages do not specify the object name when you experience a failure in the deployment task in Microsoft Visual Studio Team System Database Edition 2008 GDR

Article translations Article translations
Article ID: 970584 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When you import a schema model and then deploy a database project in Microsoft Visual Studio Team System Database Edition 2008 GDR, you receive error messages that resemble the following in the Output window:
Error TSD03041: Unknown permission type: EXEC
Error TSD02010: Incorrect syntax near SET.
Project_name.dbschema(0,0)Error TSD01234: Failed to import target model Test. Detailed message A fatal error occurred while the model was being imported.
However, the error messages do not specify which object causes the failure. Therefore, it takes you a long time to troubleshoot.

RESOLUTION

To resolve this problem, upgrade to Microsoft Visual Studio Team System 2008 Database Edition GDR R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970479 List of fixed issues in the Microsoft Visual Studio Team System 2008 Database Edition GDR R2

Note Microsoft Visual Studio Team System 2008 Database Edition GDR R2 replaces Microsoft Visual Studio Team System 2008 Database Edition GDR.

MORE INFORMATION

After you upgrade to Microsoft Visual Studio Team System 2008 Database Edition GDR R2, you will also receive the following messages:

Project_name.dbschema(0,0)Error TSD01234: The application encountered an unexpected error. To diagnose this problem, enable tracing.

How to enable the tracing

To do this, follow these steps:
  1. Locate the tracing.reg registry file under the following folder:
    %ProgramFiles%\Microsoft Visual Studio 9.0\VSTSDB
  2. Set the value of the TraceToLogFile registry entry to 1.
  3. Set an appropriate value for the TraceSwitch registry entry:

    Collapse this tableExpand this table
    Registry valueFunction
    1Trace only error level events
    2Trace warning and error level events
    3Trace informational, warning and error level events
    4Trace verbose and all other category level events
  4. Restart the Visual Studio IDE.

Note When you complete the trace diagnosis, you must set the values of the TraceToLogFile registry entry and the TraceSwitch registry entry to 0 to disable the tracing function. Otherwise, you will have performance issues.

The following table lists the registry entries that are included in the tracing.reg registry file.

Collapse this tableExpand this table
Registry nameRegistry typeDefault value
PrefixTimeDWORD00000001
PrefixPidDWORD00000001
PrefixThreadIdDWORD00000001
TraceSwitchDWORD00000000
TraceToLogFileDWORD00000000
TraceToDebugOutputDWORD00000001
DisplayCallStackDWORD00000000
UniqueLogFileDWORD00000001
EventIdsToTraceDWORD0001ffff
For more information about how to diagnose problems in the Visual Studio 2008 Team System Database Edition GDR and GDR R2, visit the following Microsoft Web sites:
http://blogs.msdn.com/gertd/archive/2008/08/17/diagnosing-problems.aspx
http://blogs.msdn.com/gertd/archive/2008/08/17/event-monitor.aspx

Properties

Article ID: 970584 - Last Review: July 16, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft Visual Studio Team System 2008 Database Edition
Keywords: 
kbqfe kbexpertiseadvanced kbsurveynew kbprb KB970584

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com