Since we updated MS Office 2016 to version 1703 (Build 7967.2139), all the users having issues with registering Redemption.dll using regsvr32. It just doesn't give any error while running the regsvr32 command. We ran the command in admin mode. I looked at the events in Application log, and found below information:
Faulting application name: regsvr32.exe, version: 10.0.10586.0, time stamp: 0x5632d7fb
Faulting module name: olmapi32.dll, version: 16.0.7967.6531, time stamp: 0x58f7803c
Exception code: 0xc0000409
Fault offset: 0x0012c733
Faulting process id: 0x4294
Faulting application start time: 0x01d2c4413ac3ef95
Faulting application path: C:\WINDOWS\SysWOW64\regsvr32.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\olmapi32.dll
Report Id: dade8820-84eb-46a0-9e19-2d5f9c4d9f7d
Faulting package full name:
Faulting package-relative application ID:
Is there anyone who is having this problem and found a solution?
Thanks.
You need to make sure you are using Redemption 5.12 or at least 5.11. Older versions of Redemption (released before Outlook 2016 was available) do not support Outlook 2016.
Related
Trying to launch Iaas IIS hosted asp.net application. getting below error.
any idea please?
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: clr.dll, version: 4.6.1055.0, time stamp: 0x563c12de
Exception code: 0xc00000fd
Fault offset: 0x0000000000009780
Faulting process id: 0x3b8
Faulting application start time: 0x01d28eb490fe4237
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: d7320ef8-faa7-11e6-80dc-000d3af785ff
Faulting package full name:
Faulting package-relative application ID:
This is because of code session is looping infinity. i spent hell amount of time.
I'm trying to connection to the Xamarin Build Host (MAC OS) from my Visual Studio (Windows PC). Every time I'm paring VS and Build Host I'm getting proposal to sync SDKs:
https://www.dropbox.com/s/wc4q7apmjxzcxru/shot_140320_170111.png
and every time I'm pressing the OK button I get the following error:
https://www.dropbox.com/s/kka5c9kqh9f65nn/shot_140320_165146.png
Visual Studio is crashed with the following error fetched from the EventLog:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
Stack:
at System.Windows.Interop.WindowInteropHelper..ctor(System.Windows.Window)
at System.Windows.MessageBox.Show(System.Windows.Window, System.String, System.String, System.Windows.MessageBoxButton, System.Windows.MessageBoxImage)
at Mono.IOS.VisualStudio.Utilities.SdkStatus.NotifySdkIconClick(System.Object, System.EventArgs)
at System.Windows.Forms.NotifyIcon.OnBalloonTipClicked()
at System.Windows.Forms.NotifyIcon.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NotifyIcon+NotifyIconNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
Faulting application name: devenv.exe, version: 12.0.30110.0, time stamp: 0x52cfb65a
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16496, time stamp: 0x52b3e015
Exception code: 0xe0434352
Fault offset: 0x00012eec
Faulting process id: 0x16ec
Faulting application start time: 0x01cf447df8795b46
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Report Id: 6a73a398-b071-11e3-bec4-7ce9d3fe3dda
Faulting package full name:
Faulting package-relative application ID:
Support didn't answer my question yet.
I manged to fix the issue by switching to the Alpha channel of Xamarin software.
After updating both Windows and Mac I got a working environment, no "SDK sync is required" notifications and an ability to deploy a build to my iPhone connected to the Mac from Visual Studio
Every 24 hours or so, we receive a 503 from our IIS 7.5 web server that hosts our MVC application.
I read some related articles and checked if the Application Pool/Identity had the necessary permissions and was a part of the IIS_USR (or whatever it is called) group.
The event log reports that the ASP.NET worker process crashed. This is the information from the event log:
Log Name: Application
Source: Application Error
Date: 5/14/2013 11:15:58 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER_MACHINE_NAME
Description:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x1ccbc2de
Faulting process id: 0x2640
Faulting application start time: 0x01ce51338e238a4b
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: unknown
Report Id: e8120b0c-bd26-11e2-9313-001f290b5f7a
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-05-15T06:15:58.000000000Z" />
<EventRecordID>4265</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER_MACHINE_NAME</Computer>
<Security />
</System>
<EventData>
<Data>w3wp.exe</Data>
<Data>7.5.7601.17514</Data>
<Data>4ce7a5f8</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>00000000</Data>
<Data>1ccbc2de</Data>
<Data>2640</Data>
<Data>01ce51338e238a4b</Data>
<Data>C:\Windows\SysWOW64\inetsrv\w3wp.exe</Data>
<Data>unknown</Data>
<Data>e8120b0c-bd26-11e2-9313-001f290b5f7a</Data>
</EventData>
</Event>
Deployment Environment:
Web Server: IIS 7.5
.NET Framework: v4
MVC version: 4
Windows Server: Windows Server 2008 R2 Standard
Help appreicated.
After upgrading an ASP.NET solution to 4.0 we have noticed that every time the application pool recycles automatically (every 1740 minutes), exactly 32 seconds later we get an error in the event logs with event ID 5009.
I installed the debugger on the server and ran the analysis tool on the crash dump and below you can see what I got. Can you help me understand what could be the issue? This is happening on 4 different machines (which all happen to be virtual machines). I noticed that there is a "loop" going on in the full call stack (which I spare you here for space reasons), with the following group of calls being repeated over and over:
clr!Thread::DoAppropriateWaitWorkerAlertableHelper+4d 0000000000000000 000000001bb30ba0 0000000020a0cf60 0000000000000000
clr!Thread::DoAppropriateWaitWorker+146 000000001bb30ba0 0000000000000001 0000000001c05970 0000000000000000
clr!Thread::DoAppropriateWait+73 0000000020a0c0a0 0000000000000001 000007fee4736ca9 000007fee4736c2c
clr!CLREvent::WaitEx+c1 0000000000000000 0000000000000000 0000000000000000 000007fee7e7f960
clr!RegMeta::SaveToStream+134 0000000020a0b740 000000001bb30ba0 00000000dc951994 0000000076df0e4a
clr!WaitForEndOfShutdown+9 0000000000010000 000007fee7804b65 0000000000000000 0000000000000000
clr!Thread::RareDisablePreemptiveGC+490 000007fee4a8cca0 0000000020a0b9f0 00000000dc951994 0000000000001200
clr!EEHashTableBase,0>::FindItem+5c 000007fee4a8cca0 0000000020a0b9f0 0000000000000001 000007feefbc229b
clr!IsCerRootMethod+b1 0000000000000001 0000000000000000 0000000000000000 00000000ffffff98
clr!TAStackCrawlCallBack+1e9 0000000020a0bd90 0000000020a0b9f0 0000000020a0bd90 0000000020a0bd90
clr!Thread::MakeStackwalkerCallback+2f 0000000020a0c2a0 0000000000000002 0000000000000002 0000000020a0c060
clr!Thread::StackWalkFramesEx+8d 000000001bb30ba0 000000001bb30ba0 000000001bb30ba0 0000000000020019
clr!Thread::ReadyForAsyncException+197 0000000076f471ba 000000001bb30ba0 0000000000000000 0000000000000000
clr!Thread::HandleThreadAbort+6c 0000000076def5e4 000007fee4da009a 000000001bb30ba0 0000000000000000
clr!Thread::HandleThreadInterrupt+7e 00000000000007c0 00000000000007c0 000007fee79ae71c 000007fee4d9f9dc
Analysis Summary
Type Description Recommendation
Error In w3wp_QAWEB4_PID_4668_Date__05_02_2012__Time_04_16_30PM_242_Second_Chance_Exception_C0000005.dmp the assembly instruction at clr!CLREvent::WaitEx+f in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x20990ff0 on thread 20
Please follow up with the vendor Microsoft Corporation for C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Information DebugDiag determined that this dump file (w3wp_QAWEB4_PID_4668_Date__05_02_2012__Time_04_16_30PM_242_Second_Chance_Exception_C0000005.dmp) is a crash dump and did not perform any hang analysis. If you wish to enable combined crash and hang analysis for crash dumps, edit the Globals.asp script (located in the DebugDiag\Scripts\inc folder) and set the g_DoCombinedAnalysis constant to True.
Analysis Details
Report for w3wp_QAWEB4_PID_4668_Date__05_02_2012__Time_04_16_30PM_242_Second_Chance_Exception_C0000005.dmp
Type of Analysis Performed Crash Analysis
Machine Name XXXX01-QA-WEB01
Operating System Windows Server 2008 Service Pack 2
Number Of Processors
Process ID 4668
Process Image c:\Windows\System32\inetsrv\w3wp.exe
System Up-Time 4 day(s) 14:59:36
Process Up-Time 00:06:32
Thread 20 - System ID 4364
Entry point clr!Thread::intermediateThreadProc
Create time 5/2/2012 4:10:16 PM
Time spent in user mode 0 Days 0:0:1.421
Time spent in kernel mode 0 Days 0:0:0.453
.NET Call Stack
Function
System.Threading.Thread.SleepInternal(Int32)
System.Threading.Thread.Sleep(System.TimeSpan)
Sitecore.Services.Heartbeat.WorkLoop()* ERROR: Module load completed but symbols could not be loaded for Sitecore.Kernel.dll
System.Threading.ExecutionContext.runTryCode(System.Object)
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Threading.ThreadHelper.ThreadStart()
Full Call Stack
removed for space reasons
Exception Information
CLR!CLREVENT::WAITEX+FIn w3wp_QAWEB4_PID_4668_Date__05_02_2012__Time_04_16_30PM_242_Second_Chance_Exception_C0000005.dmp the assembly instruction at clr!CLREvent::WaitEx+f in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x20990ff0 on thread 20
Module Information
Image Name: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Symbol Type: PDB
Base address: 0x0000000300905a4d Time Stamp: Sat Jul 09 05:44:20 2011
Checksum: 0x0000000000000000 Comments: Flavor=Retail
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: Microsoft .NET Runtime Common Language Runtime - WorkStation
ISAPIFilter: False File Version: 4.0.30319.239 (RTMGDR.030319-2300)
Managed DLL: False Internal Name: clr.dll
VB DLL: False Legal Copyright: © Microsoft Corporation. All rights reserved.
Loaded Image Name: clr.dll Legal Trademarks:
Mapped Image Name: Original filename: clr.dll
Module name: clr Private Build: DDBLD205
Single Threaded: False Product Name: Microsoft® .NET Framework
Module Size: 9.39 MBytes Product Version: 4.0.30319.239
Symbol File Name: c:\symcache\clr.pdb\887DDF30473443C9905C3217115D7DE72\clr.pdb Special Build: &
Script Summary
Script Name Status Error Code Error Source Error Description Source Line
CrashHangAnalysis.asp Completed
What is error code listed in event id 5009 description? http://www.eventid.net/display-eventid-5009-source-Microsoft-Windows-WAS-eventno-8833-phase-1.htm indicates that this might be caused by an empty folder from the previous .Net version.
I'm attempting to create a Dev instance of TFS 2005 (non SP1) with a view to test SP1. We're using dual server mode.
So far, I've installed TFS on my App machine, restored the db from prod on my database machine, and updated references in my db. Also ran the usual tfsadminutil commands.
When I open VS2005 and attempt to connect to TFS, I get this error:
Team Foundation Server scdctstmp01 does not exist or is not accessible at this time. Technical information (for administrator): HTTP code 503: TF30059: Fatal error while initializing web service
The event log on my app machine gives 2 errors:
Event Type: Error
Event Source: TFS Version Control
Event Category: None
Event ID: 3023
Date: 1/12/2011
Time: 2:23:53 PM
User: N/A
Computer: SCDCTSTMP01
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 1/12/2011 6:23:53 AM
Machine: SCDCTSTMP01
Application Domain: /LM/W3SVC/3/Root/VersionControl-6-129671942250700000
Assembly: Microsoft.TeamFoundation.VersionControl.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4440
Thread Id: 4660
Account name: JUSTICE\svctfsservicetest
Detailed Message: TF14073: The stored download key is not valid. The key will be regenerated.
Web Request Details
Url: http://scdctstmp01:8080/VersionControl/v1.0/repository.asmx [method: POST]
User Agent: Team Foundation (devenv.exe, 8.0.50727.147)
Headers: Content-Length=319&Content-Type=application%2fsoap%2bxml%3b+charset%3dutf-8&Accept-Encoding=gzip%2cgzip%2cgzip&Accept-Language=en-AU&Authorization=NTLM+TlRMTVNTUAADAAAAGAAYAHgAAAAYABgAkAAAAA4ADgBIAAAAEAAQAFYAAAASABIAZgAAABAAEACoAAAANYKI4gUBKAoAAAAPSgBVAFMAVABJAEMARQBSAGEAdABpAGwAYQBsAEEAVwBLAFMANQAzADcAMgA2ADEAPY1tpAEvSp0AAAAAAAAAAAAAAAAAAAAAyQBeCmtO9f7LX%2fiQDfGQkQsvS8PePBVfQSawM960yZWsaavouGJD6A%3d%3d&Expect=100-continue&Host=scdctstmp01%3a8080&User-Agent=Team+Foundation+(devenv.exe%2c+8.0.50727.147)&X-TFS-Version=1.0.0.0&X-VersionControl-Instance=182973de-f5c6-4c0f-9895-91f36f476551
Path: /VersionControl/v1.0/repository.asmx
Local Request: False
Host Address: 10.96.144.249
User: JUSTICE\RatilalA [authentication type: NTLM]
Exception Message: Keyset does not exist
(type CryptographicException)
Exception Stack Trace: at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
at System.Security.Cryptography.SafeProvHandle._FreeCSP(IntPtr pProvCtx)
at System.Security.Cryptography.SafeProvHandle.ReleaseHandle()
at System.Runtime.InteropServices.SafeHandle.InternalDispose()
at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
at System.Runtime.InteropServices.SafeHandle.Dispose()
at System.Security.Cryptography.RSACryptoServiceProvider.Dispose(Boolean disposing)
at System.Security.Cryptography.AsymmetricAlgorithm.System.IDisposable.Dispose()
at Microsoft.TeamFoundation.VersionControl.Server.Proxy.RequestSignatures.GetKeyInformation(Byte[] privateKey, Int32& keyLength, Byte[]& publicKey)
at Microsoft.TeamFoundation.VersionControl.Server.RepositoryProperties.set_PrivateKey(Byte[] value)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and
Event Type: Error
Event Source: TFS Version Control
Event Category: None
Event ID: 3000
Date: 1/12/2011
Time: 2:23:59 PM
User: N/A
Computer: SCDCTSTMP01
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 1/12/2011 6:23:59 AM
Machine: SCDCTSTMP01
Application Domain: /LM/W3SVC/3/Root/VersionControl-6-129671942250700000
Assembly: Microsoft.TeamFoundation.VersionControl.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4440
Thread Id: 4660
Account name: JUSTICE\svctfsservicetest
Detailed Message: TF14000: A critical error occured while generating new download key. Shutting down the current AppDomain
Web Request Details
Url: http://scdctstmp01:8080/VersionControl/v1.0/repository.asmx [method: POST]
User Agent: Team Foundation (devenv.exe, 8.0.50727.147)
Headers: Content-Length=319&Content-Type=application%2fsoap%2bxml%3b+charset%3dutf-8&Accept-Encoding=gzip%2cgzip%2cgzip&Accept-Language=en-AU&Authorization=NTLM+TlRMTVNTUAADAAAAGAAYAHgAAAAYABgAkAAAAA4ADgBIAAAAEAAQAFYAAAASABIAZgAAABAAEACoAAAANYKI4gUBKAoAAAAPSgBVAFMAVABJAEMARQBSAGEAdABpAGwAYQBsAEEAVwBLAFMANQAzADcAMgA2ADEAPY1tpAEvSp0AAAAAAAAAAAAAAAAAAAAAyQBeCmtO9f7LX%2fiQDfGQkQsvS8PePBVfQSawM960yZWsaavouGJD6A%3d%3d&Expect=100-continue&Host=scdctstmp01%3a8080&User-Agent=Team+Foundation+(devenv.exe%2c+8.0.50727.147)&X-TFS-Version=1.0.0.0&X-VersionControl-Instance=182973de-f5c6-4c0f-9895-91f36f476551
Path: /VersionControl/v1.0/repository.asmx
Local Request: False
Host Address: 10.96.144.249
User: JUSTICE\RatilalA [authentication type: NTLM]
Exception Message: Keyset does not exist
(type CryptographicException)
Exception Stack Trace: at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
at System.Security.Cryptography.SafeProvHandle._FreeCSP(IntPtr pProvCtx)
at System.Security.Cryptography.SafeProvHandle.ReleaseHandle()
at System.Runtime.InteropServices.SafeHandle.InternalDispose()
at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
at System.Runtime.InteropServices.SafeHandle.Dispose()
at System.Security.Cryptography.RSACryptoServiceProvider.Dispose(Boolean disposing)
at System.Security.Cryptography.AsymmetricAlgorithm.System.IDisposable.Dispose()
at Microsoft.TeamFoundation.VersionControl.Server.Proxy.RequestSignatures.GenerateNewPrivateKey(Int32 keyLength)
at Microsoft.TeamFoundation.VersionControl.Server.AdministrationManager.GenerateRepositoryKey(Int32 keyLength)
at Microsoft.TeamFoundation.VersionControl.Server.Global.Initialize()
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Anyone knows what the issue is? Thanks.
Found out that the database I was copying was SP1, while my test server was not.
To find TFS version: Navigate to
C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Services\bin
Right click on Microsoft.TeamFoundation.Server.dll, Properties, Version
File version 8.0.50727.762 = SP1.
File version 8.0.50727.147 = RTM.