"OSVBlockAddr: Bad VBlock Handle" selecting database properties on deleted database in Domino Admin client

Technote (troubleshooting)


Problem

The following Red Box crash occurs when you select the Database Properties on a deleted database in the Domino® Administration client:

Sorry, an uncorrectable error has occurred.
OSVBlockAddr: Bad

Symptom

The Fatal thread on Notes 8.0.1 is as follows:

##################################################
### thread 1/27: [ nlnotes: 0b3c: 0248] FATAL THREAD (Panic)
### FP=0013d094, PC=7c90eb94, SP=0013d030
### stkbase=00140000, total stksize=212992, used stksize=12240
### EAX=0xffffffff, EBX=0x7c801e16, ECX=0x00000000, EDX=0x00280608
### ESI=0x000006a8, EDI=0x00000000, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00000297
##################################################
[ 1] 0x7c90eb94 ntdll.KiFastSystemCallRet+0 (6a8,493e0,0,13d614)
[ 2] 0x7c802532 kernel32.WaitForSingleObject+18 (6a8,493e0,3,13d830)
@[ 3] 0x601a5704 nNOTES.OSRunExternalScript@8+1284 (12c,1)
@[ 4] 0x601a5b9a nNOTES.FRTerminateWindowsResources+986 (1,0,1010,1)
@[ 5] 0x601a5f5f nNOTES.OSFaultCleanupExt@24+895 (f84dd8,1010,0,0,0,13db60)
@[ 6] 0x601a5fea nNOTES.OSFaultCleanup@12+26 (0,1010,0)
@[ 7] 0x601b1254 nNOTES.OSNTUnhandledExceptionFilter@4+276 (13eb98)
@[ 8] 0x6017ac78 nNOTES.Panic@4+520 (13ebb8)
@[ 9] 0x6000426f nNOTES.OSVBlockAddr@8+111 (6224c1c0,ffff)
@[10] 0x61b805e3 nnotesws.CDatabaseSelection::Property+67 (96f6014,13ecb0,3,13ecb0)
@[11] 0x61801cff nnotesws.CSelectableObject::PropertyWithUndo+79 (96f6014,13ecb0,0,1)
@[12] 0x6180063b nnotesws.CSelectionManager::Property+219 (1dfc014,13ecb0,3,1)
@[13] 0x61800adf nnotesws.CSelectionManager::IBtoApp+847 (0,8,13ed04,13ed58)
@[14] 0x61800ec7 nnotesws.InfoBoxToApp@12+23 (61680000,8,13ed04)
@[15] 0x0bc52999 ninfobox.IBEdit::IBEdit+217 (13ee0c,4002,0,13ee7c)
@[16] 0x0bc32dc5 ninfobox.IBEditText::IBEditText+21 (13ee0c,4002,0,ab0e9ec)
@[17] 0x0bc46e49 ninfobox.PCMakeItem+3961 (113ee7c,ab0e994,ab0e9ec,61680000)
@[18] 0x0bc48025 ninfobox.ReadControlPCODE+309 (6290ea85,ab0e994,61680000,ab0e9e8)
@[19] 0x0bc3392c ninfobox.PageView::PageView+236 (6290ea00,a01,61680000,61680000)
@[20] 0x0bc41886 ninfobox.SettingsView::SetPage+390 (1,1,a986a14,0)
@[21] 0x0bc42707 ninfobox.SettingsView::SelChanged+1559 (1,0,1dfc014,0)
@[22] 0x0bc3ca10 ninfobox.ApptoIB@8+1056 (2,0)
@[23] 0x616e0318 nnotesws.CSelectionManager::SelectionChanged+1352 (1,0,0,1dfc020)
@[24] 0x617d0c04 nnotesws.NEMShowInfoBox@0+52 ()
@[25] 0x617d124d nnotesws.ProcessWMCommand@8+173 (40060001,0)
@[26] 0x61683eca nnotesws.MainWndProc@16+4234 (206ce,111,40060001,0)
[27] 0x7e418734 USER32.GetDC+109 (61682e40,206ce,111,40060001)
[28] 0x7e418816 USER32.GetDC+335 (0,61682e40,206ce,111)
[29] 0x7e4189cd USER32.GetWindowLongW+295 (13f7b4,0,13f7d4,6171a0b6)
[30] 0x7e418a10 USER32.DispatchMessageW+15 (13f7b4,1,206ce,61680000)
@[31] 0x6171a0b6 nnotesws.NEMMainLoop@4+742 (4013d0)
@[32] 0x0040197b nlnotes.WinMain@16+1451 (617595a0,0,172340,0)
@[33] 0x00401e39 nlnotes.WinMainCRTStartup+389 (655d4,7c90ee18,7ffde000,8054a6ed)
[34] 0x7c816fd7 kernel32.RegisterWaitForInputIdle+73 (401cb4,0,78746341,20)


Crash Thread:

##################################################
### FATAL THREAD 1/8 [ NLNOTES:0c98: 3400]
### FP=0x0013ecfc, PC=0x6018eb23, SP=0x0013e384, stksize=2424
### EAX=0x0156088c, EBX=0x00000000, ECX=0x010b0000, EDX=0x010b0000
### ESI=0x0013ed14, EDI=0x80f47cac, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010202
Exception code: c0000005 (ACCESS_VIOLATION)
##################################################
@[ 1] 0x6018eb23 nnotes._Panic@4+483 (130016,57980f4,57980f4,109a)
@[ 2] 0x60004072 nnotes._OSVBlockAddr@8+114 (61bf6cf0,7cacffff,57980f4,13edfc)
@[ 3] 0x61567974 nnotesws.CDatabaseSelection::Property+52 (57980f4,13edfc,3,13edfc)
@[ 4] 0x611e8c5f nnotesws.CSelectableObject::PropertyWithUndo+79 (57980f4,13edfc,0,1)
@[ 5] 0x611e8003 nnotesws.CSelectionManager::Property+211 (1870814,13edfc,3,1)
@[ 6] 0x611e7975 nnotesws.CSelectionManager::IBtoApp+725 (1870814,8,13ee54,13eea8)
@[ 7] 0x611e6f27 nnotesws._InfoBoxToApp@12+23 (61180000,8,13ee54,61f59841)

@[ 8] 0x06851a72 ninfobox.IBEdit::IBEdit+226 (13ef70,4002,61f59841,13efd4)
@[ 9] 0x06832c65 ninfobox.IBEditText::IBEditText+21 (13ef70,4002,0,5ab944c)
@[10] 0x06846ea1 ninfobox.PCMakeItem+4177 (8713efd4,5ab93f4,5ab944c,61180000)
@[11] 0x06845b2c ninfobox.ReadControlPCODE+140 (61f59845,5ab93f4,61180000,5ab9448)
@[12] 0x0683382e ninfobox.PageView::PageView+238 (61f597c0,a01,61180000,61180000)
@[13] 0x06841f09 ninfobox.SettingsView::SetPage+441 (1,1,42deef4,0)
@[14] 0x06841c44 ninfobox.SettingsView::SelChanged+1524 (1,0,1870814,0)
@[15] 0x0683c8f4 ninfobox._ApptoIB@8+1092 (2,0,1870820,0)
@[16] 0x61191505 nnotesws.CSelectionManager::SelectionChanged+917 (1,0,0,61191045)
@[17] 0x61190510 nnotesws._NEMShowInfoBox@0+48 (1870814,40060001,0,0)
@[18] 0x6119099e nnotesws._ProcessWMCommand@8+174 (40060001,0,13f6e8,611b0160)
@[19] 0x611b122c nnotesws._MainWndProc@16+4300 (b00f6,111,40060001,0)
[20] 0x77d67ad7 USER32 (611b0160,b00f6,111,40060001)
[21] 0x77d6ccd4 USER32 (0,611b0160,b00f6,111)
[22] 0x77d44455 USER32 (13f7c0,0,611960d3,13f7c0)

 [23] 0x77d495d5 USER32 (401000,14,15235c,0)
@[24] 0x0040156d NLNOTES._WinMain@16+1389 (400000,0,15235c,1)
@[25] 0x00401dfa NLNOTES._WinMainCRTStartup+308 (14,1,7ffdf000,2e0053)
[26] 0x77e814c7 KERNEL32 (401cc6,0,78746341,20)



Cause

The crash does not occur in cases in which the Notes Client was not previously opened.

Diagnosing the problem

Steps to reproduce:


1. Start the Notes Client.

2. Start the Admin Client and open a database with a double-click.

3. In the Notes menu, select File > Database > Delete Database.

4. Message displays that the file is currently open and will be deleted later; select OK.

5. Press Escape to delete the database.

6. Switch back to Administrator; do not refresh (F9) the view. Double-click on the database name. You will get the error "File does not exist: <filename.nsf>". (Note: In some cases the issue will recreate when you execute the above step.)

7. Right-click on the same database to see the properties; the client crashes with the above red box error.

Resolving the problem

This crash is under investigation by Quality Engineering as SPR #GFLY5U4QAT.


Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Domino
Crash

Software version:

6.0, 6.5, 8.0.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, i5/OS, z/OS

Reference #:

1156598

Modified date:

2009-10-26

Translate my page

Machine Translation

Content navigation