Forum Replies Created
-
Posts
-
Hi John,
The test document does validate successfully against the schema. I am able to generate an instance successfully as well. When I drop this test document in the receive location, it gets picked up and the above error message shows up in the administrator console.
Michael
does your flat-file schema correctly validate a test document in the schema editor? And does this test document fail when submitted through the receive location?
John D.
Hi,
But in my case both are 64bit.I have a solution for this.
a)
Stop the Distributed Transaction Coordinator serviceb)
Open Add/Remove Programs -> Add/Remove Windows Components -> Select
Application Server then click the Details button. Uncheck "Enable network DTC
access". Click OKthrough rest of Wizard; even if that check box is
unchecked.c)
Open and command window and type: msdtc -uninstall. Hit Enter.
d) In
the registry, remove the following keys (if they still
exist):HKEY_CLASSES_ROOT\CID
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\MSDTC
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\MSDTC
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
e) Reboot the
Serverf)
Open a command window and type: msdtc -install. Hit Enter.
g) Go
through Add/Remove Programs -> Add/Remove Windows Components -> Select
Application Server then click the Details button. Check "Enable network DTC
access"if
needed (see note below). Click OK through rest of the
Wizard.Note:
Step f) only re-populates the HKLM\Software\Microsoft\MSDTC\Security folder.
You
must complete step g) above to populate the rest of the registry keys, like
HKLM\Software\Microsoft\MSDTC\MTXOCI, HKLM\Software\Microsoft\MSDTC\Setup and
HKLM\Software\Microsoft\MSDTC\XADLL. You can go through step g) above without
checking Enable Network DTC Access, but you must click Next…Next…etc to go
through the Add/Remove Components
Wizard.Solved…
My server is a 64-bit machine while BizTalk is still 32-bit. The COM error received is due to a bug in running a 32-bit app on a 64-bit platform. The solution was to install a hotfix from Microsoft.
256340_ENU_x64_zip.exe is the name of the file I installed. The Microsoft KB article is #910907.
Thanks for everyone looking into this.
Michael
As JohnD said… I’ll second it.
BizTalk does not fit into a standard .net build model. You will have endless problems doing anything that changes the .net version numbers on a continuous basis.
I have seen this requirement before and it’s possible to do using find and replace scripts on the raw text file of the maps and pipelines referencing .net assemblies. I just question the value of this since I think a cleaner approach is to version the MSI’s you use for deployment. (you lose side by side version ability but that’s usually ok since BizTalk doesn’t play will with that either without additional effort)
I’ve never tied to do this. If it’s not a production server, I’d just Unconfigure BizTalk and reconfigure it to use the new SQL. That way all the accounts will be created for you with the correct permissions.
Then you need to reinstall you applications.
You might want to look in the SDK if there is anything on moving to a new SQL. Again, not something I’d even try to do if there was any other way…
Anonymous,
as a minimum, you need a development box with BizTalk and Visual Studio installed. You also need SQL Server somewhere (can also be on the same box).
After that, you can work remotely with Remote Desktop.
Or you can install the BizTalk client bits on a client developer machine and point to the remote BizTalk database. (At least, this was possible in BTS 2004 – I haven't checked in 2006).
John D.
Anonymous,
I have certainly seen applications that zipped in the send pipeline, so technically it should be no problem.
As to size, I wouldn't worry. First, you're not processing it – it's just a blob. Second, BTS 2006 handles bigger files more comfortably than prvious versions.
As to timing – why worry – you're going out to FTP and inherently async protocol.
John D.
Sergiy,
why do you allow the build to bump the version number all the time? (It's just an attribute of the assembly, so you choose its behaviour). I usually only change version numbers when something significant has changed. For small projects you can do this manually, for larger ones you could have a script.
Or perhaps I misunderstood your issue?
John D.
Well "King" Henry,
Ru using the same input and Output Schemas in tht other project.
If yes then I think you have set some property within the Map itself which is causing this issue.
I think thrz a small mistake some where….
Can you just mail me the MAP,Input and Output Schema and the Input xml file u are facing problem with at [email protected]
We tried installing SQL Server 2005 on the same machine and reconfigured Biztalk to point to it, but found out all Applications are lost, then we copied management db from Express to 2005, got an error saying it needs reference to Express SQL Server\RuleEngine Db.
I'm gonna to restore everything back and exports MSI, and rebuilt a biztalk dev machine, to see if i can import the MSI onto the new server.
Is there anyone tried similar thing and succeeded?
[quote user="Anonymous"]
hi i had done that already , but exception is uncaught . i want to know that exception type which we gave in a property of catchException .
[/quote]
It will certainly be slower to process than a smaller file and will take up more resources. How much will depend a lot on what you expect to do with it, though. If you don't really care about the file contents, then just do it the other way around: compress it during receive with a custom component in a receive pipeline; this will be far more efficient and will help conserve a lot of biztalk resources for the remainder of processing.
Nishil,
thanks for the reply.
This is exactly how I set it up. After I wrote the post I checked another project (in the same solution) and discovered the Value Mapping was working perfectly – what would cause the *exact* same construct to work in one project and not the other?
Henry
