Server 2008 r2 Dec 10 patches stops snipping tool

I have 3 2008r2 terminal servers, somehow after the Dec 10, 2014 patches the snipping tool no longer works on two of the servers.
I am running Office 2010 Pro Plus
Error message is
The Snipping Tool in Not working on your computer right now. Restart your computer and try it again.
Wayne

Hi,
Good to hear that and thanks for sharing.
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Similar Messages

Window server 2008 r2 error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"

Hi All
Please help
my server not working showing display error window server 2008 r2 error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"
Please help me how to resolve this issue ???
thnaks !!!

Hi,
If there is any external device plug into your computer, please unplug it and restart the Server.
You can also test the issue in Safe mode.
If it can boot into Safe mode, please update any driver has yellow warning on it, also check if the dump file is existing under %SystemRoot%\, if so, please help to post back for our research.
Kate Li
TechNet Community Support

Windows Server 2008 R2 SP1 - BSOD Stop Error 0x00000050 RDPWD.SYS

Hi all,
I have been struggling with a BSOD for the past 5 weeks and have scoured the web trying in vain to find someone else with the same issue.
Environment:
8 x 2008 R2 SP1 Windows Servers (8Gb RAM, 25Gb HDD) with Remote Desktop Services Roles installed, running as part of an RDS Farm. All Servers are VM Guests (hardware version 7) running on VMware vSphere v4.1.0-260247 Hosts (Dell
PowerEdge R710 - 128Gb RAM). Our vSphere 'farm' has 5 Hosts that connect to our EMC SAN via iSCSI with multipath routes.
Each RDS Server is load balanced via a Connection Broker, and each server has the same set of software / vm hardware installed. In a nutshell, each has Symantec Endpoint Protection v11.0.5002.333, Symantec Altiris v7.0, Microsoft Office 2007 as well as
other various software essential to these servers.
Symptoms:
Randomly throughout the day, one (or more) of the RDS Servers will crash with a BSOD more often than not with "caused by driver ntoskrnl.exe" sometimes with "cng.sys" and once with "ksecpkg.sys". So far in the 5 weeks I have had 90 crashes. Yesterday
all 8 of the RDS Servers crashed at some point throughout the day.
On a typical BSOD, it says:
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
Technical Information:
*** STOP: 0x00000050 (0xfffffa800c153284, 0x0000000000000001, 0xfffff880053dc0c9, 0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff8000169ac40 base at 0xfffff8000161e000 DateStamp 0x4e02aaa3
Using BlueScreenView it says "caused by address: ntoskrnl.exe+7cc40" nearly every time.
I have analysed as best I could using Microsoft WinDbg, and this is the output of a typical mini-dump file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\hqrds01\c$\Windows\Minidump\030112-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01609000 PsLoadedModuleList = 0xfffff800`0184e670
Debug session time: Thu Mar 1 09:14:00.921 2012 (UTC + 0:00)
System Uptime: 0 days 21:31:41.950
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa800be83284, 1, fffff8800576f0c9, 0}
Could not read faulting driver name
Probably caused by : RDPWD.SYS ( RDPWD!memcpy+1d9 )
Followup: MachineOwner
1: kd> !analyze -v
*                        Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800be83284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800576f0c9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018b8100
fffffa800be83284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800bf70a80 -- (.trap 0xfffff8800bf70a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000023d rbx=0000000000000000 rcx=fffffa800be83284
rdx=ffffffffffe7e63b rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800576f0c9 rsp=fffff8800bf70c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0033401e8 r10=fffff8a0033401e8
r11=fffffa800be83268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax ds:0c40:fffffa80`0be83284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016319fc to fffff80001685c40
STACK_TEXT:
fffff880`0bf70918 fffff800`016319fc : 00000000`00000050 fffffa80`0be83284 00000000`00000001 fffff880`0bf70a80 : nt!KeBugCheckEx
fffff880`0bf70920 fffff800`01683d6e : 00000000`00000001 fffffa80`0be83284 00000000`00000000 fffff8a0`0be85820 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0bf70a80 fffff880`0576f0c9 : fffff880`057547cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0bf70c18 fffff880`057547cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`0576c99d : RDPWD!memcpy+0x1d9
fffff880`0bf70c20 fffff880`0576c9fc : fffff8a0`0f938010 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0bf70c60 fffff880`0576b354 : fffff880`0bf70da0 fffff8a0`033401e8 00000000`00000000 fffff880`0576abfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0bf70d10 fffff880`0576af64 : 00000000`00000031 fffffa80`0bd01895 00000006`0000001f fffff880`05739079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0bf70d50 fffff880`029ba1f8 : fffff8a0`03345000 fffffa80`0bae6e80 fffffa80`0a5c0e60 fffff880`05737e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0bf70df0 fffff880`057378d0 : 00000000`00000000 fffff880`0bf70f10 fffff880`0bf70f08 00000000`00000000 : termdd!IcaRawInput+0x50
fffff880`0bf70e20 fffff880`05736d85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0bf70e50 fffff880`057367c2 : fffffa80`088e8a28 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0bf70ef0 fffff880`029ba1f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0bf70f60 fffff880`0572c4c5 : fffffa80`088e8a10 fffffa80`0bd01658 00000000`00000000 fffffa80`088e8a10 : termdd!IcaRawInput+0x50
fffff880`0bf70f90 fffff880`029baf3e : fffffa80`0bd01620 fffffa80`0c100420 fffffa80`0bd4b450 fffffa80`0973b9b0 : tdtcp!TdInputThread+0x465
fffff880`0bf71810 fffff880`029b9ae3 : fffffa80`09d902b0 fffffa80`0973b9b0 fffffa80`093d8520 fffffa80`0bd4b450 : termdd!IcaDriverThread+0x5a
fffff880`0bf71840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
The RDS servers are set to reboot automatically, and after a period of 5 minutes or so, the users can reconnect and log back in. On a typical day each server will have around 10 people RDP'd in to them.
The Users connecting to the RDS Servers included XP laptops/desktops and IGEL UD-120-LX Thin Terminals. The XPs have SP3 installed and are fully patched via Symantec Altiris.
Things I have tried:
- Analyse the dump-files (as per above).
- I have tracked each user logging on to the RDS Farm (via batch scripts) and tried to determine if this is caused by the same individual(s) but it appears random.
- Check to see if the crashing Virtual Machine is running on a specific host, but it has happened on all Hosts.
- Check to see if there was anything specific that happened on the day that the crashes started. There were about 5 new poeple introduced to the RDS Farm at that time, but there were using (a) client machines that had been used previously elsewhere with
no issues, (b) software that had been used previously, (c) in a remote location that had previous users using RDS, (d) have not been logged on to a RDS Server when it has crashed.
- Updated Windows Server 2008 R2 SP1 to the latest patches (as of Feb 2012).
- Turned on Verifier (using recommended settings), and then analysed dump-files with the same reference to rdpwd.sys.
- Fixed the Memory Resource Reservation in vSphere to the full 8Gb for all these RDS Servers (so that the memory is not shared at all).
- Ran MEMTEST on a VM Guest with the full 8Gb RAM, on a couple of the ESX Hosts.
- Changed the VMTools Video Driver to the SVGA II driver from the Standard VGA Driver.
- Ran a full AV Scan (using SEP).
- Isolated the Printer Drivers using the Printer Management MMC.
- Ran sfc /scannow of all RDS Servers and rebooted.
The mini-dump file mentioned above is here:https://skydrive.live.com/redir.aspx?cid=48f471f287af2349&resid=48F471F287AF2349!105&parid=48F471F287AF2349!103
I hope someone can help, as what hair I have left (from pulling it out) is turning grey!
Andy

*                        Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800c153284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880053dc0c9, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018cd100
fffffa800c153284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800aa48a80 -- (.trap 0xfffff8800aa48a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001ff rbx=0000000000000000 rcx=fffffa800c153284
rdx=ffffffffffee6b8b rsi=0000000000000000 rdi=0000000000000000
rip=fffff880053dc0c9 rsp=fffff8800aa48c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0123923a8 r10=fffff8a0123923a8
r11=fffffa800c153268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax ds:8c40:fffffa80`0c153284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016469fc to fffff8000169ac40
STACK_TEXT:
fffff880`0aa48918 fffff800`016469fc : 00000000`00000050 fffffa80`0c153284 00000000`00000001 fffff880`0aa48a80 : nt!KeBugCheckEx
fffff880`0aa48920 fffff800`01698d6e : 00000000`00000001 fffffa80`0c153284 00000000`00000000 fffff8a0`10919830 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0aa48a80 fffff880`053dc0c9 : fffff880`053c17cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0aa48c18 fffff880`053c17cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`053d999d : RDPWD!memcpy+0x1d9
fffff880`0aa48c20 fffff880`053d99fc : fffff8a0`10cf30d0 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0aa48c60 fffff880`053d8354 : fffff880`0aa48da0 fffff8a0`123923a8 00000000`00000000 fffff880`053d7bfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0aa48d10 fffff880`053d7f64 : 00000000`00000031 fffffa80`0c039de5 00000006`0000001f fffff880`053a6079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0aa48d50 fffff880`012c01f8 : fffff8a0`12393000 fffffa80`0bb7aa60 fffffa80`0b81e9c0 fffff880`053a4e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0aa48df0 fffff880`053a48d0 : 00000000`00000000 fffff880`0aa48f10 fffff880`0aa48f08 fffffa80`0c039ba8 : termdd!IcaRawInput+0x50
fffff880`0aa48e20 fffff880`053a3d85 : fffff880`01716890 fffffa80`0c0327e8 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0aa48e50 fffff880`053a37c2 : fffffa80`0c16e598 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0aa48ef0 fffff880`012c01f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0aa48f60 fffff880`052994c5 : fffffa80`0c16e580 fffffa80`0c039ba8 00000000`00000000 fffffa80`0c16e580 : termdd!IcaRawInput+0x50
fffff880`0aa48f90 fffff880`012c0f3e : fffffa80`0c039b70 fffffa80`0acccf20 fffffa80`0a95c450 fffffa80`0abf9620 : tdtcp!TdInputThread+0x465
fffff880`0aa49810 fffff880`012bfae3 : fffffa80`0c0a6560 fffffa80`0abf9620 fffffa80`087eee80 fffffa80`0a95c450 : termdd!IcaDriverThread+0x5a
fffff880`0aa49840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
Bug Check Code 0x50:http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
Please start by that:
Update all possible drivers
Uninstall all unused programs
Disable all security softwares you have
Run chkdsk /r /f and sfc /scannow
Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
If this does not help then upload MEMORY.DMP file (You can zip it and divide it using 7-ZIP) using Microsoft Skydrive and post a link here.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Installing SSMS 2012 after SQL Server 2008 R2 Express was installed (without tools)

Hi everybody,
This is a question in another forum I am frequent. Someone installed SQL Server Express 2008 R2 and he used the wrong exe, so he installed it without tools. Now he wants to install SSMS.
It looks like SSMS 2012 wants to have SQL Server 2012 Express installed first.
Can someone please confirm if it's possible to install just SSMS 2012 after SQL Server 2008 R2 Express was already installed and if possible, guide through the installation steps?
Thanks a lot in advance.
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

Hi Naomi,
Agree with Shanky.
I have tested the scenario you described. Everything works well, I successfully install SQL Server Management studio 2012 after SQL Server 2008 R2 Express (without tools) was already installed.
Please note that we don’t need to install SQL Server 2012 Express first when installing SSMS 2012. For detailed installation steps of SQL Server 2008 R2 Express and SSMS 2012, you can review below blogs.
How to Install SQL Server 2008 R2 (Express Edition)
SQL Server Management Studio – A step-by-step installation guide
In addition, we can use SSMS 2012 to manage SQL Server Express 2005 /2008 /2008 R2, the tool is backward compatible.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Windows Server 2008 R2 - Windows Error STOP 0X000000D1 usbuhci.sys.sys

Hi everybody,
Since we had this error happening a couple of time in the few months. I was wondering how to resolve this issue.
This issue is happening for no apparent reason and on a threads writen on Microsoft it says it occur when you plug a USB device into it.
http://support2.microsoft.com/kb/2615763/en-us
There was no USB plugged into the device and there is none at all. Is there anyone who had this issue?
Thanks everybody !

Hi EdveTech,
Please try to update all your hardware driver and firmware and disable all AV soft then monitor this issue again, please notice whether any error log before the BSOD occur,
more solution you can refer the following similar thread:
BSOD S"line-height:107%;font-family:'Verdana','sans-serif';font-size:10pt;">http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/bsod-stop-0x000000d1-usbechisys/f17397d6-2169-46e9-b784-cb2441877efc
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

What is the best way to deal with memory leak issue in sql server 2008 R2

What is the best way to deal with memory leak issue in sql server 2008 R2.

What is the best way to deal with memory leak issue in sql server 2008 R2.
I have heard of memory leak in OS that too because of some external application or rouge drivers SQL server 2008 R2 if patched to latest SP and CU ( may be if required) does not leaks memory.
Are you in opinion that since SQL is taking lot of memory and then not releasing it is a memory leak.If so this is not a memory leak but default behavior .You need to set proper value for max server memory in sp_configure to limit buffer pool usage.However
sql can take more memory from outside buffer pool if linked server ,CLR,extended stored procs XML are heavily utilized
Any specific issue you are facing
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

ORA AS on Windows Server 2008????

Hi... I am installing ORA AS 10G R2 on windows server 2008 but the installation stops with error message like "OS version should be 5.0.0 " appears
.IZ ORA AS IS NOT SUPPORTED ON WINDOWS SERVER 2008??????????????????

Hi,
Please check the link below for ias 10gR2 certification. I do not think it is certified.
http://www.oracle.com/technology/software/products/ias/files/as_certification_r2_101202.html
Regards,
Mithun

Error Starting Service Manager 2007B patch 10 Windows Server 2008 64 bit

Hi All,
I am trying to do a new installation of SAP Business One 2007B patch level 10 with a operating system of Windows Server 2008 64 bit and SQL Server 2008. Installation of Server, Server Tools and Client sucessfully happened without any errors but when I am trying to open the service Manager its giving me an error as ServiceManager.exe has stopped Working and when I click on view problem details the follwoing is the error details :
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     ServerManager.exe
Application Version:     0.0.0.0
Application Timestamp:     49af579d
Fault Module Name:     B1iEventSender.dll
Fault Module Version:     0.0.0.0
Fault Module Timestamp:     49af5783
Exception Code:     c0000005
Exception Offset:     00033482
OS Version:     6.0.6002.2.2.0.274.10
Locale ID:     1033
Additional Information 1:     fd00
Additional Information 2:     ea6f5fe8924aaa756324d57f87834160
Additional Information 3:     fd00
Additional Information 4:     ea6f5fe8924aaa756324d57f87834160
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
I tried to reinstall the Server Tools but still the problem remains the same.
Can you please advise whaty might be the mistake or problem from my end.
Regards,
Venkat

Hi,
Modify license server from add/remove program but do not check the B1i event sender in the select feature.
Probably, the B1i event ender is not installed correctly.
Rgds,
JimM

Problem of SAPConsle 7.10 (Patch 13) on Windows server 2008 R2 (64bit)

My company is moving from server 2003 to Server 2008 R2 (64bit). We installed SAPConsole 7.10 (Patch level 13) on test server without any problem and configured the profiles in SAPConsole administrator. However when we running the sapcnsl.exe from command prompt, it prompt with error message "*** ERROR => ***AgCom (006FC558): Error: Internal error" and failed to get the SAP login screen.
I checked SAP Note 1043241 saying SAPConsole 710 as patch level 7 could support Windows server 2008 (32/64bit) both.
Can anyone help advise on my issue? or is there anyone has testl the SAPConsole 710 on Server 2008 R2 64bit successfully?
Thank you very much!

Hello Jackcd,
I am not an expert in this area but I did a message search for "AgCom error internal error" and I found a message where the customer solved the problem by using a patch. In the customers own words:
"I installed sapgui 7.10 Patch level 6 on the server where I installed SAPCONSOLE 7.10. Now, the sapconsole working."
The Sapinator

Webi scheduling error in BO 4.0 SP04 after security patch updates in windows server 2008 R2

We are getting below error in BO 4.0 SP04 Web Intelligence report scheduling after security patch updates in windows server 2008 R2
while trying to invoke the method com.businessobjects.sdk.core.server.IServer.getServerContext() of an object returned from com.businessobjects.rebean.wi.impl.services.DocumentInstanceManagementServiceImpl.getServer(com.businessobjects.sdk.core.context.IContext, com.businessobjects.rebean.wi.model.engine.IDocumentInstance)
We have reverted back security patch but still giving above scheduling problem in BO 4.0 SP04 WebI and we can view and refresh report.
Is there any way to fix the scheduling problem in BO 4.0 SP04 WebI?

HI,
Check SAP notes if they will help you.
1934855 - Scheduled Web Intelligence documents fail with com.businessobjects.sdk.core.server Error
1916443 - Scheduling Web Intellignce reports which are having long names to excel and pdf fails.
1792921 - Unable to schedule Webi documents in Excel or PDF format

Unable to install Directory Sync tool in windows server 2008 R2 Eneterprise

Hi,
I am unable to install Directory Sync in windows server 2008 R2 Eneterprise.i have joined my machine domain joined computer running Windows Server 2008 r2 enterprise,when i click dirsync.exe then gives below Error.
The Windows Azure Active Directory Sync tool must be installed on a domain joined computer running Windows Server 2008 Service Pack 2 or later,or Windows Server 2008 r2 Service Pack 1 or later
Please help on this why this happing when i try to installed DirSync software.
Regards
Anil Kumar

Hi,
have you already installed .net framwork 3.5 and 4.5.1 on that machine?
http://technet.microsoft.com/en-us/library/jj151831.aspx
Also make sure that you run the install command from an elevated command prompt.
Hope that helps,
Lutz

Crystal Reports XI stopped working error message on a Windows Server 2008

We recently installed Crystal Report XI in a Windows Server 2008 environment. After completed the installation as the Administrator every time that we try to execute Crystal we receive the following error message:
"Crystal Reports has stopped working"
Problem signature:
Problem Event Name: BEX
Application Name: crw32.exe
Application Version: 11.0.0.1282
Application Timestamp: 422d5c77
Fault Module Name: StackHash_1fc1
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 7ef2fbfc
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 1fc1
Additional Information 2: 1fc163a1c57ae45571bce37d539b233f
Additional Information 3: 2f92
Additional Information 4: 2f92817e9e63d4100e2aa48e72910a78
Any recommendation on what is causing this error?
Thanks,
Luis

Hi, did you get this working? I'm really struggling to get up and running on 2008 R2, the CMS service just refuses to connect to the database. It also looks like the database wasn't created properly during the install. I set it up on an MSDE database, and when I look at it with sql management studio the database is there but there aren't any tables or anything else
Can anyone either confirm or deny that its possible to run Crystal XI on 2008 R2?
The error I'm getting when trying to start the service is:
The root server reported an error Initialization Failure. (Reason: Unable to connect to the database using the provided connection string. Reason: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified).
I've confirmed that the ODBC connections work (both 32 bit and 64 bit) via the built in test, but Crystal for some reason isn't happy

Install BI Tools with paid VS2008 Pro in workstation and paid Sql Server 2008 R2 in server?

My workstation has VS2008 Pro (paid) and Sql Express (free); our Windows Enterprise server has SQL Server 2008 R2 RTM (paid).
In other words, my workstation may not have a paid version of the sql server DB, but our server does. Is there a possibility that I can install the BI development tools in my workstation?
Thanks.
VM

Hi VM,
As you can see on the link below
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#Dev_tools
The Business Intelligence Development Studio is not available on SQL Server 2008 Express Edition. So if you want to the BIDS tool is available on your workstation, then you need to change the edition from Express to other edition.
Besides, you can install SQL Server Data Tools - Business Intelligence for Visual Studio 2012 on your workstation, in this case, the BI development tools is available on your workstation. The SQL Server Data Tools - Business Intelligence for Visual Studio
2012 is available on the link below.
http://www.microsoft.com/en-in/download/details.aspx?id=36843
Regards,
Charlie Liao
TechNet Community Support

Remote Desktop Printer Redirection Stops Working Randomly on Server 2008 R2

We have a MS Windows Server 2008 R2 that is used SOLELY as a Terminal Services remote desktop server onto our network. It is used for employees who are off site and need to use the networked company software. VPN works, but is extremely slow for this software.
Over the past week, the redirected printers function has repeatedly stopped on this server. The employees need this to print to their own local printers. It will eventually restart itself, but after several hours. To get it started faster, I have to restart
the server.
I've done this maybe 6 time since last Monday. This has never been an issue before, and I cannot think of any change that may have occurred that could cause this.
The Event Viewer says this:
The Remote Desktop license server cannot update the license attributes for user "DrewR" in the Active Directory Domain "XXXX.main". Ensure that the computer account for the license server is a member of Terminal Server License Servers group
in Active Directory domain "XXXX.main".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: 0x80070005
(I inserted the Xs)
I've never looked at the Event Viewer on this server, but it is littered with messages such as this, and has been for months and months, so if this IS the issue, then it sure took its sweet time affecting anything.

Hi,
Initially try to update with the latest rollup for fixing remote desktop printing issue. You can check below link and verify result.
https://support.microsoft.com/en-us/kb/2647753
And for the error you can check the related information from beneath article.
TerminalServices-Licensing 4105 – The Terminal Services license server cannot update the license attributes for user “<UserName>” in Active Directory Domain “<DomainName>”
https://support.microsoft.com/en-us/kb/2030310
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to stop SQL Server 2008 R2 generating SQLDump.mdmp files constantly?

Something went wrong with local SQL Server 2008 R2 and it constantly generates SQLDump.mdmp files. It generated 40Gb(!) of SQLDump.mdmp this morning. Server rebooted, but didn't help.
Any ideas what happened with SQL Server and how to stop SQLDump.mdmp files generation?
SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP |
My Blog about Information Management |
My twitter

Memory Dumps are generated automatically by the SQL Server under various circumstances - most of which indicate potential problems in the Instance or the machine. Some that I can recall right now are:
Database Corruption
Non-yielding scheduler
Non-yielding resource monitor
AV (Access Violation)
There can be several other reasons as well. SQL Server generates the dumps, so that these dumps can be analyzed to find out potential problems in the SQL Server.
IMHO, rather than trying to find out ways to stop the dumps from being generated, please try to find out potential problems in the Instance or the machine and fix that. This will stop the dump generation anyway.
In case you need any assistance in analyzing the Dumps, please feel free to engage Microsoft Support.
Suhas De
Please mark solved if your question is completely answered; vote it as helpful to help others find a solution quicker.
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog: http://blogs.msdn.com/b/suhde

Server 2008 r2 Dec 10 patches stops snipping tool

Similar Messages

Maybe you are looking for