Skip to Content
avatar image
Former Member

Internal Error - dbsrv11

hi guys, just wondering if anyone encounters such problem before ?

Internam Error - dbsrv11

dbsrv11 has envountered a serious error and needs to close. We are sorry for the inconvenience.

From the crash log i found :

VERSION=11.0.1.2044

FILENAME=C:\Documents and Settings\All Users\Application Data\SQL Anywhere 11\diagnostics\SA11_20140721_103517_9508.crash_log

OS=Windows 2003 Build 3790 Service Pack 2

PROCESSOR=X86_64

EXEC_ARCH=X86

EXEC_PATH=C:\Program Files\SQL Anywhere 11\Bin32\dbsrv11.exe

MODULE_PATH=C:\Program Files\SQL Anywhere 11\Bin32\dbserv11.dll

EXCEPTION_PTR=0F07CB60

EXCEPTION_CODE=2147483651

EXCEPTION_FLAGS=0

EXCEPTION_RECORD=00000000

EXCEPTION_ADDRESS=77E4BEF7

EXCEPTION_NumParameters=1

EXCEPTION_Param0=0084036C

TRYING_TO_SAVE_MINI_DUMP C:\Documents and Settings\All Users\Application Data\SQL Anywhere 11\diagnostics\SA11_20140721_103517_9508.dmp

DUMPLEVEL 0

SAVING_MINI_DUMP_COMPLETED

CRASH_LOG_COMPLETE

ATTEMPTING_TO_SUBMIT_MINIDUMP...

From another err.xml, there are more encrypted messages here (so, i guess i will not post here in case if it is needed)

The platform of this OS :

product="SQL Anywhere"

application_version_build="2044"

system_properties="Windows 2003 Build 3790 Service Pack 2"

Anyone had such problem before ? Need to know if the root cause is from the OS platform or the software side itself 😊

thank you

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 21, 2014 at 05:55 PM

    Can you reproduce this problem regularly?  If so, you might consider opening a support case to diagnose the problem further.

    Also, you should apply the latest SQLA 11.0.1 ebf to ensure you have all fixes that may apply to this scenario.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jason Hinsperger,

      I have checked from the machine's event viewer and unable to find anything related to SQLANYWHERE log.

      More important, we are unable to reproduce such scenario that leads to the dbsrv11 crashed too.

      At the moment, our client is using this older version and we wont be in the right position to advise them to get an updates of this 😔