Problem with access violation

K

knoble

New Member
Due to a recent hard drive crash, I have a new laptop on which I have loaded Progress 10b with SP5. I have created and loaded my databases successfully, but when I try to do a compile, add directories to the propath, access ProTools, etc., my session bombs with the message "prowin32.exe has generated errors and will be closed by Windows". With the compile, it actually compiles about 15 programs before it quits.

Here is the information from the protrace file:

//=====================================================
PROGRESS stack trace as of Fri Feb 23 10:43:16 2007
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 0027A9AD 01:000499AD C:\progress\OpenEdge\bin\snbd12dm.dll
Registers:
EAX:00000000
EBX:00000000
ECX:00000000
EDX:4F740000
ESI:00017B48
EDI:00000000
CS:EIP:001B:0027A9AD
SS:ESP:0023:0012ED2C EBP:0012EEA0
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010212
Call Stack:
Address Frame
0027A9AD 0012EEA0 0001:000499AD C:\progress\OpenEdge\bin\snbd12dm.dll
1034D982 02B2BE18 0001:0034C982 C:\progress\OpenEdge\bin\prow32.dll
6F72645F 2F637465 0000:00000000
//=====================================================
PROGRESS stack trace as of Fri Feb 23 10:43:48 2007
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 0027A9AD 01:000499AD C:\progress\OpenEdge\bin\snbd12dm.dll
Registers:
EAX:00000000
EBX:00000000
ECX:00000000
EDX:4F740000
ESI:00017B48
EDI:00000000
CS:EIP:001B:0027A9AD
SS:ESP:0023:0012ED2C EBP:0012EEA0
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010212
Call Stack:
Address Frame
0027A9AD 0012EEA0 0001:000499AD C:\progress\OpenEdge\bin\snbd12dm.dll
1034D982 02B2BE18 0001:0034C982 C:\progress\OpenEdge\bin\prow32.dll
6F72645F 2F637465 0000:00000000

I have been unable to find any information in the Progress Knowledgebase which addresses this problem. Prior to the crash of my old hard drive, I had the same database structure, etc. and did not receive this error.

Does anyone have any idea of what might be causing this?

Thanks
Kathy Noble
 
knoble,
might be a long shot but check your permissions on the folders / files involved.
especially the areas that are used when it reaches the magical '15' or so and quits.
regards,
longhair
 
I appreciate the suggestion. Unfortunately (for solving the problem, anyway), I have full permissions to the applicable files and folders.

Thanks anyway.

Any other suggestions? Does anyone know what the snbd12dm.dll is for?
 
You must log in or register to reply here.
Back
Top