Windows Azure Project is not loading - visual-studio-2010

I am having below mentioned issue when I am running The Azure Project on Emulator.
Below mentioned error popup is not coming always.
It's appearing Time to Time
Sometimes my Azure project loads as expected but sometimes not
Why ?
My Environment as below :
VS 2010 SP 1
MVC 2 Project
Windows Azure Tools for Microsoft Visual Studio 2010 - October 2012 v1.8.51019.1603
Error shown as below :
My Azure project as below:
Error message on IISConfigurator
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:39.516] Started iisconfigurator with args /start
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:39.532] StartForeground selected. Check if an instance is already running
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:39.563] Starting service WAS
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:39.813] Starting service w3svc
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:39.828] Starting service apphostsvc
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:40.764] Setting registry key for cloud drive to path:C:\Users\sampath\AppData\Local\dftmp\wadd
IISConfigurator Information: 0 : [00005740:00000001, 2013/01/02 12:14:40.858] IISConfigurator is running
IISConfigurator Information: 0 : [00005740:00000006, 2013/01/02 12:14:40.998] Clean operation called over WCF interface with prefix 'deployment18('
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.64] Deploying sites from package path D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web.Azure\csx\Debug\roles\PawLoyalty.Web with given optional destination directory
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.64] Using full IIS appdomain
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.687] Creating site named deployment18(2790).PawLoyalty.Web.Azure.PawLoyalty.Web_IN_0_Web for modelled site name Web
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.687] Deploying site named deployment18(2790).PawLoyalty.Web.Azure.PawLoyalty.Web_IN_0_Web
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.687] Using package path D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web\ which exists? True
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:11.687] Adding binding 127.255.0.0:82:www.pawloyalty.com to site deployment18(2790).PawLoyalty.Web.Azure.PawLoyalty.Web_IN_0_Web
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:12.545] Add access for appPool d3f7f918-51ee-4c8b-b113-18bdf8ff08c9 to runtime api instance deployment18(2790).PawLoyalty.Web.Azure.PawLoyalty.Web_IN_0 for SID
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:12.794] Add access for appPool d3f7f918-51ee-4c8b-b113-18bdf8ff08c9 to site directory D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web\ for SID
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:12.794] Adding access to users IUSR and NT AUTHORITY\NETWORK SERVICE to path D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web\
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.371] Added access to users IUSR and NT AUTHORITY\NETWORK SERVICE to path D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web\
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.371] Add access to NetworkService to web.config
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.387] Add access for appPool d3f7f918-51ee-4c8b-b113-18bdf8ff08c9 to cloud drive directory C:\Users\sampath\AppData\Local\dftmp\wadd for SID
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.387] Deploy Complete
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.387] Add read access to runtime base dir
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.387] Adding access to IIS_IUSRS to D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web.Azure\csx\Debug\roles\PawLoyalty.Web\base
IISConfigurator Information: 0 : [00005740:00000007, 2013/01/02 12:15:13.917] Added access to IIS_IUSRS to physical path D:\PawLoyalty Module\PawLoyalty\PawLoyalty\PawLoyalty.Web.Azure\csx\Debug\roles\PawLoyalty.Web\base
IISConfigurator Information: 0 : [00005740:00000010, 2013/01/02 12:15:13.964] Wait for all sites to be setup in IIS
IISConfigurator Information: 0 : [00005740:00000010, 2013/01/02 12:15:14.151] All sites and app pools are ready, wait for sites complete.
When I click PawLoyalty.Web.Azure -> Properties -> Web It's like below

Enable IISExpress and try again. If it does not work, check the logs mentioned in the comments.

Related

Caused by: java.io.IOException: Invalid keystore format

I have a JBoss 7.4.0 installation running in domain mode on a RHEL 7 platform. The JDK version is java version "15.0.2" 2021-01-19
Java(TM) SE Runtime Environment (build 15.0.2+7-27)
I am using the Jboss documentation How to Configure Server Security, specifically section 2.5: Configuring SSL/TLS for the legacy core management authentication mechanism. I am setting up Two-Way SSL/TLS.
I create a keystore, generate key pairs, export and import certificates. The storetype is JCEKS. (I have also tried using PCKS12 and JKS, same issue)
When I try to start the JBoss server I see the following error:
06:47:41,216 INFO [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final-redhat-00001
06:47:41,498 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final-redhat-00001
06:47:41,514 INFO [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 06:47:41,982 INFO [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final-redhat-00001
...
[Host Controller] 06:47:43,848 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /u01/redhat/jboss/domain_74/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[Host Controller] 06:47:43,851 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.20.SP1-redhat-00001
[Host Controller] 06:47:43,852 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.core.management.security.realm.CertificateRealm.key-manager: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.CertificateRealm.key-manager: Failed to start service
[Host Controller] at org.jboss.msc#1.4.12.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
...
[Host Controller] Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0018: Unable to start service
...
[Host Controller] Caused by: java.io.IOException: Invalid keystore format
So my understanding is the issue is with the keystore format, yet if I use another keystore format I get the same issue.
And, when I run the following command I get success:
./keytool -list -keystore $EAP_HOME/vault/h1vault.jceks
Enter keystore password:
Keystore type: JCEKS
Keystore provider: SunJCE
Your keystore contains 3 entries
h1server_alias, Sep 20, 2022, PrivateKeyEntry,
Certificate fingerprint (SHA-256): 58:58:36:82:EE:B5:88:BB:AF:59:F6:17:F2:9B:D3:29:D6:CC:DD:02:04:E5:3B:50:8A:70:AB:5C:85:59:DD:25
h1vault, Sep 20, 2022, SecretKeyEntry,
host2_alias, Sep 20, 2022, trustedCertEntry,
Certificate fingerprint (SHA-256): 62:07:76:CB:B7:B8:9C:89:6D:36:82:8B:5B:8A:E9:7E:8E:6A:23:8E:51:56:03:B9:F9:98:D3:DA:D4:53:B5:57
I would expect this command to fail if the keystore format was incorrect.
I have read all sorts of threads and so on about this but cannot find an answer.
Appreciate if anyone can suggest possible solutions.
Thanks

Xamarin Android Profiler won't start — "Deploy your app again with a newer version of Xamarin Studio"

We're struggling to get the Xamarin Profiler to start with our Android application.
We're using Visual Studio 2017 Enterprise (15.4.3) with Xamarin Profiler v1.6.0.16, Xamarin version 4.7.10.38.
Every time we try to use the profiler, it simply stops and writes to its log file:
Runtime installed on device [...] is too old. Deploy your app again with a newer version of Xamarin Studio.
This confuses us since we're not using Xamarin Studio at all.
We've tried:
checking for VS/Xamarin updates (obviously).
creating a new empty Xamarin project and attempting to profile it.
various devices and emulators.
various combinations of 'Target Framework', 'Minimum Android version' and 'Target Android version'.
Windows 7 and Windows 10.
Visual Studio both v15.4.3 and v15.5.0.
'Enable developer instrumentation (debugging and profiling)' is checked.
'Use Shared Runtime' and 'Use Fast Deployment' checked/unchecked.
But we always get the same result: "Deploy your app again with a newer version of Xamarin Studio".
Any suggestions would be greatly appreciated; thanks.
The profiler's log file is as follows:
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.2416] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.2416] # Xamarin Profiler version - 1.6.0.16
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.2416] # * Arch x86_64
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.2416] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.3820] initializing android platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.3820] initializing ios platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.3820] initializing mlpd platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-11-15 10:19:34.4600] processing command line = C:\Program Files (x86)\Xamarin\Profiler\XamarinProfiler.exe --type=android --target=au.com.<redacted>|md52635741fd041340e6948a5329c9048f1.MainScreen --device=025b38394ca8478b --options=name:LGE Nexus 5X
XamarinProfiler.Windows.Core.WindowsRunFactory Information: 0 : [2017-11-15 10:19:44.6840] Creating android run for au.com.<redacted>|md52635741fd041340e6948a5329c9048f1.MainScreen target on device 025b38394ca8478b
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:44.7152] Initializing profiling...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:44.7620] Waiting for device 025b38394ca8478b to connect
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-11-15 10:19:44.7620] StartRecording for au.com.<redacted>
XamarinProfiler.Core.Platforms.Android.ProfileAndroidRun Information: 0 : [2017-11-15 10:19:45.4582] checking runtime version on device LGE Nexus 5X
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-11-15 10:19:46.1802] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-11-15 10:19:46.1802] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:46.1812] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:46.1822] Stopping application au.com.<redacted>.md52635741fd041340e6948a5329c9048f1.MainScreen
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-11-15 10:19:46.1892] Error occured on run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-11-15 10:19:46.1892] Error occured on run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:46.2812] Application au.com.<redacted>.md52635741fd041340e6948a5329c9048f1.MainScreen stopped
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:46.2852] Stopping session. Please wait...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:19:46.2952] Stopped
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-11-15 10:19:46.2982] CurrentRun.Finished for au.com.<redacted>
XamarinProfiler.Windows.Core.WindowsRunFactory Information: 0 : [2017-11-15 10:20:48.4232] Creating android run for au.com.<redacted>|md52635741fd041340e6948a5329c9048f1.MainScreen target on device 025b38394ca8478b
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:48.4232] Initializing profiling...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:48.4562] Waiting for device 025b38394ca8478b to connect
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-11-15 10:20:48.4562] StartRecording for au.com.<redacted>
XamarinProfiler.Core.Platforms.Android.ProfileAndroidRun Information: 0 : [2017-11-15 10:20:50.0302] checking runtime version on device LGE Nexus 5X
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-11-15 10:20:50.7792] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-11-15 10:20:50.7792] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:50.7792] Sorry, something went wrong trying to run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:50.7792] Stopping application au.com.<redacted>.md52635741fd041340e6948a5329c9048f1.MainScreen
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-11-15 10:20:50.7802] Error occured on run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-11-15 10:20:50.7802] Error occured on run au.com.<redacted>: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:50.8902] Application au.com.<redacted>.md52635741fd041340e6948a5329c9048f1.MainScreen stopped
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:50.8902] Stopping session. Please wait...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-11-15 10:20:50.8902] Stopped
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-11-15 10:20:50.8912] CurrentRun.Finished for au.com.<redacted>
I suspect that you are all downloading the profiler from
https://learn.microsoft.com/en-gb/xamarin/tools/profiler/?tabs=windows
which actually is a link to an older version with a bug, try downloading it from
https://learn.microsoft.com/en-gb/xamarin/tools/profiler/release-notes/1.6/1.6.4
with the latest stable version and it should work, at least it did for me.
cheers
Same here, adding research. Xamarin Profiler fails with the example SingleViewApp Xamarin project running on LGE Nexus 5X Android 8.0.0 but succeeds running on old Samsung SM-T280 Android 5.1.1.
Failure case profiler log
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.5188] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.5207] # Xamarin Profiler version - 1.6.0.16
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.5207] # * Arch x86_64
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.5207] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.7168] initializing android platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.7168] initializing ios platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.7174] initializing mlpd platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:47:34.8973] processing command line = C:\Program Files (x86)\Xamarin\Profiler\XamarinProfiler.exe --type=android --target=SingleViewApp.SingleViewApp|singleviewapp.SingleViewApp --device=00d0eee43fcc3e58 --options=name:LGE Nexus 5X
XamarinProfiler.Windows.Core.WindowsRunFactory Information: 0 : [2017-12-03 14:47:45.4078] Creating android run for SingleViewApp.SingleViewApp|singleviewapp.SingleViewApp target on device 00d0eee43fcc3e58
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:45.4293] Initializing profiling...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:45.4850] Waiting for device 00d0eee43fcc3e58 to connect
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-12-03 14:47:45.4880] StartRecording for SingleViewApp.SingleViewApp
XamarinProfiler.Core.Platforms.Android.ProfileAndroidRun Information: 0 : [2017-12-03 14:47:48.0039] checking runtime version on device LGE Nexus 5X
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-12-03 14:47:49.5410] Sorry, something went wrong trying to run SingleViewApp.SingleViewApp: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Error: 0 : [2017-12-03 14:47:49.5410] Sorry, something went wrong trying to run SingleViewApp.SingleViewApp: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:49.5420] Sorry, something went wrong trying to run SingleViewApp.SingleViewApp: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:49.5430] Stopping application SingleViewApp.SingleViewApp.singleviewapp.SingleViewApp
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-12-03 14:47:49.5470] Error occured on run SingleViewApp.SingleViewApp: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.MainWindow Error: 0 : [2017-12-03 14:47:49.5470] Error occured on run SingleViewApp.SingleViewApp: Runtime installed on device LGE Nexus 5X is too old. Deploy your app again with a newer version of Xamarin Studio
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:49.7319] Application SingleViewApp.SingleViewApp.singleviewapp.SingleViewApp stopped
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:49.7470] Stopping session. Please wait...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:47:49.7571] Stopped
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-12-03 14:47:49.7754] CurrentRun.Finished for SingleViewApp.SingleViewApp
Failure case Android logcat
12-03 14:37:34.523: D/AndroidRuntime(19727): >>>>>> START com.android.internal.os.RuntimeInit uid 2000 <<<<<<
12-03 14:37:34.781: D/AndroidRuntime(19727): Calling main entry com.android.commands.pm.Pm
12-03 14:37:34.813: I/app_process(19727): System.exit called, status: 0
12-03 14:37:34.813: I/AndroidRuntime(19727): VM exiting with result code 0.
12-03 14:37:34.815: W/MessageQueue(19727): Handler (android.os.Handler) {6ee8755} sending message to a Handler on a dead thread
12-03 14:37:34.815: W/MessageQueue(19727): java.lang.IllegalStateException: Handler (android.os.Handler) {6ee8755} sending message to a Handler on a dead thread
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:545)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.Handler.enqueueMessage(Handler.java:661)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.Handler.sendMessageAtTime(Handler.java:630)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.Handler.sendMessageDelayed(Handler.java:600)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.Handler.post(Handler.java:356)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.ResultReceiver$MyResultReceiver.send(ResultReceiver.java:57)
12-03 14:37:34.815: W/MessageQueue(19727): at com.android.internal.os.IResultReceiver$Stub.onTransact(IResultReceiver.java:58)
12-03 14:37:34.815: W/MessageQueue(19727): at android.os.Binder.execTransact(Binder.java:674)
12-03 14:37:35.793: I/ActivityManager(771): Force stopping SingleViewApp.SingleViewApp appid=10444 user=0: from pid 19740
Success case profiler log
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.2196] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.2216] # Xamarin Profiler version - 1.6.0.16
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.2226] # * Arch x86_64
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.2226] ##########################################
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.4174] initializing android platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.4174] initializing ios platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.4186] initializing mlpd platform
XamarinProfiler.Core.Profiler Information: 0 : [2017-12-03 14:56:40.8207] processing command line = C:\Program Files (x86)\Xamarin\Profiler\XamarinProfiler.exe --type=android --target=SingleViewApp.SingleViewApp|singleviewapp.SingleViewApp --device=3100784abd71b200 --options=name:Samsung SM-T280
XamarinProfiler.Windows.Core.WindowsRunFactory Information: 0 : [2017-12-03 14:57:15.4411] Creating android run for SingleViewApp.SingleViewApp|singleviewapp.SingleViewApp target on device 3100784abd71b200
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:15.4632] Initializing profiling...
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:15.5209] Waiting for device 3100784abd71b200 to connect
XamarinProfiler.Windows.MainWindow Information: 0 : [2017-12-03 14:57:15.5229] StartRecording for SingleViewApp.SingleViewApp
XamarinProfiler.Core.Platforms.Android.ProfileAndroidRun Information: 0 : [2017-12-03 14:57:17.6114] checking runtime version on device Samsung SM-T280
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:19.0527] Starting application SingleViewApp.SingleViewApp.singleviewapp.SingleViewApp
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:20.8807] Starting profiler on Android device Samsung SM-T280 with heapshot=ondemand,alloc,nocalls,maxframes=8,counters,
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:21.6067] Opening C:\Users\robert\AppData\Local\Temp\hlvkcpc1.mlpd
XamarinProfiler.Core.Platforms.Mono.MlpdReader Information: 0 : [2017-12-03 14:57:21.6323] opening C:\Users\robert\AppData\Local\Temp\hlvkcpc1.mlpd
XamarinProfiler.Core.Platforms.Mono.MlpdReader Information: 0 : [2017-12-03 14:57:21.9964] read header with format version 13
XamarinProfiler.Windows.ViewModels.ProgressReport.ReportViewModel Information: 0 : [2017-12-03 14:57:22.5255] Reading data...
Success case Android logcat (too long to include)
You should update your Visual Studio to Visual Studio 2017 Enterprise (15.6.2) and the Profiler will work. I had the same proble

XAMPP on Windows - Attempting to start Apache service... - No Port block

I have installed XAMPP on my windows 7 machine but can't get Apache to work.
After opening the XAMPP panel and installing Apache service: I have tried start it, it always get stuck at "Starting apache service..."
On start I get the following:
7:36:57 [main] Initializing Modules
7:36:57 [main] The MySQL module is disabled
7:36:57 [main] The FileZilla module is disabled
7:36:57 [main] The Mercury module is disabled
7:36:57 [main] Starting Check-Timer
7:36:57 [main] Control Panel Ready
7:37:02 [main] Executing "services.msc"
7:41:50 [Apache] Attempting to start Apache service...
Event Viewer:
The Apache service named
reported the following error: >>>
httpd.exe: Syntax error on line 172 of C:/xampp/apache/conf/httpd.conf: Cannot load modules/mod_ssl.so into server: The specified module could not be found.
I also get an ERROR for the .NET Runtime Optimization Service:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 . Error code = 0x80070002
PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
On the first start i had some .dll problems but i solved them, I do not know if it is related.
I already tried everything in:
"XAMPP - Apache could not start - Attempting to start Apache service"
without improvement.
Any advice on how I could resolve this ?
Thanks
Go to Xampp control panel and click on config->httpd.conf then go to line no 171 and change
ServerName localhost:80
with
ServerName localhost:81
It will work.

How to find out the PID of a running Windows service from the command line given the service name?

I have the name of a Windows service as it appears in the service control panel. I know that service is running. How do I get the PID of the service using the windows command line?
(Background: I want to verify if a specific service appears in jconsole or not).
sc queryex <name>
See SC.
Example:
>sc queryex Tomcat9
SERVICE_NAME: Tomcat9
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 4908
FLAGS :
>

something wrong with jbpm and kie server

I want use jbpm6's rest interface,so i installed the kie. I put the kie-server-6.3.0.Final-ee7.war in the deployments folder and new the hibernate.properties in the jbpm-installer folder.Then i command ./add-user.sh -a -u admin -p admin -g admin,kie-server and standalone.sh -c standalone-full.xml -Dorg.kie.server.id=hello-kie-server -Dorg.kie.server.location=http://localhost:8080/kie-server-6.3.0.Final-ee7/services/rest/server.But it failed.the errors are:
ERROR [org.kie.server.services.impl.KieServerImpl] (MSC service thread 1-8) Error when initializing server extension of type jBPM KIE Server extension: java.lang.RuntimeException: Unable to create EntityManagerFactory due to [PersistenceUnit: org.jbpm.domain] Unable to build EntityManagerFactory
Caused by: javax.naming.NameNotFoundException: datasources/ExampleDS -- service jboss.naming.context.java.jboss.datasources.ExampleDS
(all ExampleDS have change to jbpmDS)
ERROR [org.guvnor.structure.backend.repositories.RepositoryServiceImpl] (MSC service thread 1-1) Error during create repository: java.lang.RuntimeException: https://github.com/guvnorngtestuser1/jbpm-console-ng-playground-kjar.git: cannot open git-upload-pack
(I don't kown which file use the address?)
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."jbpm-console.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions:Exception 0 :org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void org.kie.workbench.backend.AppSetup.assertPlayground()org.kie.workbench.backend.AppSetup#3d037714
I want open web http://localhost:8080/kie-server/services/rest/server/ but it failed. it means the kie server start failed? I don't kown why?

Resources