Windows error 0x00000510, 1296

Detailed Error Information

CONTENT_BLOCKED[1]

MessageThe requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.
Declared inwinerror.h

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

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.
FlagsSeveritySuccess

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
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][1]
DescriptionThe default facility code.[2][1]
Error Code1296 (0x0510)

Questions

0votes
0answers

Cannot access memory at break point address in GDB

I've already set breakpoint at address 0x000004ed. But why can't I access it even after the code has been ran? (gdb) disassemble main Dump of assembler code for function main: 0x000004ed <+0>: push ebp 0x000004ee <+1>: mov ebp,esp 0x000004f0 <+3>: sub esp,0x10 0x000004f3 <+6>: call 0x512 <__x86.get_pc_thunk.ax> 0x000004f8 <+11>: add [...] read more
c
memory
gdb
0votes
1answer

XMS.NET fails when receiving JMS message with RFH2 header at ParseJmsFolder

Our partner started using custom properties for messages being sent over IBM WebSphere MQ and our application developed using XMS.NET started to fail because of that. It turned out that the error is being thrown inside parsing the JMS envelope and inside the ParseJmsFolder method. This is the exception we [...] read more
.net
jms
ibm-mq
xms
rfh2
0votes
1answer

Bochs: assembly far jump got lost in bogus memory area (invalid opcode error)

I started to develop a small toy operating system in (NASM) assembly, just for my entertainment. I've written a bootloader that loads the first (and only one) file from a FAT12 file system called "kernel.sys" into the memory at offset 0x7E00. In real mode, the kernel only sets the appropriate [...] read more
assembly
x86
kernel
protected-mode
bochs

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0