Duplicate Ganache accounts - token

When I run Ganache in the background and choose Web3 provider as the Environment in remix IDE, I always get a duplicate copy of the Account list. That is, the Account list shows twice in the drop down list box.
Has anybody seen this before?
I wonder if this is a bug and the same issue doesn't happen to Injected Web or Javascript VM.

Related

Trying connecting solution to "Azure Cosmos DB Emulator on container (Local)", does "nothing"

Context
I am trying to run a solution. I did not create it and I cannot contact its creator (because it is some kind of exercise).
This solution has a React front-end running on API through Axios.
I do not know this type of stack very well.
Running the API through npm start, I get a 404 error when the API is called.
I'm not sure if and how npm start is supposed to be able to start a C# webservice at the same time as the React application.
So, maybe I'm going in a completely wrong direction at this point but,
I guess that I should launch the API from Visual Studio in parallel.
I know that I'm supposed to use local CosmosDBService to reach some database.
In the service appsettings.json, CosmosDB.Account and CosmosDB.Key are empty.
'CosmosDB' also has a CosmosDB.Content property (which looks like a long encrypted string). I expect that this is the database content (it should not be very big) stored in the JSON file, but I don't find much info about this precise property.
What I am trying right now is to connect the solution to the DB in Visual Studio through [Solution] > Connected Services > Azure Cosmos DB > Right click > Connect then in the dialog, I try to select Azure Cosmos DB Emulator on container (local)
(The other option is Azure Cosmos DB but I think that I need an Azure account for this.)
Docker is required to go further.
I install Docker (I'm on Windows 10). Docker requires something called something like WSL 2 Linux Services. I install WSL 2 Linux Services, but Docker keeps requiring it even after rebooting the whole system.
I read that an alternative way is use Hyper-V. I enable Hyper-V through Powershell. Reboot system. I uncheck WSL 2 in Docker. Reboot everything again. Docker now starts successfully.
Back in Visual Studio [Solution] > Connected Services > Azure Cosmos DB > Right click > Connect then in the dialog, I try to select Azure Cosmos DB Emulator on container (local). The 'Finish' button is greyed out, but the 'Next' button is active.
When I click on the 'Next' button, nothing happens... No error, not other dialog box, just no info and no clue at this point. And the current Dialog is not closing. Clicking on 'Next' literally does nothing.
Edit: I noticed that first time clicking on 'Next' after relaunching Visual Studio, for a very brief moment, the cursor display "Loading" start and something appears at the bottom left of that dialog box (it just says "Waiting" and then disappears).
Question
By reading the previous paragraphs, you may understand that I'm trying to run an application stack completely out of my "comfort zone". So I'm no asking for complete solution about this whole situation. (Though suggestions are welcome.)
The scope of my question here is limited to:
Why clicking on 'Next' is doing nothing? What am I missing? How can I diagnose this?

How to make container installation behave like host machine installation

I'm working with the following:
Docker for Windows v20.10.11
Docker running in Windows container mode
mcr.microsoft.com/windows:1903 base image
Proprietary application installed on top of this base image
Each year we create a Docker image with the latest version of our company's software. However this year's version behaves differently. Host machine installation runs fine. Containerized installation fails to run in certain situations. I can start the application as a simple EXE, for example using the Docker run command. The app will start and show up in "tasklist". However I can't start the app via the COM API, which is a critical requirement. The problem appears to be COM related. Normally we can create COM objects for our software just like for any other application. For example, IE returns a COM object just fine:
Creating these objects for our application works outside containers. However inside the container, our latest installation gives this error:
Access permissions appear to be ok. I tried a couple tests to prove this. First I can install other software like MS Word into a container and create COM objects for that:
Second I tried retrieving + modifying the application's DACL in PowerShell.
Changing access masks or trustees can cause an Access Denied error:
This also appears to confirm the access permissions were Ok by default.
Next I made sure COM is aware of the application. This appears to be fine. I get the same result on host machine and container when running this PS script:
gci HKLM:\Software\Classes -ea 0| ? {$.PSChildName -match '^\w+.\w+$' -and
(gp "$($.PSPath)\CLSID" -ea 0)} | ft PSChildName
The application shows up just like any other. The details show up fine when querying by AppID. LocalServer32 points to the correct EXE:
Some other things I tried:
Querying registry keys. There are 7 keys created when installing our software. These appear identical on host machine install and container install.
Even though permissions appear fine, I still tried logging into the container as alternate users. For example "nt authority\system" is another virtual admin user. I also changed the password of the "builtin\administrator" user to enable logging in with that one. Lastly tried creating new users entirely and adding them to the Administrators user group. All these attempts had the same errors as "builtin\containeradministrator" (default user).
A minor check was ensuring CMD.exe / Powershell is running as x64:
Re-registering the DLLs associated with the installation using regsvr32.
Starting from different base images. https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-base-images. The full Win Server base image behaves exactly the same way regarding errors. The smaller Win Server Core base image is even more problematic, as I can't even start the app's EXE manually using that base. Lastly I tried other tags of the full Windows base image such as 20H2 and 2004. Same result from those. Multiarch or x64 makes no difference.
Included the "Ogawa hack" which was historically needed to make MS Office apps function correctly with COM: https://stackoverflow.com/a/1680214/7991646. It could be necessary for other COM apps too, but didn't help with my specific installation.
Is there anything else I can do to diagnose or solve this COM issue?
There are several things to consider:
The Considerations for server-side Automation of Office article states the following:
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
The When CoCreateInstance returns 0x80080005 (CO_E_SERVER_EXEC_FAILURE) page describes possible reasons.
If many COM+ applications run under different user accounts that are specified in the This User property, the computer cannot allocate memory to create a new desktop heap for the new user. Therefore, the process cannot start. See Error when you start many COM+ applications: Error code 80080005 -- server execution failed for more information.
Finally, you may find a similar thread here helpful, see Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)).

Start electron app with admin privileges as default

I created an electron app which can only be started as admin, because it needs it for various command executions. Now it prompts that it must be started as admin.
This question was very helpful.
Now I want to start it with admin privileges right away so windows asks for the acception. It shouldn't be able to start the app without admin privileges.
I tried adding --win32metadata.requested-execution-level=requireAdministrator, but then it writes an error on startup (always):
The application has failed to start because the side by side configuration is incorrect.
How can I achive this with the electron packager?
Your electron-packager code looks fine, and the switch works for me.
This can happen if you are missing Visual C++ Runtimes, or if they're corrupted. Try installing them from here and try again.
If that doesn't help, then you should dig into the Event Viewer, which should come installed on your machine, and see what the specific error is. This page has some additional tips on troubleshooting this issue.

Umbraco 6.0.3 missing content and media nodes

I have just put up an Umbraco 6.0.3 site on eHosting and set all the directory permissions iaw our.umbraco.org/.../permissions. And this(http://our.umbraco.org/wiki/reference/files-and-folders/permissions/perform-permissions-check) reports the permissions as "perfect". .NET framework set to 4.0 and App pool has been set and recycled. Site shows up but no macros load and in the Umbraco UI there is only a Content node and a Media node, both the Content and Media trees are empty.
I can't think of anything else it can be. This is the first V6 site I've put live.
Is there anything else I can check?
Cheers
Check that your user login has permissions to view those nodes. The fact that you are not seeing any other sections (Settings, Developer, etc) suggests this.
Also - are you using any hostnames in Umbraco for the site (where you right click and click manage hostnames on the content node)? If so then check that the root node has a wildcard hostname added.
This is a case of retracing your steps over what you've done. If the other options don't work then you can do a database refresh too (copy the dev database to live). The fact you can login to the admin UI, says that you have the database working. However, is it possible that you've tweaked anything manually in the database?
Are you using MVC or ASP.NET rendering engine?
Check your log files and paste them here if all else fails and we'll try and help you out as best we can. You'll find them in App_Data/Logs/UmbracoLogs.txt
When the content and media nodes failed to load for us in Umbraco 6.0.3 it was due to a bug in Courier which causes the back-office to malfunction if you are connected to a MySQL database (throws an exception complaining "Keyword not supported: 'charset'").
Courier interferes with many back office functions and in this case it is incorrectly assuming that you must be connecting to an MSSQL server.
The only solution was to uninstall Courier (which was OK for us because we'd already determined that there are too many show-stopping bugs for it to function as advertised).

Error TF218027 when creating a Team Project in TFS 2010

Consider the scenario of a user creating a new Team Project. The user is a developer who wants to create and manage their Team Project.
Why can't this user create a new Team Project, including the Reporting Services components?
What can be done to resolve this error?
The exception is
TF218027: the following reporting folder could not be created on the server running SQL Reporting Services.
SQL Reporting services is running under an Active Directory service account created expressly for this purpose.
The developer attempting this action is a member of a TFS group with the following permissions.
The workaround way that I implemented was to ensure the developer was in a group that had 'Content Manager' permissions in the SQL Reporting Services.
I simply added the appropriate AD group in the textbox, and the operation worked perfectly.
First I visited the SSRS page at http://myServer/TFS/Reports/MyCollection
Enter the "New Role Assignment" screen.
I actually blogged about this not too long ago. You usually see this error if Reporting Services gets set up with something other than the NETWORK SERVICE account.
FTA:
I was playing around with my test
instance of Team Foundation Server
today, trying to create a new project,
when I got error TF218027 when it
tried to create the Reporting Services
folder for the project. The strange
thing was, this was not my first
project created on this server.
I searched the Internet for anything
similar, and found a post that said
Reporting Services should be run with
the NETWORK SERVICE account. Since
this was a hastily put together
server, I was running it with the
Administrator account, so I tried
switching it over.
No dice. I got the same TF218027
error, but this time it was due to it
not being able to decrypt the
symmetric keys. Apparently, it's a
bad thing to change the account on the
Reporting Services service.
I hastily changed the account back to
Administrator and resarted the
service. Interestingly enough, this
seems to have fixed the problem.
I just run throught the same issue. I granted the user rights in SharePoint, TFS, and Report Server. And still I was getting the same error message. Then I realized something. I added that user to the Report Server's local administrator's group. It worked! Hopefully this help you out.

Resources