Volume Activation Management Tool 2.0.67 critical bug
-
2010年4月28日 14:15
The latest version of VAMT - 2.0.67 has a bug that won't allow you to open saved lists.
I put in a ton of our keys yesterday and saved the list as a .CIL file. I went to open it later by opening then VAMT program and choosing Open list from the Actions bar and I see "An item with the same key has already been added". There isn't anything listed when I just open the program so I don't see what it's referring to.
I added the keys over again and saved a new file with a different name and the same thing happens!
Here's a screenshot.
http://img59.imageshack.us/img59/3710/capturve.jpg
MCTS 70-620 Certified
すべての返信
-
2010年4月28日 20:00I haven't been able to repro this, but then again, I might not have included as many keys as you did. Could you please list out your repro steps, including OS and the number of keys you've added to your CIL file?
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年4月29日 13:47
Hello Ted, here are my steps. I just added one key and got the same problem. The OS is Server 2008 R2 x64.
1. Open VAMT
2. Products > Add Computers (search within AD) > 291 computers
3. Select all > Update status > Current credentials > completed
4. Added Office 2010 KMS key + remarks > validate > Add Product Key
Save List as > 123.cil (on Desktop)
Close VAMT > open 123.cil
"An item with the same key has already been added"
MCTS 70-620 Certified -
2010年4月29日 22:03
Here's something from the VAMT team:
1) Are you doing an "open" or an "import"?
2) Are you touching the CIL file outside of VAMT? (e.g. opening it up in Notepad)
3) Would you be willing to send us your CIL file so we can see if something's up?If you want to send the CIL file, please send it to ted_msft@hotmail.com.
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年5月3日 18:01
I performed some more tests Ted, thank you.
1. Uninstalled VAMT 2.0
2. Uninstalled VAMT 1.0 ( I had the old version installed so I removed it)
3. Redownloaded VAMT from the provided link inthe forum.
4. Entered one product key (Office 2010)
5. Added one computer (my own) and updated the status
6. Saved file - no issues opening it again.
7. I then scanned all of AD but did not update the status.
8. Saved file - no issues opening it again.
9. Updated status on all the new computers added and saved the file.
10. Could not open with the same error I usually get.
There's something happening after the full list is added AND updated.I would like to send you my .CIL file, but due to the security concerns I am unable.
MCTS 70-620 Certified -
2010年5月3日 19:07
I understand that you won't be able to send the CIL file. The only way the VAMT team has been able to repro this so far was to simulate a machine in the CIL file with two NICs with identical MAC addresses. This would probably happen in a VM scenario. Are all your computers physical machines, or do you have VMs?
In your repro steps, instead of scanning all of AD and adding all new computers, what if you only added a subset of those, especially only physical machines?
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年5月3日 19:15
We do have about 20 VMs (ESX and MS Virtual PC) and 70 or so physical.
Would teamed NICs be affected by this?
I was thinking about searching by OU I don't see the option in VAMT to search by OU, could this be added?
I will add as many physical machines as I can and see what happens.
MCTS 70-620 Certified -
2010年5月3日 19:43
I found something. It appears VAMT is duplicating the NIC MAC address. This is from a regular physical desktop PC.
<Computer Name="xx" OSVersion="5.1.2600" OSEdition="Microsoft Windows XP Professional" NetworkType="Domain"
NetworkName="network.com" Id="e3f3f83c-f050-4d81-9117-xx">
<MacAddresses>
<MacAddress>00:11:11:CF:FC:xx</MacAddress>
<MacAddress>00:11:11:CF:FC:xx</MacAddress>
</MacAddresses>
<Products>
<Product>
<Sku Id="00000000-0000-0000-0000-000000000000" Name="Microsoft Windows XP Professional"ApplicationId="---" Description="" />
<LicenseInfo LicenseStatus="NotAvailable" LicenseStatusReason="0" GracePeriodRemaining="0"GenuineStatus="Unknown" TokenEnabled="false" LicenseIsAddon="false" />
<Version>5.1.2600</Version>
<PartialProductKey />
<ProductKeyId />
<KeyType>Unknown</KeyType>
<InstallationId />
<ConfirmationId />
<LastErrorCode>0</LastErrorCode>
<LastActionState>Successfully updated the product information.</LastActionState>
<LastUpdateTime>2010-05-03T12:36:08.5594139-07:00</LastUpdateTime>
<LicenseFamily />
</Product>
</Products>
</Computer>
MCTS 70-620 Certified -
2010年5月3日 20:42
In addition, I've found that computers that have the network adapter with "#2" at the end have this problem.
i.e. Intel(R) PRO/100 VE Network Connection #2
So it's like WMI calls are pulling the hidden/inactive NIC from the adapters list.
I thought this was only affecting a specific model, but that is not the case.I went through our CIL file and removed all the duplicate MAC entries and I can open my original file.
MCTS 70-620 Certified -
2010年5月4日 19:08I got the same error, and was completely stumped as to what it meant, or where it came from. By painstaking trial and error, I was able to determine the first machine or two that would trigger the bug, but until I found this page, I couldn't tell what characteristic of those machines was causing the bug. But after opening the .cil file in a text editor and deleting all instances where a given machine had a duplicate MAC address, the .cil file opened properly in VAMT 2.0.67. Of course, as soon as I refreshed the properties via the WMI queries, the duplicates were re-created, and the resulting file was impossible to open.
-
2010年5月4日 19:39
Did you happen to run VAMT from Server 2008?
I've found that Server 2003/XP can manage the affected computers (system>manage>connect to another computer) but Server 2008 fails with:
"Connecting to remote server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests....."
Since this is happening at the OS level, it seems Server 2008 (maybe even Vista/Win7) handle WMI requests differently which is causing the problem.
I wonder if I install VAMT on a Server 2003 machine and get the same results.
MCTS 70-620 Certified -
2010年5月6日 15:36
I was able to run VAMT from Server 2003 and got the same result. Should VAMT be updated to check for duplicate MAC entries?
MCTS 70-620 Certified -
2010年5月6日 20:28Thanks LDVG for bringing our attention to this issue. Your output and diagnostic information has been helpful in figuring out what the issue is and what the fix would be. I'm in touch with the VAMT team to see what they'd like to do about it, and I'll keep you posted (I'm being deliberately vague here... I don't want to imply or promise something that may not happen).
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年5月6日 20:29
No problem Ted, and thank you. It's always nice to diagnose and find a solution.
MCTS 70-620 Certified -
2010年5月10日 2:37
Hi Ted,
Has there been any progress on this issue? I've only just installed VAMT 2.0 to allow for Office 2010 activation/management but have encountered the same error as mentioned. I am running the tool on a Windows 2003 server platform.
-
2010年5月10日 16:22We are working to get an update soon, but I can't commit on a timeline. The issue here is identical MACs for machines. If you remove the computer that has identical MACs , then you'll be able to load up the CIL file. The alternative is to open the CIL file and delete the redundant entry. Note if you refresh the status of that computer, then the identical MAC will get refreshed, and the CIL cannot be opened.
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年5月17日 17:38
Hello all,
I will add another mention of this bug. I have 17 computers (out of around 150) that have this issue. I would love to find a fix for this. From what I can see all these computers are Windows XP or Windows 2000. Some are Servers but most are workstations.
Ted if you still need a CLI file I probably can get you the file with just these 17 computers on it.
Bernard
-
2010年5月20日 14:23
Have the same Problem thougt i was not able to use this Tool.
Had changed from VAMT 1.x in cause of Office 2010. Had no Problems before. Now this Tool is not useable. Runnig Windows Server 2008R2.
greetings rasti-ch
-
2010年5月20日 18:03
If you are feeling up to it, you can open the .CIL file in Notepad that you saved in VAMT and look for any duplicates of the MAC address fo each computer.
<MacAddresses>
<MacAddress>00:11:11:CF:FC:xx</MacAddress>
<MacAddress>00:11:11:CF:FC:xx</MacAddress>
</MacAddresses>Delete the duplicate so there is only one line, and repeat for any other computers that are like this. Save the file in Notepad and you will be able to open it again in VAMT.
MCTS 70-620 Certified -
2010年5月21日 10:10
Hi LDVG
with more than 600 Computers and horrible much Stuff in the cil File, i will wait for a new Version ;-)
greetings rasti-ch
-
2010年5月21日 11:12
-
2010年5月21日 11:56
OK Cleaned 12395 lines. Now can open the cil file again. But what happens after New Computers have been added???????
rasti-ch
-
2010年5月21日 17:58If new computers are added, or if you refresh the status of your existing computers, then you will hit the same issue. Please stay tuned regarding the fix for this issue.
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年5月26日 7:43
Hi,
I got the same problem. For some machines I got double entries for the MAC
<MachineAttribute AttribName="MachineMAC_NIC1" AttribValue="00:21:86:A0:25:2B"/>
<MachineAttribute AttribName="MachineMAC_NIC2" AttribValue="00:21:86:A0:25:2B"/>
<MachineAttribute AttribName="MachineMAC_NIC3" AttribValue="F8:98:20:52:41:53"/>and for some different machines I got the same MAC:
<MachineAttribute AttribName="MachineMAC_NIC2" AttribValue="20:41:53:59:4E:FF"/>
This MAC is used by the Microsoft RAS Async Adapter, which is build in software, not a physical device.So this will be a big trouble maker. :-(
Since the data is collected using WMI there should be an aditional expression in the where clause like
PhysicalAdapter = trueMaybe this will help for finding a solution,
best regards, Nils.
PS: I'm running VAMT 2.0 (.exe version 2.0.67.0) on Windows Server 2003 SP2
- 回答の候補に設定 Nikolay Sotskiy 2010年6月2日 17:29
- 回答の候補の設定解除 David Wolters 2010年7月30日 18:49
-
2010年6月2日 17:37
We've got same problem. Here is PF script which filters dublicate MACs out:
[PS] C:\>$hash=@{}
[PS] C:\>gc Old.cil | %{if($_ -like "*<Mac*</Mac*"){if($hash.$_ -eq $null) {$_ }; $hash.$_ = 1} else {$_}} | out-file -encoding ASCII New.cil- 回答の候補に設定 Nikolay Sotskiy 2010年6月2日 17:37
-
2010年6月10日 23:20
I am wondering if there is an update/fix on this issue, I am experiencing it also.
Additional problem I have found:
I have found that if there are VMWare Player virtual adapters, on the initial find and scan the computer will be there, and get saved with all information. However, upon reloading the tool and the saved list, the VMWare-MAC computers will not be displayed. Viewing the text file at this point will show the VMWare-MAC entry for the computer. However, if you save the list while it is not displaying the computer, it will discard the computer from the source file. This is on Windows 7 Enterprise computers. I do not know if this applies to computers with other virtual adapters, or other OS versions.
So, this entry for a computer does not display:
<MacAddresses>
<MacAddress>00:24:E8:FC:EA:8A</MacAddress>
<MacAddress>00:50:56:C0:00:01</MacAddress>
<MacAddress>00:50:56:C0:00:08</MacAddress>
</MacAddresses>However, if I edit it down to this, it works:
<MacAddresses>
<MacAddress>00:24:E8:FC:EA:8A</MacAddress>
</MacAddresses>So, in sequence:
1- Initial import of computers
2- Initial use of "Update Status"
3- Save List
4- Close List
5- Load previously saved List, Display is missing computers that have VMWare MAC addresses7- Close List or Exit without another save
8- View CIL in Notepad, you will see the missing computers are still present in text
9- Open or Load List, again notice the missing computers.
10- Save List
11- Close List
12- View CIL file in Notepad, the VMWare MAC computers are no longer present
-
2010年6月10日 23:44
I found further info on my previous note involving VMWare adapters.
If each computer record in the CIL file has unique VMWare virtual adapter MAC addresses, then they will all show up. The problem is only if the virtual MAC is a duplicate to another computer's virtual MAC. I believe the default is for VMWare player to use the same virtual MAC address, so any default install will have the same one, and thus conflict. From what I have seen, only the first computer with a conflicting MAC will show up, those later in the list will not be displayed. Change the virtual adapter MAC addresses and there is no conflict, then all computers will show up in the list.
-
2010年6月15日 9:42 Just thought I'd add my problem experience as well. Experienced no problems until one merry notebook popped-in returning a duplicate MAC address. Thankfully found this thread and will monitor it for when a solution is available. I have removed the offending MAC entry in the meantime.
- 回答の候補に設定 Murat Demirkiran 2010年7月13日 6:17
-
2010年6月16日 16:39
This has to be a bug. I am having the same problem opening a saved CIL file. The saved CIL file will not open until ALL extra MAC address from every machine are removed leaving a single MAC address per machine.
-
2010年6月17日 13:16
We've got same problem. Here is PF script which filters dublicate MACs out:
[PS] C:\>$hash=@{}
[PS] C:\>gc Old.cil | %{if($_ -like "*<Mac*</Mac*"){if($hash.$_ -eq $null) {$_ }; $hash.$_ = 1} else {$_}} | out-file -encoding ASCII New.cil
I believe this worked for me.
MCTS 70-620 Certified
-
2010年6月17日 13:19
I'm having the same issue, and I confirmed that it was duplicate MAC address causing it. Running VAMT 2.0.67.0 on a 2008 R2 Guest OS. Duplicate MAC address came from the Hyper-V server. Removed the duplicate MAC address using Notepad, opened the file, removed the server from the list. Can now successfully save and open the list.
-
2010年7月6日 12:11Very nice PS script...worked like a charm and I can finally reopen my 591 node list instead of starting from scratch every time. Looks like you spent some time with PS. Thanks a million!
-
2010年7月16日 8:14
We had the same problem, too. Your script worked like a charm! Thanks!
Best regards, John
-
2010年7月22日 13:44
We used the script as well and it worked fine, but having to run this script every time we want to re-open our .cil file is getting to be a nuissance.
Has there been an update on this issue, or a hotfix for VAMT?
Thanks
-
2010年7月23日 19:17
We are having this issue also. Can someone point me in the right direction on how to use the PF script provided in this posting?
Thanks
AWOJCIK
- 回答の候補に設定 aperezny 2010年8月4日 15:29
-
2010年8月11日 10:53Any fix in the pipeline for this issue?
-
2010年8月19日 13:22I'm curious too. Any updates?
MCTS 70-620 Certified -
2010年8月20日 7:13
Don't mean to be a nag but any news from the team Ted? The fix is ok , but when your adding new machine all the time and refreshing the list it becomes cumbersome.
If new computers are added, or if you refresh the status of your existing computers, then you will hit the same issue. Please stay tuned regarding the fix for this issue.
Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office -
2010年9月2日 17:26
I hate to be so persistent, but I'm reading our KMS server move and VAMT would be great to have working properly. Any updates?
Thak you
MCTS 70-620 Certified -
2010年9月2日 18:49Agreed. This tool is almost useless with this bug.
-
2010年9月3日 15:25
Thats a same that microsoft force us to use this kind of product and take so much time without provide us a fix
Thank for the script
-
2010年9月6日 16:19Bump
-
2010年9月7日 20:47
Hello everyone,
We have a KB posted that provides a fix for this issue: http://support.microsoft.com/kb/2383895
I don't have anything official to add about a permanent fix for this in the future, but if that changes I will update this thread again.
Regards,
Sean Francis
Microsoft Online Community Support
Office Deployment Support Blog: http://blogs.technet.com/odsupport- 回答としてマーク Ted WayMicrosoft Employee 2010年10月25日 2:38
-
2010年9月8日 13:46
Thank you Sean.
I just wanted to add that the error will occur on Server 2008 as well (since the KB says only Windows 7), but I'm not sure if this is considered a "Windows 7 based computer". I found the error on our Server 2008 R2 IT server.
MCTS 70-620 Certified -
2010年9月8日 23:42
Hello everyone,
We have a KB posted that provides a fix for this issue: http://support.microsoft.com/kb/2383895
I don't have anything official to add about a permanent fix for this in the future, but if that changes I will update this thread again.
Regards,
Sean Francis
Microsoft Online Community Support
Office Deployment Support Blog: http://blogs.technet.com/odsupport
While this fix can be helpfull, but it needs more information to become completely usefull.When I try this fix, all I get is this:
PS C:\script> .\Scrub.ps1 new.cil
File C:\script\Scrub.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-
help about_signing" for more details.
At line:1 char:12
+ .\Scrub.ps1 <<<< new.cil
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeExceptionOk, so I followed the rabbit down the hole and got this:
PS C:\script> set-executionpolicy remotesigned
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): [I hit "y"]
Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft
.PowerShell' is denied.
At line:1 char:20
+ set-executionpolicy <<<< remotesigned
+ CategoryInfo : NotSpecified: (:) [Set-ExecutionPolicy], UnauthorizedAccessException
+ FullyQualifiedErrorId : System.UnauthorizedAccessException,Microsoft.PowerShell.Commands.SetExecutionPolicyComma
ndIt turns out that all Windows 7 OS's by default block this kind of script running and the note on the bottom of the KB article "Note: You may have to change Set-ExecutionPolicy to RemoteSigned depending on your powershell configuration" is less than helpful when faced with another access denied error even though I am logged in as admin of both the domain and the local box. I checked the security on the above mentioned registry key and found that I was indeed allowed full permissions to it. Any thoughts? Perhaps a tad more explanation could help out that KB?
-
2010年9月9日 13:32
Hello everyone,
We have a KB posted that provides a fix for this issue: http://support.microsoft.com/kb/2383895
I don't have anything official to add about a permanent fix for this in the future, but if that changes I will update this thread again.
Regards,
Sean Francis
Microsoft Online Community Support
Office Deployment Support Blog: http://blogs.technet.com/odsupport
Sean, it sounds like a grim situation: "for this in the future." Does that mean the issue is considered fixed with the provided KB? I hope not.
MCTS 70-620 Certified -
2010年9月9日 21:32
The issue is not just on a windows 7 but also on a XP sp3 pc.
thanks.
-
2010年9月15日 19:04
Hello everyone,
We have a KB posted that provides a fix for this issue: http://support.microsoft.com/kb/2383895
I don't have anything official to add about a permanent fix for this in the future, but if that changes I will update this thread again.
Regards,
Sean Francis
Microsoft Online Community Support
Office Deployment Support Blog: http://blogs.technet.com/odsupport
This was kind of a tough solution/workaround but it did resolve my issue. The only gotcha is the "Restricted" script execution policy set on servers. After building the script, I ran the following commands in the powershell:PS C:\script> get-executionpolicy
Restricted
PS C:\script> set-executionpolicy unrestricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expos
you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y
PS C:\script> .\ScrubCil.ps1 saved.cil
PS C:\script> set-executionpolicy restricted
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y
Jason -
2010年11月6日 0:37Hi
I have also run into the problem with the VAMT tool running on a Windows 2003 server. I am unable to open my cil file I get An item with the same key has already been added" error. I been following this thread, Is the only solution to the problem to run the powershell script from http://support.microsoft.com/kb/2383895.
Is this doable on my Windows 2003 server so I can open my cil file again?. Also every time I update in the vamt tool is the same issue going to happen, and will I need to run the powershell script everytime?.
Is there any other workarounds for this serious problem?
Thanks, urgent assistance is required please.
-
2011年3月4日 10:56
Hi,
Is there a solution to this problem yet? I tried the script thing but it did not fix my problem, ended up giving me some things I am trying to figure out.
I will appreciate some useful info for solving this. Or suggestions for some other more reliable tool I can use to manage my licenses?
-
2011年3月4日 12:13
Until now there is no other solution.
And yes, the PS script is not easy to use because it seems not to be possible to run it just with a double click...
-
2011年3月14日 18:07We reverted back to ver 1.2 and that seems to work fine for re-opening the .CIL files. Hope to see a solution for ver 2 soon.
-
2011年3月14日 19:32The original post in this thread goes back to April 2010. Why is Microsoft not fixing this tool?
-
2011年3月22日 10:09
Realising this is an old thread... Just thought I'd add this bit of info for anyone else who comes across the above problem when setting the execution policy.
Due to UAT, you need to right click on your powershell icon and click Run As Administrator in order to perform a set-executionpolicy RemoteSigned.
This only needs to be performed once.
-
2011年5月11日 15:22Just bumping this I guess. Does MS doesn't even use their own tool and see how much a nuisance this is?
MCTS 70-620 Certified -
2011年5月11日 15:50The issue is now over a year old and there is still no corrected version available. It would be nice to see an update on such an easy fixable bug!
-
2011年5月13日 13:51Why no update or fix?
-
2011年6月2日 7:39
Same problem here as well. Still no fix on this?
-
2011年6月16日 9:04Still same issue here, very cumbersome re-run the script. Any ETA?????
Tony -
2011年8月18日 13:47Are you going to fix this? It's been well over a year now!
-
2011年11月18日 19:55Are there any plans to fix this with a new release? Running a FixIt tool (which didn't work in my case anyway), is not a solution if you have to use the tool every time you Update Status.
-
2012年2月20日 18:48Just started our implementation of MS Office 2010 Pro+ and ran into this same problem, using XP SP3 as the host machine for VAMT 2.0. After all this time is there still no fix? What a time waster to enter all the info over and over again with each activation!
-
2012年2月29日 20:03
Hello everyone,
I apologize for the inconvenience this issue has caused you while trying to use VAMT 2.0 in your environments.
I would like to invite you to try the prerelease version of VAMT 3.0 which is now available in the Windows Assessment and Deployment Kit (ADK) for Windows 8 Consumer Preview. The ADK is available for download here: http://go.microsoft.com/fwlink/?LinkID=232339
This release fixes this and many other issues, and introduces new features and support for new products. You can find additional information about VAMT 3.0 here http://technet.microsoft.com/en-us/library/hh824953.aspx
Please note that VAMT 3.0 requires SQL Server. If you have an existing SQL server available in your environment, VAMT can use it. If not, simply check the "SQL Server" option at the ADK installation's feature selection page to install a free copy of Microsoft SQL Server Express Edition.
Eric Bluestein [MSFT]. Software Development Engineer II - Microsoft Windows Team. This posting is provided AS IS with no warranties, and confers no rights.
- 回答の候補に設定 Eric Bluestein 2012年2月29日 20:03
-
2012年3月1日 7:23
Thanks for the update Eric! But I need some help:
I Installed the ADK with only the VAMT selected. After the install I started VAMT and selected an already installed SQL Server 2008 R2 Standard in our network. The previously created Database was there, too, so I selected it. When I click connect I get "The specified database is not a valid VAMT database". Thats correct, it's empty. How do I get the base structure? I found no *.sql files, no installer of some kind and nothing on TechNet.
Could you please help me out?
-
2012年3月1日 18:16
Meilon,
It's not necessary to create a database for VAMT ahead of time, VAMT will create its own. You can specify the name of your existing SQL server in the "Server" field (if you're using a named instance of SQL, you may need to specify <server name>\<instance name> syntax to find the server).
In the "Database" field, simply type a name for the new database. When you click "Connect", VAMT will create the new database for you and begin using it.
Thanks!
-Eric
Eric Bluestein [MSFT]. Software Development Engineer II - Microsoft Windows Team. This posting is provided AS IS with no warranties, and confers no rights.
- 編集済み Eric Bluestein 2012年3月8日 3:31
-
2012年3月8日 1:49I too Installed the ADK with only the VAMT selected. After the install I started VAMT and selected an already installed SQL Server 2008 R2 Express Instance . I typed in the name of the new database in this case "preVAMT3" and clicked connect. It goes through the motions to create it and then I get the following error, "The specified database is not a valid VAMT database".
-
2012年3月8日 3:44Dwayne,
This is not an issue I have seen before, but I'd be happy to help you troubleshoot it.
If you launch the system Event Viewer (Start -> type "event viewer" OR Start -> Run -> type "eventvwr.msc") and then expand "Applications and Services Logs" in the tree on the left, you should see a log for VAMT named "Volume Activation Management Tool".
I would expect there to be one or more Error entries from "VAMT Runtime" that might shed some more light on this issue. Could you please let me know if there are any error messages in the log?
Thank you,
-Eric
Eric Bluestein [MSFT]. Software Development Engineer II - Microsoft Windows Team. This posting is provided AS IS with no warranties, and confers no rights.
-
2012年4月17日 8:40
I saw the same error this evening, using the Windows 8 Consumer Preview version of ADK (8250), running on Windows 8 Consumer Preview (8250), using SQL Server 2008 R2 Express.
When running VAMT and connecting to the default SQL Server instance of ".\ADK", a timeout error was generated in the event log. But when specifying "SERVERNAME\ADK", it worked fine. So that's a potential workaround. (This may be related to the SQL Server 2008 R2 Express configuration, but I don't see any obvious reason - the databases were listed in the drop-down, and even with the error, the database was created.)
Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus
.png)
