Windows error 0x00000274, 628

Detailed Error Information


MessageThe server process is running under a SID different than that required by client.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070274.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
Reserved (X)false
FacilityCode0 (0x000)
DescriptionThe default facility code.[2][1]
Error Code628 (0x0274)

Possible solutions


ELF, Build-ID, is there a utility to recompute it?


So, I've got an answer from Mark. Since it is an up to date info, I post it here. But basically you guys are right. Indeed there is no tool for computing Build-ID, and the intentions of Build-ID are not (1) identification of the file contents, and not even (2) identification of the executable (code) part of it, but it is for (3) capturing "semantic meaning" of a build, which is the hard bit for formalization. (Numbers are for self-reference.)

Quote from the email:

-- "Is there a user tool recomputing the build-id from the file itself, to check if it's not corrupted/compromised somehow etc?" If you have time, maybe you could post an answer there?

Sorry, I don't have a stackoverflow account. But the answer is: No, there is no such tool because the precise way a build-id is calculated isn't specified. It just has to be universally unique. Even the precise length of the build-id isn't specified. There are various ways using different hashing algorithms a build-id could be calculated to get a universally unique value. And not all data might (still be) in the ELF file to recalculate it even if you knew how it was created originally.

Apparently, the intentions of Build-ID changed since the Fedora Feature page was written about it. And people's opinions diverge on what it is now. Maybe in your answer you could include status of Build-ID and what it is now as well?

I think things weren't very precisely formulated. If a tool changes the build that creates the ELF file so that it isn't a "semantically identical" binary anymore then it should get a new (recalculated) build-id. But if a tool changes something about the file that still results in a "semantically identical" binary then the build-id stays the same.

What isn't precisely defined is what "semantically identical binary" means. The intention is that it captures everything that a build was made from. So if the source files used to generate a binary are different then you expect different build-ids, even if the binary code produced might happen to be the same.

This is why when calculating the build-id of a file through a hash algorithm you use not just the (allocated) code sections, but also the debuginfo sections (which will contain references to the source file names).

But if you then for example strip the debuginfo out (and put it into a separate file) then that doesn't change the build-id (the file was still created from the same build).

This is also why, even if you knew the precise hashing algorithm used to calculate the build-id, you might not be able to recalculate the build-id. Because you might be missing some of the original data used in the hashing algorithm to calculate the build-id.

Feel free to share this answer with others.



Also, for people interested in debuginfo (linux performance & tracing, anyone?), he mentioned a couple projects for managing them on Fedora:

answered on Stack Overflow Jan 30, 2017 by xealits • edited Jan 31, 2017 by xealits

ELF, Build-ID, is there a utility to recompute it?


The build ID is not a hash of the program, but rather a unique identifier for the build, and is to be considered just a "unique blob" — at least at some point it used to be defined as a hash of timestamp and absolute file path, but that's not a guarantee of stability either.


ELF, Build-ID, is there a utility to recompute it?


I wonder if there is an easy way to recompute Build ID yourself?

No, there isn't, by design.

The page you linked to itself links to the original description of what build-id is and what it's usable for. That pages says:

But I'd like to specify it explicitly as being a unique identifier good
only for matching, not any kind of checksum that can be verified against 
the contents.

(There are external general means for content verification, and I don't 
think debuginfo association needs to do that.)

Additional complications are: the linker can take any of:


So the build id is not necessarily an sha1 sum to begin with.

answered on Stack Overflow Jan 21, 2017 by Employed Russian

g++ symbol versioning. Set it to GCC_3.0 using version 4 of g++


No. They are mean to be incompatible. You have to use a older version of g++.

Also, the different is at and

answered on Stack Overflow Jun 29, 2009 by J-16 SDiZ

How to disable SIGABRT when debugging Android app?


You can select debug app in Developer Option.

// How long we allow a receiver to run before giving up on it.
static final int BROADCAST_FG_TIMEOUT = 10*1000;
static final int BROADCAST_BG_TIMEOUT = 60*1000;
// How long we wait until we timeout on key dispatching.
static final int KEY_DISPATCHING_TIMEOUT = 5*1000;
// How long we wait until we timeout on key dispatching during instrumentation.

To build and push service module:

make services
adb push $ANDROID_PRODUCT_OUT/system/framework/services.jar system/framework/
adb push $ANDROID_PRODUCT_OUT/system/framework/oat/arm/services.odex system/framework/oat/arm/
[you need reboot] adb reboot or manually reboot
answered on Stack Overflow May 29, 2018 by You Kim

How to disable SIGABRT when debugging Android app?


From Android Studio's debugger window one can select "View breakpoints" (Ctrl+Shift+8) and from there set "Suspend [X]: [O] All" (threads), Android now allows a reasonable amount of time to be spent using the debugger, instead of the previous ~15sec.

answered on Stack Overflow Mar 20, 2018 by Avamander • edited Mar 20, 2018 by Justin

OSAtomicIncrement64Barrier crash on 32-bit devices


It seems that the issue had to do with alignment issues in my data struct.


__attribute__ ((aligned (8)))

to the struct that held the counter fixed the issue.

answered on Stack Overflow Jul 4, 2015 by olynoise

Athena ID Protect v2 Token triggers Select Card dialog on PKCS#11 C_Login


I got answer from my Crypto Dealer of choice (shout out to This is a known limitation of the most recent Athena Middleware Clients and it helps to remove those Smartcards from the framework by deleting the following registry keys:

answered on Super User Jun 7, 2017 by eckes


Leave a comment

(plain text only)


  1. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0