iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

Errores comunes ejecutando proyectos del Windows Azure Training Kit (WATK)
Errores comunes ejecutando proyectos del Windows Azure Training Kit (WATK) avatar

By Leave a Comment

 

1. Package restore is disabled by default. To give consent, open the Visual Studio Options dialog, click on Package Manager node and check ‘Allow NuGet to download missing packages during build.’ You can also give consent by setting the environment variable ‘EnableNuGetPackageRestore’ to ‘true’. MyTodo.WebUx.

Este error para algunos es fácil solucionarlo pero para otros es un poco más complicado, estos son los pasos:

a. En Visual Studio 2012 TOOLS->Library Package Manager-> Package Manager Console.

image

b. Luego hacer clic en Restore

image

 

2. System.Runtime.InteropServices.SEHException: External component has thrown an exception.

Ocurre cuando el proyecto Windows Azure, no es el proyecto que inicialmente se ejecuta. Solución:

Clic derecho en el proyecto y seleccionar Set As Start Up Project.image

3.  The remote server returned an error: (403) Forbidden.

Al momento de enviar notificaciones ese es el mensaje de estado de conexión devuelto, aparentemente es un tema de autorización pero la excepción lanzada es esta Channel URL incompatible with caller app. Para este caso se tiene una aplicación Windows 8 en Javascript y un web site en azure encargado de enviar las notificaciones. Solución:

El  nombre de la aplicación es diferente al nombre del paquete del archivo package.appxmanifest.

image

Es decir, este mismo nombre  es el id de la aplicación que se le envía en el objeto cuando se registra el canal para recibir notificaciones.

image

Luego ir al web site e intentar enviar una notificación, el mensaje debe ser Status Code OK – 200: Notification was accepted by WNS.

Failed to load the current WSDL. An XML error has ocurred. (Microsoft.BizTalk.TrackingCompiler) (BAM)
Failed to load the current WSDL. An XML error has ocurred. (Microsoft.BizTalk.TrackingCompiler) (BAM) avatar

By Leave a Comment

When we work with BAM, we have to ways to deploy the activities (XML) and the Tracking’s we have made. One of them is doing it by console using the following commands:

You have to be in this directory: C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking.

Once you are there you can apply them:

  • To deploy activity: bm.exe deploy-all -DefinitionFile
  • To deploy tracking: bttdeploy.exe

The other way to deploy the tracking file (.btt) is using the graphic interface call: Tracking Profile Editor (TPE).

The error which is showed in the title and in the next figures happens when you have made the .btt before and you want to open it for any reason.

This errors is shows up because the interface cannot load the orchestration assemblies that have interceptor in the activity.

The process you can follow is: without load the tracking profile, open the event source and select the orchestration schedule, select at least one of the assemblies which are involve in the tracking profile you tried to open before. After that, open the tracking profile normally and everything is going to work fine and is going to be loaded just as the follow figure shows:

 

 

RebuildIndexes in BizTalk Server
RebuildIndexes in BizTalk Server avatar

By Leave a Comment

En ocasiones para mejorar desempeño en el proceso de publicación y suscripción de BizTalk Server junto con las tareas de mantenimiento (jobs de Sql Server) que ya posee BizTalk Server, es conveniente como en toda base de datos hacer un rebuild de indices a las bases de datos de BizTalk.

A continuación relaciono los procedimientos almacenados creados que son los únicos para soportar este proceso:

Base Datos                  Procedimiento Almacenado

BizTalkDTADb              dtasp_RebuildIndexes

BizTalkMsgBoxDb       bts_RebuildIndexes

BizTalk Server solo soporta rebuild de indices cuando este se encuentra completamente parado, por lo que se recomienda parar todos los host instances y el SQL Server Agent antes de ejecutar estos procedimientos.

Si se llegara presentar un error al ejecutar bts_RebuildIndexes, ver la documentación que hay sobre el mismo en el siguiente link:

You experience blocking, deadlock conditions, or other SQL Server issues when you try to connect to the BizTalkMsgBoxDb database in BizTalk Server

 

Article ID: 917845 – View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft BizTalk Server, you experience blocking, deadlock conditions, or other Microsoft SQL Server issues when you try to connect to the BizTalkMsgBoxDb database.

Back to the top | Give Feedback

CAUSE

This issue may occur if one or more of the following conditions are true:

  • The Auto Create Statistics option is enabled on the BizTalkMsgBoxDb database.
  • The Auto Update Statistics option is enabled on the BizTalkMsgBoxDb database.
  • The max degree of parallelism option is set to a value other than 1 on the computer that is running SQL Server and that is hosting the BizTalkMsgBoxDb database.
  • You defragment or rebuild an index in the BizTalkMsgBoxDb database when BizTalk Server is processing data.
Back to the top | Give Feedback

RESOLUTION

To resolve this issue, use one of the following methods.

Method 1: Disable the Auto Create Statistics option and the Auto Update Statistics option

To resolve this issue, disable the Auto Create Statistics option and the Auto Update Statisticsoption on the BizTalkMsgBoxDb database in SQL Server.

Method 2: Set the max degree of parallelism option to 1

To resolve this issue, set the max degree of parallelismoption to 1 on the computer that is running SQL Server.

Method 3: Do not rebuild an index when BizTalk Server is processing data

To resolve this issue, do not run the bts_RebuildIndexes stored procedure or any SQL command that rebuilds an index in a BizTalk Server database when BizTalk Server is processing data.

NoteDefragmenting an index in a BizTalk Server database is not supported.

Back to the top | Give Feedback

MORE INFORMATION

The bts_RebuildIndexes stored procedure

The only supported method to rebuild an index in the BizTalkMsgBoxDb database is to run the bts_RebuildIndexes stored procedure. On BizTalk Server 2006 and later versions, you can run the dtasp_RebuildIndexes stored procedure to rebuild indexes in the BizTalkDTADb database.

Most of the BizTalk indexes are GUID-based. Many tests have shown that as long as the tables are not scanned, GUID-based indexes can perform better than identity-based indexes for BizTalk-specific workloads. This may cause fragmentation. However, because data flows in and out of the tables at a steady pace, fragmentation may not cause any issues. If lots of data is expected to build up in the BizTalkMsgBox database, you can periodically rebuild indexes during scheduled downtime. The same guidelines apply to the tracking database.

You can use the DBCC DBREINDEX SQL command to rebuild an index in the other BizTalk Server databases. For an example of how to use the DBCC DBREINDEX SQL command, right-click the bts_RebuildIndexes stored procedure, and then click Properties.

Note Microsoft only supports rebuilding database indexes during BizTalk Server downtime. You should stop all host instances and SQL Server Agent before you rebuild an index. When you run the bts_RebuildIndexesstored procedure in BizTalk Server 2006 and later versions, you may receive one of the following error messages:

Error message 1
Msg 5239, Level 16, State 1, Procedure bts_RebuildIndexes, Line 4
Unable to process object ID 674101442 (object ‘TrackingData’)
This database consistency checker (DBCC) command does not support this kind of object.
Error message 2
Msg 5239, Level 16, State 1, Procedure bts_RebuildIndexes, Line 4 Unable to process object ID 722101613 (object ‘TrackingData’) because this DBCC command does not support objects of this type.

This problem occurs because the TrackingData object is a view in BizTalk Server 2006 and later versions. To resolve this problem, do the following and then execute the bts_RebuildIndexesstored procedure:

  1. Comment out the following line in the bts_RebuildIndexesstored procedure. 
    DBCC DBREINDEX ('[dbo].[TrackingData]') WITH NO_INFOMSGS
  2. Add the following lines to the bts_RebuildIndexesstored procedure. 
    DBCC DBREINDEX ('[dbo].[TrackingData_0_0]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_0_1]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_0_2]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_0_3]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_1_0]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_1_1]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_1_2]') WITH NO_INFOMSGS
DBCC DBREINDEX ('[dbo].[TrackingData_1_3]') WITH NO_INFOMSGS
Back to the top | Give Feedback

Properties

Article ID: 917845 – Last Review: May 5, 2011 – Revision: 8.0
APPLIES TO
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
Keywords:
 kbbts kbtshoot kbprb KB917845
Back to the top | Give Feedback

Give Feedback

 

Was this information helpful?
Yes
No
Somewhat
How much effort did you personally put forth to use this article?
Very low
Low
Moderate
High
Very high
Tell us why and what can we do to improve this information
Back to the topBack to the top

©2012 Microsoft