This is a desperate cry for help. I am working on my finals exam and need a few tools to do this, mainly an SQL Server.
In short, I can't for whatever reason install SQL Server 2014 Express.
When installing, I just set up everything with its default values and settings and then let it perform the install, everything goes fine until it reaches the stage: SqlEngineDbStartConfigaction_install_configrc_cpu64 where it stop with an error. Details can be seen in this picture as well as error code and description: http://imgur.com/pq2BB6c
For the full error log just follow this link: http://pastebin.com/FfWeJi0i
I have tried literately everything I can think of, I edited permissions, registry, uninstalled reinstalled countless times, I updated windows several times, restarted countless times, I even went as far as to fully format my pc and start over.. however this too turned out to be a waste of time since the problem persists even after the reinstall of windows 7.
If I can't get this issue resolved I might not be able to finish my exam project, so consider me desperate.
Related
I dont know if anyone ever come up with this situation but today I come up with this weird situation with codedu, nothing works when I run tests. Today when I come to office , installed AccessDatabaseEngine for datadriven test and start a testMethod, none of my records are running, I took a new record and also not working. Restart VS or restart PC doesnt help. Please somebody help me getting out of this situation. When I run a test, it bring up the already open application (UAT) but can not play.
I am not sure whether its cause but I installed AccessDatabaseEngine before running any test. I tried to uninstall it but when I look at applications I cant see where its placed..
I noticed that I doesnt record all, I tried to record a new test. It throws "Access is Denied", while capturing the application
and it gives Control not found error when I try to run
I found some pages for same error
I checked CodedUITestBuilder config file and I see this line was commented and I changed it but this did not fixed.
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
I also tried changing properties of CodedUITestBuilder.exe but again same result
Coded UI Test Builder fails to generate code for recorded action
Its fixed after I uninstalled the AccessDatabaseEngine . I installed it by clicking same exe. I should not install it because its too old, that is obvious with its icon.
For the last 3 days I have been trying to figure out how to install node.js. I tried every solution that I found on the internet, like disabling certain components during installation, installing both x86 and x64 etc, none of them worked.
My OS is Windows 10 x64. I tried different versions of node.js and they all return the same error shown in the screenshot below.
I tried installing through the command line and got the log. But I could not find anything useful from the log either. Please help.
The log can be found here: this path : https://drive.google.com/open?id=1OkkK36hlQeBX0xTNuOuilGaNr1u3S55e
MSI (s) (74:88) [20:49:45:955]: Executing op: ActionStart(Name=RegisterEventManifest,,)
MSI (s) (74:88) [20:49:45:961]: Executing op: CustomActionSchedule(Action=RegisterEventManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="wevtutil.exe" im "C:\Program Files\nodejs\node_etw_provider.man")
MSI (s) (74:A0) [20:49:45:969]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI33C1.tmp, Entrypoint: CAQuietExec
CAQuietExec: Error 0xc0000409: Command line returned an error.
This is the relevant part of the log and where the install keels over, noise removed. 0xc0000409 is very, very nasty. STATUS_STACK_BUFFER_OVERRUN is a stack corruption error, triggered by code that protects against viral attacks.
Searching for "nodejs install 0xc0000409" takes you to this bug report, notable from December 2015. This issue has been dogging users for a long time, but they are having trouble finding the root cause. The generic workaround is to disable this install step by disabling the installation of the ETW performance counters.
Which works, but is but a band-aid. I think macario1983's comment points at the real troublemaker. It got a lot of helpful votes in just two days. And points at the kind of viral rootkit that programmer's voluntarily install, the kind that can so easily cause a STATUS_STACK_BUFFER_OVERRUN error with no decent way to identify the code that causes it. Anti-malware has become a cure that is worse than the disease, Avast in particular is a truly awful product and does not belong on a programmer's machine.
So decent advice is to 1: disable the anti-malware product before installing Node. 2: get rid of completely if it is Avast. 3: disable the performance counter registration. 4: try the updated installer, patched 4 days ago.
I disabled the AVG antivirus(version 18.4.3056) but not windows firewall and then i was able to install nodejs.
Possible options to solve this:
1. Removing previous installations traces
If you have previous installations, make sure that they were uninstaled completely. If HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5} record exist in your register, remove it.
2. Disabling Performance Counters
If you don't need Performance counters feature, try to install without it (or maybe even without Event Tracing).
3. Disabling security and giving the full permissions
Clean Temp Folder
Disable your antivirus/firewall for the period of installation.
C:/users/$user/AppData/Local/Temp- Right Click on Temp and go to Properties > select Security Tab > give the user permissions by checking Full Control on permission
Install Node.js
I had today the same problem with Windows 10 64 bit and Node.js 8.11.2: disabling completly Avast just for the time of the installation solved the issue.
I was trying to install Node.js through node-v8.11.2-x64.exe, but it was rolling back every time at the end. The error in the event log was about wevtutil.exe, version 10.0.17134.1
I had the same issue on a Windows 2012R2 server installing node-v8.11.2-x64, and disabled the McAfee anti-virus to no avail. When I went to clean out the TEMP folder as suggested in this thread, I noticed that several files and folders were locked and could not be deleted, so I rebooted the machine (with the anti-virus disabled). After the reboot, I noticed that the locked temp files had been deleted, and I was able to install node.js, including the Performance Counters and Event Tracking options.
I spent one day for that ....Best solutions is download zip example node-v12.16.2-win-x86.zip.
I just came back from MWLUG and started to open up some Xpages DBs to work on, when all of the sudden I am getting 1000s of errors like this:
I googled the issue and I believe it has something to do with the path of the org.eclipse.pde.core.requiredPlugins.
When I opened up the packages and looked at fixing an error I got this:
The problem is that I do not know what the correct setting for this should be, or how to fix it. The apps run fine, but obviously something is wrong.
Any help would be very much appreciated.
Bryan
==================================================
I may know more about the problem. In designer when I go to File==>Application==Application Management this is what I see:
A different install has several components under it.
I updated my designer and client and admin to 9.0.1 FP4 last week. That is the last thing I remember doing before this messed up (along with installing the Debug Toolbar).
How can I fix my designer install?
Strange indeed, you should check your hard drive for bad sectors.
Looks like a broken DDE in general. The plugin XML file maybe broken so the app manager doesn't show you the plugins installed. Therefor I assume DDE starts very quickly, right? Because nothing is loaded.
I had this before and my "solution" was:
de-install DDE and Fixpacks
delete workspace folder
re-install DDE and Fixpacks
re-install plugins ad setup workig sets
This is a pity but at least you get a clean install. You don't have to delete everything (e.g. the DATA folder)
I've been following along with the actual MongoDB docs here
as well as several tutorial articles that are getting me absolutely nowhere.
Running a 64bit windows OS (which is a work computer, and my particular windows login is not an administrator login.. so I make sure to open any exe files as administrator). I can't do anything in the terminal beyond "mongo" or "use [db name]".
I cannot save or add anything like db.testData.insert( j ). Even typing "show dbs", I get an error that says
listDatabases failed:{ "ok" :0, "errmsg" : "unauthorized" } at src/mongo/shell/mongo.js:46
With every example I've followed, I can never seem to be "authenticated" to get past point A. Please help me! I have no idea what I'm doing wrong at this point.
UPDATE:
Sorry for the confusion, everyone. The problem turned out to be that I had an old MongoDB service still running in the background that I needed to disable.
The service must have been turned on while I was testing out some node packages or something. Once I disabled the service, everything started working as expected.
So for those of you who are having trouble, make sure you open up services.msc and make sure nothing is running MongoDB
As there isn't a formal installer for Windows, I'd recommend you delete the data folder and restart. Out of the box, there is no security in MongoDb, so you've followed a step which later requires a password. Either retrace your steps, or start over.
You don't need to switch to the admin Database. I'd suggest you instead switch to a test database for example:
> use test
switched to db test
By default, without extra configuration, on Windows you can delete the contents of c:\data\db when MongoDb isn't running (but if you're using a configuration file that specifies the dbpath, delete the contents of that folder).
There are a number of tutorials with details of how to configure users/security with Mongodb that you may want to read after you've resolved this issue.
There's little reason to create users and administrative control with MongoDB until you gain some experience with the platform. In fact, I wouldn't recommend it at all. It just gets in the way as you're seeing for no real gain.
I have a suite of tests for our website using Sahi. These tests are automated and feed into our Jenkins build system.
The tests run on a dedicated PC that is used for nothing else. It has Sahi plus all the browsers installed. The Jenkins server makes a remote call to the testing PC to run the tests. Due to the time it takes to run all the tests, this functional test suite is run overnight.
For several months this system was all working beautifully. But suddenly one day a few weeks ago I came into the office and found that all the tests had failed. they haven't worked since. As far as I know, nothing significant has changed (we obviously keep the browser versions up-to-date, but I don't think the failure co-incided with any updates; Sahi itself hasn't had an update since last year)
I've done some work to find out what's happening:
Sahi uses a proxy as part of it's browser control magic, and I believe that this proxy is the source of the problem. But I can't work out how or why.
When the browser under Sahi's control loads the page to be tested, it seems none of the HTTP requests are succeeding. The raw page content is shown (I think because it's cached), but none of the styles, graphics or scripts (except those already cached by the browser). Furthermore, the Sahi script then tries to click on a button to proceed through the test, but the browser fails to load anything. Sahi waits for a bit, but eventually the script times out and the test fails.
I can replicate this on the affected PC when running Sahi manually. It happens on any site, and in all browsers. However it doesn't happen on my own desktop PC, which has the same versions of all the relevant software installed. And of course, it worked fine in the past on the test box.
I have tried uninstalling Sahi and the browsers, and re-installing from scratch. This has not made any difference. (I appreciate that uninstalling often doesn't actually delete everything, so perhaps there's more I could do here?)
I'm really hoping someone can help me here, because I'm unsure what else to try.
Many thanks in advance.
Since it happens on all browsers, it looks like a firewall setting may be preventing access to port 9999. Turn off the firewall and check. If you see any exceptions on the Sahi console, you could post that too.
I wasn't able to get to the bottom of this. I suspect it was something blocking the Sahi proxy from working, but I couldn't find the culprit.
I'd wasted too much time on it, and the machine it was running on wasn't being used for anything else anyway, so my final solution to this was to re-install the OS from scratch.
This has solved the problem. It hasn't helped me understand why it happened, but as long as it's working, eh?
Thank you to everyone who stopped by.