Somehow one of my schemas got installed in BizTalk.System application even though it is not the default application on my BizTalk server 2006 R2 enterprise version. I need to undeploy it from there and install it in my targeted application. The problem is that we don't get any option to delete / move schema which are under BizTalk.System. Please suggest how can I do it? Additional info if needed: No suspended / dehydrated instances waiting. No application using the schema mentioned. Dll containing those schemas are removed from GAC. thanks in advance,
Hi, I did not try this myself but you could try to fool BizTalk by temporarily changing the 'isSystem' field the BizTalkMgmtDb. - Update table 'bts_application' in 'BizTalkMgmtDb' for the row that has 'nvcName' value 'BizTalk.System'. Set the 'isSystem' field to 'False'. - Restart BizTalk Admin Console. - Try to delete the schema. - Change the field in the database back to 'True'. - Restart BizTalk Admin Console. It it highly unrecommended to make changes to the BizTalk databases so try this as a 'last resort' option and at your own risk ;-). Make sure you have backups. I also really wonder how this schema got installed in the BizTalk.System application. HTH, Randal van Splunteren "Alok Kothana" <Alok Kothana@discussions.microsoft.com> wrote in message news:D4CC2DDB-B769-469D-A22D-502640E30BCE@microsoft.com... > Somehow one of my schemas got installed in BizTalk.System application even > though it is not the default application on my BizTalk server 2006 R2 > enterprise version. I need to undeploy it from there and install it in my > targeted application. The problem is that we don't get any option to > delete / > move schema which are under BizTalk.System. Please suggest how can I do > it? > > Additional info if needed: > No suspended / dehydrated instances waiting. No application using the > schema > mentioned. Dll containing those schemas are removed from GAC. > > > thanks in advance, >
Not sure if this will work. Try to undeploy the assembly from Biztalk Explorer in Visual Studio. "Randal van Splunteren" wrote: > Hi, > > I did not try this myself but you could try to fool BizTalk by temporarily > changing the 'isSystem' field the BizTalkMgmtDb. > > - Update table 'bts_application' in 'BizTalkMgmtDb' for the row that has > 'nvcName' value 'BizTalk.System'. Set the 'isSystem' field to 'False'. > - Restart BizTalk Admin Console. > - Try to delete the schema. > - Change the field in the database back to 'True'. > - Restart BizTalk Admin Console. > > It it highly unrecommended to make changes to the BizTalk databases so try > this as a 'last resort' option and at your own risk ;-). Make sure you have > backups. > > I also really wonder how this schema got installed in the BizTalk.System > application. > > HTH, > > Randal van Splunteren > > > "Alok Kothana" <Alok Kothana@discussions.microsoft.com> wrote in message > news:D4CC2DDB-B769-469D-A22D-502640E30BCE@microsoft.com... > > Somehow one of my schemas got installed in BizTalk.System application even > > though it is not the default application on my BizTalk server 2006 R2 > > enterprise version. I need to undeploy it from there and install it in my > > targeted application. The problem is that we don't get any option to > > delete / > > move schema which are under BizTalk.System. Please suggest how can I do > > it? > > > > Additional info if needed: > > No suspended / dehydrated instances waiting. No application using the > > schema > > mentioned. Dll containing those schemas are removed from GAC. > > > > > > thanks in advance, > > > >
Hi, Ok, I was curious and gave it a try. Both the 'Visual Studio' and the 'IsSystem' solutions seem to work. The 'IsSystem' solution is the only possible approach if visual studio is not installed on the server and you can not connect to the biztalk installation from a remote visual studio installation on another machine. This is very likely when this is a production server. HTH, Randal van Splunteren "FQ" wrote in message news:34736684-4DD8-4260-9B5D-D709F3B157CE@microsoft.com... > Not sure if this will work. Try to undeploy the assembly from Biztalk > Explorer in Visual Studio. > > > > "Randal van Splunteren" wrote: > >> Hi, >> >> I did not try this myself but you could try to fool BizTalk by >> temporarily >> changing the 'isSystem' field the BizTalkMgmtDb. >> >> - Update table 'bts_application' in 'BizTalkMgmtDb' for the row that has >> 'nvcName' value 'BizTalk.System'. Set the 'isSystem' field to 'False'. >> - Restart BizTalk Admin Console. >> - Try to delete the schema. >> - Change the field in the database back to 'True'. >> - Restart BizTalk Admin Console. >> >> It it highly unrecommended to make changes to the BizTalk databases so >> try >> this as a 'last resort' option and at your own risk ;-). Make sure you >> have >> backups. >> >> I also really wonder how this schema got installed in the BizTalk.System >> application. >> >> HTH, >> >> Randal van Splunteren >> >> >> "Alok Kothana" <Alok Kothana@discussions.microsoft.com> wrote in message >> news:D4CC2DDB-B769-469D-A22D-502640E30BCE@microsoft.com... >> > Somehow one of my schemas got installed in BizTalk.System application >> > even >> > though it is not the default application on my BizTalk server 2006 R2 >> > enterprise version. I need to undeploy it from there and install it in >> > my >> > targeted application. The problem is that we don't get any option to >> > delete / >> > move schema which are under BizTalk.System. Please suggest how can I do >> > it? >> > >> > Additional info if needed: >> > No suspended / dehydrated instances waiting. No application using the >> > schema >> > mentioned. Dll containing those schemas are removed from GAC. >> > >> > >> > thanks in advance, >> > >> >>
Thanks for the solution. I didn't find an "UnDeploy" option in Visual Studio though, "IsSystem" tweak worked. With that I found a better way to do it. Get application Id from 'bts_application' table and update table 'bts_assembly' setting 'nSystemProperty' to 0 and 'nApplicationId' to the application you want to move the assembly to. thanks again. Alok "Randal van Splunteren" wrote: > Hi, > > Ok, I was curious and gave it a try. Both the 'Visual Studio' and the > 'IsSystem' solutions seem to work. The 'IsSystem' solution is the only > possible approach if visual studio is not installed on the server and you > can not connect to the biztalk installation from a remote visual studio > installation on another machine. This is very likely when this is a > production server. > > HTH, > > Randal van Splunteren > > > "FQ" wrote in message > news:34736684-4DD8-4260-9B5D-D709F3B157CE@microsoft.com... > > Not sure if this will work. Try to undeploy the assembly from Biztalk > > Explorer in Visual Studio. > > > > > > > > "Randal van Splunteren" wrote: > > > >> Hi, > >> > >> I did not try this myself but you could try to fool BizTalk by > >> temporarily > >> changing the 'isSystem' field the BizTalkMgmtDb. > >> > >> - Update table 'bts_application' in 'BizTalkMgmtDb' for the row that has > >> 'nvcName' value 'BizTalk.System'. Set the 'isSystem' field to 'False'. > >> - Restart BizTalk Admin Console. > >> - Try to delete the schema. > >> - Change the field in the database back to 'True'. > >> - Restart BizTalk Admin Console. > >> > >> It it highly unrecommended to make changes to the BizTalk databases so > >> try > >> this as a 'last resort' option and at your own risk ;-). Make sure you > >> have > >> backups. > >> > >> I also really wonder how this schema got installed in the BizTalk.System > >> application. > >> > >> HTH, > >> > >> Randal van Splunteren > >> > >> > >> "Alok Kothana" <Alok Kothana@discussions.microsoft.com> wrote in message > >> news:D4CC2DDB-B769-469D-A22D-502640E30BCE@microsoft.com... > >> > Somehow one of my schemas got installed in BizTalk.System application > >> > even > >> > though it is not the default application on my BizTalk server 2006 R2 > >> > enterprise version. I need to undeploy it from there and install it in > >> > my > >> > targeted application. The problem is that we don't get any option to > >> > delete / > >> > move schema which are under BizTalk.System. Please suggest how can I do > >> > it? > >> > > >> > Additional info if needed: > >> > No suspended / dehydrated instances waiting. No application using the > >> > schema > >> > mentioned. Dll containing those schemas are removed from GAC. > >> > > >> > > >> > thanks in advance, > >> > > >> > >> >
