Azure Cosmos Db Emulator starting but never start - azure

I use Azure Cosmos Db Emulator for about 1 year now and it’s the 3de time it sudently stop working.
The only way i found for resolve the problem was to do a complete re-install of windows 10 …
My configuration :
Windows 10 Pro
Administrator privilege
Domain link to AAD
Antivirus software : ESET Endpoint antivirus 9.1.2051.0
Intel(R) Core(TM) i5-4670 CPU # 3.40GHz 3.40 GHz
32 Go of RAM
All my software installed on C :
I try this in command prompt (as Administrator) :
Clear performance counter before start
Microsoft.Azure.Cosmos.Emulator.exe /shutdown
lodctr /R (2 time to be sure)
Microsoft.Azure.Cosmos.Emulator.exe
Result :
The notification for « Starting » show up
A dump file is create in AppData/Local/CrashDumps
The notification that the emulator is « start » never come
The web page never open
Uninstall – re-install
Microsoft.Azure.Cosmos.Emulator.exe /shutdown
Delete folder AppData\Local\CosmosDBEmulator
Uninstall Cosmos Db Emulator
Delete folder C:\Program Files\Azure Cosmos DB Emulator
Restart the computer
Install last app version : azure-cosmosdb-emulator-2.14.9-3c8bff92.msi
Check for start the emulator after install end
Result :
Same result than 1)
Start trace
- Microsoft.Azure.Cosmos.Emulator.exe /shutdown
- Microsoft.Azure.Cosmos.Emulator.exe /startwprtraces
- Microsoft.Azure.Cosmos.Emulator.exe
- [wait for 1 minute]
- Microsoft.Azure.Cosmos.Emulator.exe /stopwprtraces
- Microsoft.Azure.Cosmos.Emulator.exe /shutdown
Result :
The notification for « Starting » show up
A dump file is create in AppData/Local/CrashDumps
Until the 1 minute of waiting , a dump file was created for about every 20/30s
When i execute Microsoft.Azure.Cosmos.Emulator.exe /stopwprtraces, a docdbemulator_001.etl was created in C:\Program Files\Azure Cosmos DB Emulator
The notification that the emulator is « start » never come
The web page never open
I try to read the dump file with WinDbg.exe and i found this error message :
CLR_EXCEPTION_System.Collections.Generic.KeyNotFoundException_80131577_Microsoft.Azure.Documents.Common.dll!Microsoft.Azure.Documents.Common.Service.WindowsFabricConfigurationProvider.GetValue
And the stack trace was :
00000085`583feb40 00007ffe`49323302 Microsoft_Azure_Documents_Common!Microsoft.Azure.Documents.Common.Service.WindowsFabricConfigurationProvider.GetValue+0x52
00000085`583feb80 00007ffe`493230cb Microsoft_Azure_Documents_Common!Microsoft.Azure.Documents.Common.CrashDump.Register+0xdb
00000085`583febf0 00007ffe`48f673ee Microsoft_Azure_Cosmos_Compute_Host_ServiceFabric_EntryPoint!Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.CosmosDBGatewayInit+0x56e
00000085`583fecf0 00007ffe`48f51465 Microsoft_Azure_Cosmos_Compute_Host_ServiceFabric_EntryPoint!Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.Main+0x295
In windows logs I found the same error description (in french):
Application : Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.exe Version du Framework : v4.0.30319 Description : le processus a été arrêté en raison d'une exception non gérée. Informations sur l'exception : System.Collections.Generic.KeyNotFoundException à Microsoft.Azure.Documents.Common.Service.WindowsFabricConfigurationProvider.GetValue(System.String) à Microsoft.Azure.Documents.Common.CrashDump.Register(System.Collections.Generic.IEnumerable`1<System.String>, Microsoft.Azure.Cosmos.Core.IConfigurationProvider) à Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.CosmosDBGatewayInit(System.Fabric.CodePackageActivationContext, System.String) à Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.Main(System.String[])
And
Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.exe
2.14.0.0
bc4d0da5
KERNELBASE.dll
10.0.19041.1889
e9ede6d6
e0434352
0000000000034fd9
4360
01d8b7ac99b3d711
C:\Program Files\Azure Cosmos DB Emulator\Packages\CosmosGatewayService\CosmosGatewayService.Code\EP\Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.exe
C:\WINDOWS\System32\KERNELBASE.dll
01134c47-5efa-4d7a-a243-15af35536df0

Finaly I found that Cosmos Db create 3 Security Groups that are not delete on uninstall.
I delete all 3 and remove all registry reference on each. (searching for Cosmos Db and DocDb)
Now when i reinstall all work properly !
Thanks you David for your help.

I tried all of the above, the security groups are under Computer management
DocDbGatewayService
DocDBMasterService
DocDbServerService
This still didn't clear it for me, I did find the following in the Event Log
Application:
Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.exe
Framework Version: v4.0.30319 Description: The process was terminated
due to an unhandled exception. Exception Info:
System.Collections.Generic.KeyNotFoundException at
Microsoft.Azure.Documents.Common.Service.WindowsFabricConfigurationProvider.GetValue(System.String)
at
Microsoft.Azure.Documents.Common.CrashDump.Register(System.Collections.Generic.IEnumerable`1<System.String>,
Microsoft.Azure.Cosmos.Core.IConfigurationProvider) at
Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.CosmosDBGatewayInit(System.Fabric.CodePackageActivationContext,
System.String) at
Microsoft.Azure.Cosmos.Compute.Host.ServiceFabric.EntryPoint.EntryPoint.Main(System.String[])
And I managed to clear the issue with the following command
netsh http add iplisten ipaddress:0.0.0.0
This was taken from this thread - https://github.com/MicrosoftDocs/azure-docs/issues/6788

Related

"SPManager.Initialize failed" when running PSConfig on sharepoint 2013

I am trying to update a sp2013 farm from SP1+July 2016 CU to the August 2020 CU. I've already installed the patch, and am trying to run PSCONFIG now.
The first APP server (which runs Central admin) PSCONFIG command completed successfully, but I have been unable to get any of the remaining servers to complete - I've tried both WFE and another App server, in all cases, PSCONFIG exits with the following error:
> PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd install
features -cmd secureresources
SharePoint Products Configuration Wizard version 15.0.4939.1000. Copyright (C) Microsoft Corporation 2012. All rights reserved.
Performing configuration task 1 of 7
Initializing SharePoint Products upgrade...
Waiting to get a lock to upgrade the farm.
Successfully initialized the SharePoint Products configuration.
Performing configuration task 2 of 7
Initiating the upgrade sequence...
Failed to initiate the upgrade sequence.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
Total number of configuration settings run: 2
Total number of successful configuration settings: 1
Total number of unsuccessful configuration settings: 5
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products.
For further details, see the diagnostic log located at d:\spdata\Logs\ULS\PSCDiagnostics_12_4_2020_16_38_33_727_1311047457.log and the application event log
When I check the PSCDiag file, the error is just "Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown"
12/04/2020 15:56:42 12 ERR Task upgradebootstrap has failed with an unknown exception
12/04/2020 15:56:42 12 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
I've rebooted (multiple times)
Tried stopping/restarting IIS
Cleared the sharepoint config cache
Run Get-spProduct -local - it give an error the first time I run it, but then succeeds the second time (which is the same behavior I had on the first server which completed successfully)
> Get-SPProduct -Local
Get-SPProduct : Failed to call GetTypes on assembly
Microsoft.AnalysisServices.SPAddin, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91. Could not load file or assembly
'Microsoft.AnalysisServices.SPClient, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot
find the file specified.
At line:1 char:1
+ Get-SPProduct -Local
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...letGetSPProduct:
SpCmdletGetSPProduct) [Get-SPProduct], SPUpgradeException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SpCmdletGetSPPro
duct
> Get-SPProduct -Local
ProductName Required Missing Servers
----------- -------- ------- -------
Microsoft SharePoint Server... True {}
Microsoftr Project Server 2013 True {}
I do see a few UNEXPECTED level errors in the ULS logs relating to Microsoft.AnalysisServices.SPAddin
ERROR Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly 'Microsoft.AnalysisServices.SPClient, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. 00000000-0000-0000-0000-000000000000
and also one that appears related to inability to update the central admin - but I believe that would have been done when I ran PSConfig on the Central admin server, which completed successfully
12/04/2020 16:58:20.93 OWSTIMER (0x3254) 0x0B3C SharePoint Foundation Upgrade SPUpgradeSession ajxme ERROR CanUpgrade [SPContentDatabase Name=SYSdev_content_CentralAdmin] failed. 00000000-0000-0000-0000-000000000000
any suggestions are appreciated.
Thanks
I found the issue. The central admin server on which PSCONFIG completed successfully had SQL Server 2014 PowerPivot installed, but the other servers in the farm all had SQL Server 2012 PowerPivot installed. (this is dev environment, and PowerPivot had been installed for testing long ago).
I uninstalled SQL Server 2012 PowerPivot and installed SQL Server 2014 PowerPivot on all other servers. PSCONFIG then completed successfully on all the servers.

Sql Server 2019 (Fedora 32) - Msg 22022, Level 16, State 1, Line 0 SQLServerAgent is not currently running so it cannot be notified of this action

I am getting this error. Though Agent seems to be running I have checked running state by calling
EXEC xp_servicecontrol 'querystate', 'SQLSERVERAGENT'
And it shows "Stopped." Then I call
EXEC xp_servicecontrol N'START',N'SQLServerAGENT';
And it shows "Running." After that I try executing the job by calling
EXEC dbo.sp_start_job N'SendCollectionSummaryReport' ;
And I get the Error: SQLServerAgent is not currently running so it cannot be notified of this action.
Then I called again EXEC xp_servicecontrol 'querystate', 'SQLSERVERAGENT'
And it shows "Stopped."
I realized that something is causing failure to start SQLServerAgent. Environment details below:
Microsoft SQL Server 2019 (RTM-CU4) (KB4548597) - 15.0.4033.1 (X64)- Developer Edition (64-bit) ort n Linux (Fedora 32 (Workstation Edition))
Access same server using SSME on Windows Client Machine and All Options coming Disabled

Windows Subsystem for Linux Error: 0x800703fa Illegal operation attempted on a registry key that has been marked for deletion

After a Windows 10 update, I'm getting this error while starting WSL Ubuntu 18.
I have tried to restart a couple of times, but the error is still there
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800703fa
Error: 0x800703fa Illegal operation attempted on a registry key that has been marked for deletion.
Press any key to continue...
The solution has been provided by Github's user #friedwm on this issue comment:
https://github.com/Microsoft/WSL/issues/2576#issuecomment-380823857
The solution is to restart LxssManager from services.msc, or start it if it is not running.
Settings > Apps&Features > select Ubuntu > Advanced options > Repair

Unable to create/start local cluster on Windows 7 machine

We have windows 7 with VS 2015 Update 3 and Service Fabric Runtime 6.1.456.9494 installed along with Service Fabric SDK 3.0.456. There are no errors while installing either the runtime or sdk, but still while setting up local cluster it fails with following errors, and this is happening in all the machines we are using.
WARNING: Service Fabric Cluster is taking longer than expected to
connect.
Waiting for Naming Service to be ready. This may take a few minutes...
Connect-ServiceFabricCluster : No cluster endpoint is reachable,
please check if there is connectivity/firewall/DNS issue. At
C:\Program Files\Microsoft SDKs\Service
Fabric\Tools\Scripts\ClusterSetupUtilities.psm1:620 char:12 +
[void](Connect-ServiceFabricCluster #connparams) +
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo :
InvalidOperation: (:) [Connect-ServiceFabricClus 2> ter],
FabricException + FullyQualifiedErrorId :
TestClusterConnectionErrorId,Microsoft.ServiceFa 2>
bric.Powershell.ConnectCluster
Faulting application name: Fabric.exe, version: 6.1.456.9494, time stamp: 0x5a66710e
Faulting module name: FabricCommon.dll_unloaded, version: 0.0.0.0, time stamp: 0x5a666cec
Exception code: 0xc0000005
Fault offset: 0x000007febd3e6d31
Faulting process id: 0x2854
Faulting application start time: 0x01d3a64824f31fdc
Faulting application path: C:\SfDevCluster\Data_Node_0\Fabric\Fabric.Code\Fabric.exe
Faulting module path: FabricCommon.dll
Report Id: 62dd8dbf-123b-11e8-bbb0-00505699504f
I don't see anything useful in Trace logs either.
I tried resintalling microsoft visual c++ 2012 redistributable package (x64) , tried running cleanupfabric , cleanupcluster but still the issue persists.
Also unisntalled and reinstalled service fabric runtime and sdk multiple times, still issue persists.

HDInsight Emulator not running on Windows / connection exception

I'm trying to setup a HDInsight emulator on a Windows 8.1 PC following these instructions: https://azure.microsoft.com/en-us/documentation/articles/hdinsight-hadoop-emulator-get-started/
When trying to run a MapReduce job, I get a connection error.
How can I solve or further investigate this issue?
Details below.
Prerequisites:
Installed Azure Powershell and Azure SDK for VS 2015
Installed HDInsight Emulator for Azure incl. Hortonworks Data Platform
Started local hdp services (13 services running)
Connected Visual Studio to Emulator (had to follow troubleshooting point 2: replacing IP addresses in core-site.xml with '*' due to dynamic IP)
Created directories and copied text files as suggested
Problem:
When trying to run the first example, I get the following error:
16/01/11 10:36:39 INFO mapreduce.Job: Job job_1452503376359_0003 failed with state FAILED due to: Application application_1452503376359_0003 failed 2 times due to AM Container for appattempt_1452503376359_0003_000002 exited with exitCode: -1000 due to: Call From EH3HOST/192.168.56.1 to EH3HOST:8020 failed on connection exception: java.net.ConnectException: Connection refused: no further information; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
.Failing this attempt.. Failing the application.
16/01/11 10:36:39 INFO mapreduce.Job: Counters: 0
The following worked for me:
Search for XML files containing <your own host name>:8020 inside the c:\hdp\hdp-<Version Number>\etc\hadoop\ folder. (e.g. EH3HOST:8020)
You should find at least
mapred-site.xml
core-site.xml
yarn-site.xml
Replace all occurrences within these files with 127.0.0.1:8020.

Resources