Initscripts 2012.08.3-1 /proc/bus/usb does not exist
After upgrading initscripts
[2012-08-28 15:26] upgraded initscripts (2012.08.2-1 -> 2012.08.3-1)
boot.log shows the following error message
mount: mount point /proc/bus/usb does not exist
I didn't find any recent post about this issue. I recall that something changed maybe with /proc and /sys some weeks/months ago, but I get this warning message since the initscripts update.
Any idea? Or is it a sign that I should familiarize myself with systemd?
Update:
I missed this thread, same issue, sorry: https://bbs.archlinux.org/viewtopic.php?id=147916
Someone may want to delete this one. Thanks.
Last edited by siriusb (2012-08-30 12:42:38)
After upgrading initscripts
[2012-08-28 15:26] upgraded initscripts (2012.08.2-1 -> 2012.08.3-1)
boot.log shows the following error message
mount: mount point /proc/bus/usb does not exist
I didn't find any recent post about this issue. I recall that something changed maybe with /proc and /sys some weeks/months ago, but I get this warning message since the initscripts update.
Any idea? Or is it a sign that I should familiarize myself with systemd?
Update:
I missed this thread, same issue, sorry: https://bbs.archlinux.org/viewtopic.php?id=147916
Someone may want to delete this one. Thanks.
Last edited by siriusb (2012-08-30 12:42:38)
Similar Messages
-
"mount point /proc/bus/usb does not exist" -deux
Hi everyone!
I've installed arch 6.0 on a laptop running on the 2.4 SCSI kernel.
Indeed, /proc/bus/usb does not exist. I'm not sure why...
I'm not sure how to get the full directory either.
I've viewed this thread and this thread and followed the advice to change the usb line in my fstab to usbfs /proc/bus/usb usbfs defaults 0 0. I'm not sure what I was expecting, but the problem didn't go away and my /proc/bus/usb did not magically appear afterwards.ok, I did the update. The usb directory is still not there.
Since I don't have permission to make the directory myself (even as root), I guess I'll call it quits here.
I'm using the arch 7.0 cd now. The problem has gone away. -
Mount point /proc/bus/usb does not exist
Does anybody know why this mount point would not be there? There is indeed a directory at that location...
hi,
kleptophobiac wrote:Does anybody know why this mount point would not be there? There is indeed a directory at that location...
sarah31 wrote:perhaps it is the syntax in your fstab?
Nope, it's a miracle, concerning the scsi kernel only, AFAIK. Some devs have
rebuilt with some module variations but no clue so far where it does come
from.
It goes like that:
usbcore loads usbfs (when it shouldn't), at a time when proc is not mounted.
usbfs tries to create the dir and throws that error. Later on boot process
hotplug corrects that. So it's a kind of annoyance, but it does feel
uncomfortable as long as no one where it does come from :-/
-neri -
/proc/acpi/button does not exist.
/proc/acpi/button does not exist. Any ideas?
or, anyone knows which module is the owner of /proc/acpi/button?
Thanks!I am having the same problem, even with a stock kernel. There is no power button
device and therefore acpi_listen does not detect putton press events. I am on a
Thinkpad T420s, which used to work until a recent reinstall. Here are the
outputs that were originally requested (most of them look quite similar to
enicham's):
% lsmod | grep evdev
evdev 11784 27
% ls /dev/input
by-id event10 event14 event2 event6 mice
by-path event11 event15 event3 event7 mouse0
event0 event12 event16 event4 event8 mouse1
event1 event13 event17 event5 event9 mouse2
% cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:101b"
P: Phys=usb-0000:00:1a.0-1.2:1
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004/input/input2
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0
B: REL=143
B: MSC=10
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech Unifying Device. Wireless PID:4002"
P: Phys=usb-0000:00:1a.0-1.2:2
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0005/input/input3
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=12001f
B: KEY=837fff072ff32d bf54444600000000 1 30f948b17c007 ffff73fad941dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=100000000
B: MSC=10
B: LED=1f
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=3
B: KEY=4000 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/LNXVIDEO:01/input/input7
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0019 Vendor=17aa Product=5054 Version=4101
N: Name="ThinkPad Extra Buttons"
P: Phys=thinkpad_acpi/input0
S: Sysfs=/devices/platform/thinkpad_acpi/input/input8
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=33
B: KEY=18040000 0 10000000000000 0 1501b00102004 c000000001104000 e000000000000 0
B: MSC=10
B: SW=8
I: Bus=0003 Vendor=04f2 Product=b221 Version=0752
N: Name="Integrated Camera"
P: Phys=usb-0000:00:1a.0-1.6/button
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/input/input9
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input10
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0001 Vendor=14f1 Product=506e Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input12
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
U: Uniq=
H: Handlers=event14
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
U: Uniq=
H: Handlers=event15
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input11
U: Uniq=
H: Handlers=mouse1 event16
B: PROP=9
B: EV=b
B: KEY=6420 30000 0 0 0 0
B: ABS=260800011000003
I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input18
U: Uniq=
H: Handlers=mouse2 event17
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3
% pacman -Qi linux
Name : linux
Version : 3.14.5-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26=3.14.5
Depends On : coreutils linux-firmware kmod
mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels
of your country
Required By : nvidia
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 71950.00 KiB
Packager : Tobias Powalowski <[email protected]>
Build Date : Sun 01 Jun 2014 01:40:01 AM EDT
Install Date : Sat 07 Jun 2014 02:21:14 PM EDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
% journalctl | grep dev/input
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event6 (Power Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event3 (Video Bus)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event4 (Lid Switch)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event5 (Sleep Button)
Jun 07 19:14:16 unmensch systemd-logind[286]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons) -
MBAM - SCCM 2012 Reports - Error: the 'MBAM Policy' view does not exist
Hi
I have installed MBAM with SCCM 2012 integration. A single server install with SQL server 2012. Mostly it has gone smoothly and laptops are being encrypted and pins stored and recoverable. The problem I have is reports are not showing. I get the following
error message.
"Error: the 'MBAM Policy' view does not exist"
Any ideas why this is? I get the same error message with all 4 reports.Hi Slycy,
There is another thread that seems to be a similar issue
here that may help you. The last post in particular has a number of steps that you can use to speed up creation of the views:
Just for future reference, there are quite a few things that have to happen before the view is created. This is merely how CM works.
Make MBAM MOF changes
Select TPM spec version in hardware inventory
Install MBAM CM Integration feature
Perform a machine policy refresh cycle on a client to get the MOF changes that need to be inventoried
Perform hardware inventory
Update MBAM Supported Computers collection membership. The machine should appear if it meets the criteria
Run another machine policy refresh on the client so that the Configuration Baseline will come down
Make sure that the MBAM agent has woken up once
Evaluate the Configuration Baseline
The MBAM views should be created now.
You don't have to do this for every machine, but this is the process to speed it up. If you let CM do it, it could take over a week before the view is created the first time, depending on when Hardware inventory runs, etc.
Hope this helps,
David -
Hi,everybody. I'm a new guy here and glad to learn from you.
I have written "none /proc/bus/usb usbfs devgid=x,devmode=x 0 0" in fstab to enable usb devices in system running on VirtualBox. For years it works fine. But maybe after some kernel updating, this folder is disappeared. Then the usb device can't mount on virtual system any more. I search the web for some answers but none is working, including using /sys/bus/usb/drivers as an alternative. And the error message is "mount: unknown filesystem type 'usbfs'" when I try to do this.
So, could anyone give me some tips? Thank you for your considrateness.Thank you!
brebs wrote:
There's already a thread on this.
You should see an entry with the current timestamp (i.e. the same time as when you plugged in the USB device while running virtualbox) in /dev/vboxusb/
Last edited by blackguester (2012-09-05 11:45:37) -
So I have to setup the usb scanner and first I have to check the output of the "cat /proc/bus/usb/devices" command, but I don't have that file. I compile my own kernel so which is the option I have to enable to see it? Thanks.
It was in the kernel documentation, sorry.
mount -t usbfs none /proc/bus/usb
Now, I want it to be mounted at boot. I wrote the command in the rc.local file, but if I wanted to do that with the fstab file the line would be:
none /proc/bus/usb usbfs user,auto 0 0
Right? -
My ipod nano 3rd generation, when connected by usb, does not show up in itunes, does not show up on my computer, does not seem to charge by the wall charger. It just has a black screen. Any ideas for me?
I've run diagnostics. Can't find device. I've tried resetting. The toggle has been turned on and off.Cable works fine on my other iPod. Reset by pressing menu and center button together for 6-10 seconds. Left it to charge for many hours. Started acting up while running. Suddenly the music stopped playing but my Nike + was still working for the rest of my run. Took it straight it home and plugged it in to the wall to recharge since the battery was fairly low. Looked like it recharged ok but then screen went blank and now does it not show up on iTunes, does not seem to recharge by the wall charger (apple wall charger plugged into a surge protector in India). I have turned the hold switch off and on many times.
Sounds like a repair issue, which is not easy to do in India :( -
VMM 2012R2 UR4 - Version 3.2.7768.0
Not sure when this started happening since I haven't had to update or create a new RunAs account in VMM in some time, but every time I do, either through the console or through PowerShell it throws an error about The specified directory service attribute
or value does not exist. The VMM Service account is the same as it always has been, and other than this issue everything with VMM is working fine. The full text of the error message is below.
I am hoping someone has some ideas because I don't have any more at this point.
------------------- Error Report -------------------
Error report created 12/22/2014 9:43:33 AM
CLR is not terminating
--------------- Bucketing Parameters ---------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=3.2.7768.0
P3(assemblyName)=Microsoft.Cryptography.DKM.dll
P4(assemblyVer)=3.2.7510.0
P5(methodName)=Microsoft.Incubation.Crypto.GroupKeys.ADRepository.EnumerateKeys
P6(exceptionType)=System.Runtime.InteropServices.COMException
P7(callstackHash)=d0d2
SCVMM Version=3.2.7768.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=3.2.7768.0
Executable Name=vmmservice.exe
Executable Version=3.2.7768.0
Base Exception Target Site=140712994535888
Base Exception Assembly name=System.DirectoryServices.dll
Base Exception Method Name=System.DirectoryServices.DirectoryEntry.Bind
Exception Message=The specified directory service attribute or value does not exist.
EIP=0x00007ffa67d15bf8
Build bit-size=64
------------ exceptionObject.ToString() ------------
System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_IsContainer()
at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container)
at Microsoft.Incubation.Crypto.GroupKeys.ADRepository.EnumerateKeys()
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.FindNewestKey()
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.GetCurrentKeyAndUpdate(KeyPolicy& keyPolicy)
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.Protect(MemoryStream plaintext)
at Microsoft.VirtualManager.Engine.DKMUtil.Protect(Byte[] data)
at Microsoft.VirtualManager.Engine.CryptoHelper.Protect(Char[] data)
at Microsoft.VirtualManager.Engine.CryptoHelper.Protect(SecureString data)
at Microsoft.VirtualManager.DB.RunAs.RunAsDBAccess.UpsertRunAsAccount(RunAsAccountData data, SqlContext context, Boolean isAdd, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.AddOrUpdateObjectInDB(SqlContext context, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.UpdateDB(SqlContext ctx, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.Update(SqlContext ctx, Boolean setCredential)
at Microsoft.VirtualManager.Engine.AuthorizationManager.SetRunAsAccountTask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
--------------- exception.StackTrace ---------------
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_IsContainer()
at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container)
at Microsoft.Incubation.Crypto.GroupKeys.ADRepository.EnumerateKeys()
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.FindNewestKey()
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.GetCurrentKeyAndUpdate(KeyPolicy& keyPolicy)
at Microsoft.Incubation.Crypto.GroupKeys.DKMBase.Protect(MemoryStream plaintext)
at Microsoft.VirtualManager.Engine.DKMUtil.Protect(Byte[] data)
at Microsoft.VirtualManager.Engine.CryptoHelper.Protect(Char[] data)
at Microsoft.VirtualManager.Engine.CryptoHelper.Protect(SecureString data)
at Microsoft.VirtualManager.DB.RunAs.RunAsDBAccess.UpsertRunAsAccount(RunAsAccountData data, SqlContext context, Boolean isAdd, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.AddOrUpdateObjectInDB(SqlContext context, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.UpdateDB(SqlContext ctx, Boolean setCredential)
at Microsoft.VirtualManager.Engine.RunAs.RunAsAccount.Update(SqlContext ctx, Boolean setCredential)
at Microsoft.VirtualManager.Engine.AuthorizationManager.SetRunAsAccountTask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
------------- StackTrace from handler --------------
This is the call stack from where the exception was caught, not where it was thrown.
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.WriteReportTextFile(TextWriter reportFile)
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonExceptionReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonCenter.ReportException(Exception e, WERReportOptions options, String& localReportPath)
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
-------------------- Assemblies --------------------
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Module=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Version=4.0.30319.34014
BuildType=retail
Product=Microsoft® .NET Framework
VMMService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Version=4.0.30319.34003
BuildType=retail
Product=Microsoft® .NET Framework
TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NativeMethods, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Common, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.IndigoAccessLayer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Skuhelper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Errors, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Remoting, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Version=4.0.30319.34230
BuildType=retail
Product=Microsoft® .NET Framework
System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Version=4.0.30319.34230
BuildType=retail
Product=Microsoft® .NET Framework
Engine.Adhc.Operations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.TaskRepository, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ImgLibEngine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VmmHelperHost, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VirtualizationInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NetworkServiceInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ClusterUtil, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VMWareImplementation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Version=3.2.7672.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManagerTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Backup, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Version=3.2.7672.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.BitBos, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Version=6.3.9600.17090
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
WsManWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
SqmWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Deployment, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement.ResourceModel, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ImgLibOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Version=4.0.30319.34230
BuildType=retail
Product=Microsoft® .NET Framework
Engine.CustomProperties, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.VmOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.MomDal, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.PxeServer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.P2VCommon, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
PatchExtractor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Engine.ConfigurationProviders, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GatewayInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Version=6.3.9600.16384
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
Microsoft.CapacityManager.Modeling.Store.ModelLibrary, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CustomPropertyTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.UMOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Tasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Version=3.2.7672.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ServiceOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GoalState, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Version=3.2.7768.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CloudService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Version=3.2.7672.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
WSManAutomation, Version=3.2.7768.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
wmiWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Module=D:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
--------- Extra Data for Watson Report -------------
Error Reporting Enabled=True
*** Extra Data ***
Process ID = 4356 (0x1104)
Managed Thread ID = 18
Native Thread ID = 5520 (0x1590)
MCITP | VCP4 | VCP5Hi,
You want userPrincipalName, not userPrincipleName.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms680857%28v=vs.85%29.aspx
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing) -
Nvidia module does not exist in /proc/modules
Hi!
I compiled kernel with grsecurity from AUR. everything goes fine, and my system boot with a new kernel.
Only thing i have a problem with, is nvidia module.
I'm tried to makepkg nvidia with ABS way, but i get errors:
ERROR: Module nvidia does not exist in /proc/modules
In order to use the new nvidia module, exit Xserver and unload it manualy.
I"m trying to do:
modprobe nvidia
but i get:
FATAL: Error inserting nvidia (/lib/modules/2.6.32-grsec-ARCH/kernel/drivers/video/nvidia.ko): Cannot allocate memory
When i write :find /lib/modules -name nvidia.ko
I get: lib/modules/2.6.32-grsec-ARCH/kernel/drivers/video/nvidia.ko
When i write: uname -r
I get: 2.6.32-grsec-ARCH
Any help please..you have to reboot after installing nvidia because the > 2.6.34 kernel has nouveau and is using the card.
-
Visual studio 2012 the name "initializeControl" does not exist in the namespace in visual WebPart
Hi All,
I'm trying to create a visual webpart in SharePoint 2013 using Visual Studio 2012 and I am seeing that the file ascx.g.cs
is missing and i have this error in file ascx.cs : the name "initializeControl" does not exist in the namespace.
And like i said i use VS2012 Ultimate
Can anyone Help me please!!!
thanks.In most scenarios this is caused by some error in code preventing Visual Studio from generating the designer file. You could try to undo the latest changes and see whether the item is being generated or not. Additionally you could try checking if the custom
tool is still associated with the Visual Web Part SPI in the Properties Window.
w: http://blog.mastykarz.nl | t:
@waldekm | c: http://mavention.codeplex.com | c:
http://mavention.nl -
Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)
Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578304
Exit facility code: 1204
Exit error code: 0
Exit message: The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
Start time: 2015-01-09 10:19:12
End time: 2015-01-09 10:20:07
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for AS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS_SHP: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS_SHPWFE: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DREPLAY_CTLR: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DREPLAY_CLT: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BIDS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
Machine name: IDCSQLTST11
Machine processor count: 2
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: E:\SQL_Server_2012_StandardEdition\x64\setup\
Installation edition: Standard
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: DOMAINAA\SQLADMINS
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME:
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: DOMAINAA\user12345
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: true
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DOMAINAA\SQLADMINS
SQLTEMPDBDIR: F:\TempDB
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: E:\SQLData
SQLUSERDBLOGDIR: D:\SQLLog
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services - SharePoint
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Reporting Services Add-in for SharePoint Products
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Data Quality Client
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Distributed Replay Controller
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Distributed Replay Client
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Writer
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: Documentation Components
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
Message:
The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
HResult : 0x84b40000
FacilityCode : 1204 (4b4)
ErrorCode : 0 (0000)
Data:
SQL.Setup.FailureCategory = InputSettingValidationFailure
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
Message:
The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
HResult : 0x87d00006
FacilityCode : 2000 (7d0)
ErrorCode : 6 (0006)
Data:
DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
SettingName = CLTRESULTDIR
WatsonData =
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this .. -
HT1476 iphone 5 usb does not charge in my 2013 Honda Accord. Is there a fix for this issue?
iphone 5 usb does not charge in my 2013 Honda Accord. Is there a fix for this issue? It will connect via bluetooth but when I go to connect the usb charger it states that it is not compatible or you never get the charging display on your iPhone 5. It charges just fine when I use the AC charger in the house. At first I thought it may have been the cord but the same cord works fine in the house too. This causes problems when you take long trips and don't have any way to charge your phone while on the road. Are there any upcoming fixes/iupdates either to the software or usb cord that will fix this?
Are there any upcoming fixes/iupdates either to the software or usb cord that will fix this?
Are there any upcoming fixes/updates to the software of your Honda Accord that will fix this? Everything works fine except when the car is put into the equation? -
I have a server 2012 machine running RDP and a PDC running SBS 2007. Every once a while all my users get an error saying "The specified domain either does not exist or could not be contacted". After waiting ~5-10 minutes the issue resolves itself.
I believe it has something to do with the syncing between the two but am not 100% sure. Anyone know a fix or what I should look at?
Jerry THi Jerry,
Thank you for posting in Windows Server Forum.
After referring to your error, it seems to have DNS issue in your case which can’t locate the DC. Please check the setting related to DNS issue as following. (Below quoted from
this thread)
If this is the case, I would recommend proceeding like that:
1. Make sure that each DC has only one IP address in use and ONLY one NIC card enabled (Other NICs should be disabled)
2. Make sure that public DNS servers are configured as DNS forwarders and not in IP settings of DCs
3. Choose a healthy DC / DNS server and make each DC point to it as primary DNS server
4. Make each DC / DNS server point to its private IP address as secondary DNS server
5. Make sure that needed ports for AD replication are opened: http://technet.microsoft.com/en-us/library/bb727063.aspx
6. Check your DNS zones and remove manually all obsolete / unused DNS records for DCs
Once done, run ipconfig /registerdns and restart netlogon on each DC you have.
On the client computer, run ipconfig /flushdns and check again.
Hope it helps!
Thanks.
Dharmesh Solanki -
SCCM 2012 R2 - Reporting Services Point installation - "The Datasource does not exist"
Hi all,
Quick bit of background, we have SCCM 2012 R2 installed on a Windows 2012 R2 server. We have the SQL back end off box, configured on a SQL 2012 R2 server running on a Windows Server 2012 R2 cluster. Then there is yet another server which runs the reporting
services. I've just tried installing the Reporting Services Point on the srs server but it doesn't appear to have worked that well. Here's the info i've got back:
A] Site Status > Reporting services point:
SMS_SITE_SYSTEM_STATUS_SUMMERIZER
Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\NA-SQLR01.in.tna.local" has changed to Failed.
B] The last message from the SMS_SRS_REPORTING_POINT Component Status is "Site Component Manager successfully installed this component on this site system"
C] Here's the first chunk of info which appears in the srsrp.log file:
SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 4204 (0x106C).
This is a SRS Reporting Point Role as SRSRP registry key exists.
Waiting for changes for 0 minutes
Timed Out...
Set configuration
Check state
Check server health.
Successfully created srsserver SMS_
Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
Reporting Services is running
The DataSource does not exist.
[sqlserver.local\SQL1] [SCCM_XXX] [ConfigMgr_XXX] [sqlreportserver.LOCAL]
[SQL2012] [1] [] [xxx\SCCM2012Server]
Confirmed version [11.0.5058.0] for the Sql Srs Instance.
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
Extract resource language packs if exists
Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
Looking for 'English (United Kingdom)' resources
Looking for 'English' resources
Found resources for 'English'
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
Item, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
Folder, String Parent, Property[] Properties)
(!) SRS root folder was reported missing
STATMSG: ID=7405 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=sqlreportserver.LOCAL SITE=P01 PID=2120 TID=4204 GMTDATE=Wed Apr 08 08:56:05.349 2015 ISTR0="ConfigMgr_XXX" ISTR1="sqlreportserver.LOCAL"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
Registry change
Waiting for changes for 1 minutes
After this point i simply get the following info messages looping endlessly:
Set configuration
Check state
Check server health.
Successfully created srsserver
Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
Reporting Services is running
The DataSource does not exist.
[sqlreportserverlocal\SQL1] [SCCM_XXX] [ConfigMgr_P01] [sqlreportserver.LOCAL]
[SQL2012] [1] [] [XX\SCCM2012Server]
[1] [0]
Confirmed version [11.0.5058.0] for the Sql Srs Instance.
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
Extract resource language packs if exists
Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
Looking for 'English (United Kingdom)' resources
Looking for 'English' resources
Found resources for 'English'
System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_P01' cannot be found.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
Item, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~ at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~ at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
Folder, String Parent, Property[] Properties)
(!) SRS root folder was reported missing
Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
Registry change
Waiting for changes for 1 minutes
Has anyone come across this issue before? Must admit, I'm not too hot on the sql side of things so any advice or suggestions would be greatly appreciated. Thanks in advance!Hi guys, cheers for the swift response.
Garth, i can access SSRS in IE from the SCCM box and it looks a-ok.
Paul, nope can't say I've done any configuration of reporting services - the whole thing has been set up by the database team. Having had a trundle through Reporting Services Configuration Manager, it seems the Database team have set up SSRS in line with
the walkthrough you posted.
Since i'm not seeing the ConfigMgr_XXX folder appear in SSRS I'm wondering if there's something preventing SCCM from being able to create it. The message
"Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions
granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation" sounds like the account SCCM is leveraging to perform the install might not have the right permissions in SSRS. Do i need to delegate specific rights to the NT
AUTHORITY\SYSTEM account in SRS perhaps?
Maybe you are looking for
-
WAN MINIPORT ERROR AND TAKES A LONG TIME TO SHUT DOWN
Few days before,my device manager was showing yellow exclamation mark in wan miniport(ikev2),SSTP and another area, which i can't remember.So i searched on forums and use another software to fix this.The link to website is - https://www.vpnhosting.
-
How do I create a configuration profile that has wireless settings including a manual proxy server.
I can configure the wireless network using the IPCU but cannot set the proxy server settings. I'm sure that this is simple but just can't work it out!
-
Any idea similar to this view???
i'm still new in learning Java..by using JCreator LE, i've try to make a simple task..can anybody help me by giving any idea similar to my task attach below? import java.awt.event.*; import java.awt.*; class Aplikasi { public static void main(St
-
When will ISO 8 be available for iMacs
24-inch, Early 2008
-
QS 2002 933 weird flakiness since stormy weather
MY HT Mac has been doing some oddball flakiness since the last t-storm earlier in the week. It is plugged into a surge protector ( with reset breaker) and the surge protector got tripped when the storm hit. I thought no big deal, reset the surge prot