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.
Related
I have MS Server 2019 Standard edition, IIS 10.0.17763.1, Visual C++ 2019, PHP 8.0.26 NTS x64, and php_pdo_sqlsrv_80_nts.dll extension enabled. I'm able to connect to MS Access 2007 database and run a query. I'm able to query the database and return 50 records. The script randomly stops working and I get a 500 error. The Windows Application log returns
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x1a54
Faulting application start time: 0x01d90be40a629837
Faulting application path: C:\PHP8\php-cgi.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
I have tried PHP 8.0.26, 8.1.13, and 8.2.0, both NTS and TS, both x86 and 64.
I searched for Faulting module name: ucrtbase.dll, version: 10.0.17763.1490 error and tried command with no luck
DISM.exe /Online /Cleanup-image /Restorehealth
Does anyone else experience this? Does anyone have php8* with PDO working on IIS and if so what did you install and what is your configuration?
I am using MIP sdk for JAVA from Microsoft (https://learn.microsoft.com/en-us/information-protection/develop/setup-configure-mip) and trying to execute its sample to read and write MIP labels.
But when I run MIPSample for JAVA I am getting following error message in MIP log.
"2021-02-16 12:23:38.609 common/api_utils.h:232 java (14700) "Unrecognized exception: profile_add_engine_async" mipns::TryExecuteFailureCallback"
And my call to
Future<IFileEngine> fileEngineFuture = fileProfile.addEngineAsync(engineSettings);
IFileEngine fileEngine = fileEngineFuture.get();
is not completing successfully.
In API AuthDelegateUserCredentials::acquireToken(), I am successfully able to get 'accessToken' but when I return that same access token, somewhere it crashes, before it could return and attach fileEngine instance.
I windows event viewer I m getting following error
Faulting application name: java.exe, version: 8.0.2420.8, time stamp: 0x5e246f62
Faulting module name: ntdll.dll, version: 10.0.17763.475, time stamp: 0x3230aa04
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0x1dc0
Faulting application start time: 0x01d7043c7ac79efc
Faulting application path: C:\code\depot\tools\windows\OpenJDK\1.8.0_242\x64\bin\java.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ddfa73cc-d1e2-48ef-a76e-866bf67aaaa6
Faulting package full name:
Faulting package-relative application ID:
Please let me know what I might be doing wrong here.
Can you share the version of the SDK you're using? I haven't been able to reproduce this in 1.7. I'm working on a sample for 1.8 and will see if I can repro there.
In my solution, I have three different projects including ASP.Net MVC, Class Library, and Web API.
The application works fine on local, but on the production server (Windows Server 2016) after setting "Enable 32-bit Applications = true" in Application Pool (it is a neccessary requirement), the project stopped working.
The following information in EventViewer is available:
Description: Faulting application name: w3wp.exe, version:
10.0.14393.0, time stamp: 0x57899135 Faulting module name: clrjit.dll, version: 4.8.4180.0, time stamp: 0x5e7d1e02 Exception code: 0xc00000fd
Fault offset: 0x00009865 Faulting process id: 0xc64 Faulting
application start time: 0x01d665a86c307401 Faulting application path:
C:\Windows\SysWOW64\inetsrv\w3wp.exe Faulting module path:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll Report Id:
751158e0-ba08-4f54-ba3c-699e0983a43d
What could be the main reason and how can I fix it?
I'm new to Azure and Service Fabric.
Today I installed the VS Service Fabric tools and the SDK (latest 3.3.617)
My home desktop has Win10 pro x64 with 8GB RAM.
I tried to run a "hello world" app from the "new project" using VS. Compilation works and then it starts to spin up the local cluster.
I get this error:
1>------ Build started: Project: Stateless1, Configuration: Debug x64 ------
1> Stateless1 -> C:\Users\USER\source\repos\Application2\Stateless1\bin\x64\Debug\Stateless1.exe
2>------ Build started: Project: Application2, Configuration: Debug x64 ------
3>------ Deploy started: Project: Application2, Configuration: Debug x64 ------
3>Started executing script 'GetApplicationExistence'.
3>Finished executing script 'GetApplicationExistence'.
3>Time elapsed: 00:00:00.4751003
3>Started executing script 'Set-LocalClusterReady'.
3>powershell -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -Command "Import-Module 'C:\Program Files\Microsoft SDKs\Service Fabric\Tools\Scripts\DefaultLocalClusterSetup.psm1'; Set-LocalClusterReady -createOneNodeCluster $true"
3>--------------------------------------------
3>Local Service Fabric Cluster is not setup...
3>Please wait while we setup the Local Service Fabric Cluster. This may take few minutes...
3>Performing Stop-Service on service: FabricHostSvc . This may take a few minutes...
3>
3>Using Cluster Data Root: C:\SfDevCluster\Data
3>Using Cluster Log Root: C:\SfDevCluster\Log
3>
3>The generated json path is C:\Users\USER\AppData\Local\Temp\tmpE26D.tmp.json
3>Processing and validating cluster config.
3>Check if machine 'ComputerFullName' is IOT Core: False. Could not open registry key.
3>Performing Stop-Service on service: FabricHostSvc . This may take a few minutes...
3>Create node configuration succeeded
3>Performing Start-Service on service: FabricHostSvc . This may take a few minutes...
3>
3>Waiting for Service Fabric Cluster to be ready. This may take a few minutes...
3>Local Cluster ready status: 4% completed.
3>Local Cluster ready status: 8% completed.
3>Local Cluster ready status: 100% completed.
3>WARNING: Service Fabric Cluster is taking longer than expected to connect.
3>
3>Waiting for fabric:/System/NamingService to be ready. This may take a few minutes...
3>Connect-ServiceFabricCluster : No cluster endpoint is reachable, please check if there is connectivity/firewall/DNS
3>issue.
3>At C:\Program Files\Microsoft SDKs\Service Fabric\Tools\Scripts\ClusterSetupUtilities.psm1:979 char:12
3>+ [void](Connect-ServiceFabricCluster #connParams)
3>+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3> + CategoryInfo : InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricException
3> + FullyQualifiedErrorId : TestClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
3>
3>fabric:/System/NamingService ready status: 8% completed.
3>fabric:/System/NamingService ready status: 17% completed.
3>fabric:/System/NamingService ready status: 92% completed.
3>fabric:/System/NamingService ready status: 100% completed.
3>WARNING: fabric:/System/NamingService is taking longer than expected to be ready...
3>Local Service Fabric Cluster created successfully.
3>--------------------------------------------------
3>Launching Service Fabric Local Cluster Manager...
3>You can use Service Fabric Local Cluster Manager (system tray application) to manage your local dev cluster.
3>Finished executing script 'Set-LocalClusterReady'.
3>Time elapsed: 00:12:29.9792319
3>The PowerShell script failed to execute.
========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
I tried closing down my Windows firewall and debugging again, now getting:
Unable to determine whether the application is installed on the cluster or not
Unable to determine whether the application is installed on the cluster or not
I have encountered this error before and have solved it in 2 ways:
I simply redeployed to the local cluster.
I stopped the local cluster from the tray menu before redeploying.
When I try to run or build my application I am getting the following error:
Faulting application name: MSDEV.EXE, version: 6.0.9782.2, time stamp: 0x40400977
Faulting module name: devncb.pkg, version: 6.0.8168.0, time stamp: 0x3588a3b6
Exception code: 0xc0000005
Fault offset: 0x0000ecff
Faulting process id: 0x116c
Faulting application start time: 0x01cf4a5b10f241ca
Faulting application path: C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\MSDEV.EXE
Faulting module path: C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\IDE\devncb.pkg
Report Id: 77fc74a1-b64e-11e3-894a-d4bed9e13763
I am using Microsoft visual c++ 6.0. I have tried excluding my program under DEP but I still get the same issue. I also get the error when I try to open it in my workspace.