When install DotNet Core on my windows 10 laptop(DotNetCore.1.0.0.RC2-VS2015Tools.Preview1),the runtime package setup failed.
I found some error information from the install log file:
web developer tool info:
[037C:1EC0][2016-06-19T11:07:26]e000: Error 0x80070643: Failed to install MSI package.
[037C:1EC0][2016-06-19T11:07:26]e000: Error 0x80070643: Failed to execute MSI package.
[2E70:3228][2016-06-19T11:07:26]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[2E70:3228][2016-06-19T11:07:26]i319: Applied execute package: WebToolsExtensionsVS14, result: 0x80070643, restart: None
[2E70:3228][2016-06-19T11:07:26]e000: Error 0x80070643: Failed to execute MSI package.
[037C:1EC0][2016-06-19T11:07:26]i318: Skipped rollback of package: WebToolsExtensionsVS14, action: Uninstall, already: Absent
[2E70:3228][2016-06-19T11:07:26]i319: Applied rollback package: WebToolsExtensionsVS14, result: 0x0, restart: None
[037C:1EC0][2016-06-19T11:07:26]i351: Removing cached package: WebToolsExtensionsVS14, from path: C:\ProgramData\Package Cache\{1F275091-F18D-37F3-8A70-8E6CE66BB1A8}v14.1.20512.0\
[037C:1EC0][2016-06-19T11:07:26]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{22041006-8484-4b8d-a13c-40189695de2f}, resume: ARP, restart: None, disable resume: No
[037C:1EC0][2016-06-19T11:07:26]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{22041006-8484-4b8d-a13c-40189695de2f}, resume: ARP, restart initiated: No, disable resume: No
[2E70:3228][2016-06-19T11:07:26]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No
Another Solution is to:
go to the folder where you have downloaded the installer
open the command prompt by Shift+right click -> Open command window here
Type - dotnetcore.1.0.0-vs2015tools.preview2 SKIP_VSU_CHECK=1 and hit enter
This should skip the VS update check and start the installation normally.
I was able to fix this issue by
turning off Antivirus
clearing the %temp% folder
running the DotNet Core (DotNetCore.1.0.0.RC2-VS2015Tools.Preview1) again in repair mode
After applying the other answers here the install was still failing for me. Periodically during the install, a pop-up warning dialog would open stating "The account already exists". I reviewed the Programs and Features list and saw 3 different entries for the VS2015Tools preview. I right-click Uninstall'ed each of them (which removed each one almost immediately), and tried the install again. This time it completed without errors.
Related
Currently running airflow 1.10.15. Wanted to perform some tests before upgrading to 2+. So installed pip install apache-airflow-upgrade-check in the scheduler pod which installed successfully. So I then run the command airflow upgrade_check but it did not return the results that I expected. It's giving me this output in terminal
[2021-06-15 21:02:38,637] {{settings.py:233}} DEBUG - Setting up DB connection pool (PID 15732)
[2021-06-15 21:02:38,637] {{settings.py:300}} DEBUG - settings.prepare_engine_args(): Using pool settings. pool_size=5, max_overflow=10, pool_recycle=1800, pid=15732
[2021-06-15 21:02:38,735] {{sentry.py:179}} DEBUG - Could not configure Sentry: No module named 'blinker', using DummySentry instead.
[2021-06-15 21:02:38,754] {{__init__.py:45}} DEBUG - Cannot import due to doesn't look like a module path
[2021-06-15 21:02:38,916] {{cli_action_loggers.py:42}} DEBUG - Adding <function default_action_log at 0x7f9a637c3a70> to pre execution callback
Please install apache-airflow-upgrade-check distribution from PyPI to perform upgrade checks
[2021-06-15 21:02:39,266] {{settings.py:310}} DEBUG - Disposing DB connection pool (PID 15732)
What am I missing?
Updated 6/16/2021: I verified if the package was installed, I did see the package in list:
...
apache-airflow 1.10.15
apache-airflow-upgrade-check 1.3.0
apispec 1.3.3
argcomplete 1.12.2
...
The problem I had was the container was running as a non-root user which was defined in Dockerfile. If I install the package in the running pod, it will install in some local directory and when executing the airflow upgrade_check command, it cannot find the package. To work-around this issue, I need to add the packages in Dockerfile so it will be included when creating the docker image.
I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.
look here figure below:
enter image description here
06/14 05:56:50: Launching 'app' on Pixel 3 API 29 3.
Installation did not succeed.
The application could not be installed.
List of apks:
[0] 'C:\Users\Ahmed\AFAQTravelTurismMobileApplication\app\build\outputs\apk\debug\app-debug.apk'
Installation failed due to: 'device offline'
Retry
C:\Users\Ahmed\AFAQTravelTurismMobileApplication\app\build\outputs\apk\debug\app-debug.apk
Go to the directory and (re)move app-debug.apk
Remove the device from the cable.
Connect the device again and try to run it.
Its worked for me.
I am getting below error while installing informatica 8.6:
****use the error below and catalina.out and node.log in the server/tomcat/logs directory on the current machine to get more information. Select Retry to continue the installation.
STDOUT: Installing the service '"Informatica Services 8.6.0"' on node 'node01_geettika4912'...
Using CURRENT_DIR: C:\Informatica\PowerCenter8.6.0\server\tomcat\bin
Using INFA_HOME: C:\Informatica\PowerCenter8.6.0
The service '"Informatica Services 8.6.0"' has been installed.
STDERR: The filename, directory name, or volume label syntax is incorrect.
The service name is invalid.
More help is available by typing NET HELPMSG 2185.**
EXITCODE: 2**
I am getting this error after the successful creation of domain.
Please help me in resolving this error.
Thanks!
Run services.msc to get a list of all the services.
Click properties on the service you want, there you can see the "service name" and the "display name".
The service name is what you need to use with the net command. Check if Informatica Services 8.6.0 is in the list.
I'm trying to start a new mean stack application. However i only get this error when I'm running grunt to start the server:
[nodemon] v1.2.1
Running "watch" task
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --debug server.js`
Waiting...
Debugger listening on port 5858
Mean app started on port 3000 (development) cluster.worker.id: 0
/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:246
throw message;
^
TypeError: Cannot read property 'length' of undefined
at processResults (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1581:31)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1619:20
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1157:7
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1890:9
at Server.Base._callHandler (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/base.js:448:41)
at /Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:481:18
at MongoReply.parseBody (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:439:20)
at emit (events.js:107:17)
at null.<anonymous> (/Users/olehenrik/Sites/learn/mean_test2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
[nodemon] app crashed - waiting for file changes before starting...
Have any one encountered this before? Can't find too many other people who have encountered this before.
I was also facing the same error and this info solves it.
"Upgrade to 3.8.23. 3.8.22 introduced better compatibility with mongodb server 3.0 by upgrading to latest version of the driver." credit to vkarpov15 from mongoose Github thread.
What I did was I edit my package.json to upgrade mongoose to "3.8.23". After I edited the package.json I ran npm install and bower install(just to make sure) again and that solved the problem.