The content from the BizTalk training course from Microsoft has now been publically released. You can download this video content and the VM for learning BizTalk 2010 here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=38c2ccfc-510c-4627-a33c-95e9d19f3478.
Enjoy!
#1 by Colin on May 24, 2011 - 4:21 am
It’s a pity the labs have been limited to Windows Server 2008 and Hyper-V. It rules my team out of utilizing them.
#2 by Ben Cline on May 24, 2011 - 7:45 am
I hear your feedback, lots of companies are using VMWare or other VM products. My current company uses VMWare extensively too.
Sorry about that.
Ben Cline
#3 by Colin on May 24, 2011 - 9:53 am
No need to apologise
We are one of those companies; we use VMWare.
#4 by lyf on August 24, 2011 - 11:20 am
I have just downloaded the VM and extracted the files. I notice some of the folders (namely bt10d-02 and bt10d-03) are missing after the extract. Anybody knows why?
Also I tried to use the import tool to import the VM but I keep getting below error:
Creating symbolic link to the VM base image.
Cannot create a file when that file already exists.
Importing VM – Invoking WMI method ImportVirtualSystemEx.
In progress… 10% completed.
Error Code:32773
ErrorDescription: Import failed because the virtual machine must have a new iden
tifier. Select a new identifier and try the import again.
Hope someone can guide me on this.
BizTalker
#5 by clineer on August 24, 2011 - 11:33 am
BizTalker,
What import tool are you using? Is this a Hyper-V tool?
I can report to the right people at Microsoft that published the new training about the issue if you can give me just a little more detail about what is happening.
Thanks,
Ben
#6 by lyf on August 24, 2011 - 9:12 pm
Ben,
Thanks.
Ok, after I extracted the files, there are a few folders namely “VM” folder that contains all the virtual machines files (19 VM folders for the different lab) and a “Setup” folder that contains a importVM.exe utility. From the readme file (root folder), the instruction is to run using this utility to import in the VM under a base vhd.
The command to use is something like this:
importvm.exe “Full path to base image of vhd”
The vhd is called biztalk2010demo.vhd and can be found in the “common” folder.
I’m posting from work so I can’t refer to the stuff I downloaded back home, but details above should be correct.
BizTalker
#7 by lyf on September 5, 2011 - 2:59 am
Ben,
Any help you can give on this?
Thanks
#8 by Ben on November 16, 2011 - 3:00 pm
I am getting below error while trying to import the vms to hyper-V:
2011-11-16T15:53:27 [DATA_BEGIN] ———- Exception Details ———-
Error while importing VM bt10d-01.
—– Exception Details —–
System.ApplicationException: Error while importing the Hyper-V configuration settings for bt10d-01. —> System.Management.ManagementException: Invalid namespace
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at ImportVM.VirtualMachine.ImportVirtualSystemEx()
— End of inner exception stack trace —
at ImportVM.VirtualMachine.ImportVirtualSystemEx()
at ImportVM.ImportVM.Main(String[] args)Error while importing VM bt10d-01.
—– Inner Exception Details —–
System.Management.ManagementException: Invalid namespace
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at ImportVM.VirtualMachine.ImportVirtualSystemEx()
2011-11-16T15:53:27 [DATA_END] —————————
#9 by clineer on November 16, 2011 - 3:52 pm
Benyang,
I am not that knowledgeable about whether this is a problem with what you are doing or something wrong with the VMs. But I will email the BizTalk product group about this and let you know.
Thanks,
Ben Cline
#10 by clineer on November 24, 2011 - 11:03 am
Hey, on Monday (11/21/2011), I did send your information into the BizTalk product team and they are working on finding someone to look into your problem.
Thanks,
#11 by clineer on December 8, 2011 - 3:36 pm
Ben, Tony Meleg from Microsoft posted some suggestions below. Hope this helps.
#12 by Frank on March 7, 2012 - 8:49 pm
Hi Biztalker,
Have you found the solution to your issue? I have exactly the same error, and I am wondering if you can share your solution?
Thank you
Frank
#13 by clineer on March 8, 2012 - 12:18 pm
Did you see Tony’s comments below about starting with the Lab 1 Hyper-V file?
Thanks,
#14 by Ben on March 8, 2012 - 1:34 pm
I wasn’t able to resolve the issue.
Hope Frank could get a solution this time.
#15 by Ben on March 8, 2012 - 1:35 pm
MSFT didn’t offer a solution for it since they couldn’t reproduce it.
Now you are able to.
#16 by Tom Fuldner on December 6, 2011 - 4:59 pm
I am receiving the same error as documented above….Invalid Namespace…when running the HyperV import utility. Has there been any feedback as yet to the question you asked last month?
#17 by clineer on December 7, 2011 - 11:20 pm
A couple weeks ago I had reached out to a Microsoft contact but I have not heard anything more from them. I will check again with them to see if anything has changed. Thanks for posting, they were interested if anyone could reproduce the problem. I will post a reply here if I hear anything more. Thanks!
#18 by clineer on December 8, 2011 - 3:35 pm
Tom, Tony Meleg from Microsoft posted below with some suggestions.
#19 by Tony Meleg on December 8, 2011 - 2:34 pm
I just tried to repro this… everything worked just fine for me… A couple of things to check… (a) – Did you run the import tool from a command prompt using Admin credentials (right click command prompt and select Run as Administrator (b) Make sure that all the rar files have successfully downloaded – I has a problem with one and had to download again. The ONLY thing I did differently, was use a short install folder c:\btstk – that might help – maybe there is a path length issue..
#20 by Tony Meleg on December 8, 2011 - 2:40 pm
Also, on your question about the missing hyper-v VM’s 02 and 03 – this is because Labs 2 and 3 use the same Hyper-V start point as lab 1. If you read the lab docs, you will see that for labs 2 and 3, they refer you to start the Lab 1 hyper-V file.
#21 by clineer on December 8, 2011 - 3:34 pm
Tony, a big thanks for trying this out for us!