Re: Upgrade Issues

I have tried tihe 7.4.3.17 websql.dll but the same thing happens.  The 
only difference is the memory address that the program is trying to 
write to (0x012e022a).  I would be willing to try a debug dll and send a 
trace.

Thanks,
Mark

Auer, Wolfgang wrote:

> Hi Mark,
>  
> as a work around you could try to replace the websql.dll from 7.4.3.27 
> with the dll from 7.4.3.17. If this does not work I would like to send 
> you  a debug version of the dll which will write a trace file.
>  
> Regards
> Wolfgang
>  
> -----Original Message-----
> From: Mark Johnson [mailto:[email protected]]
> Sent: Dienstag, 2. September 2003 23:06
> To: [email protected]
> Subject: Upgrade Issues
>
> After upgrading SAPDB from 7.4.03.17 to 7.4.03.27, websql no longer 
> works.  The log file contains the following (this is on Win2K, SP4)
>
>[2003/04/11 15:10:02] Scanning ini-file: Success
>[2003/04/11 16:30:23] WebAgent exiting  --  Good Bye
>[2003/07/21 15:37:15] Scanning ini-file: Success
>[2003/07/28 17:02:10] Scanning ini-file: Success
>[2003/07/31 14:17:57] WebAgent exiting  --  Good Bye
>[2003/08/04 14:05:56] Scanning ini-file: Success
>[2003/08/13 17:17:22] Scanning ini-file: Success
>[2003/09/02 15:25:17] Scanning ini-file: Success
>[2003/09/02 15:26:49] Fatal exception in Service function of websql: Unhandled exception..
>[2003/09/02 15:26:49] The service websql is disabled now.
>[2003/09/02 15:26:49] The service-function in user-dll websql throwed an exception.
>[2003/09/02 15:32:18] Scanning ini-file: Success
>[2003/09/02 15:38:36] WAHTTP_WebAgent.c: sapw3_as->SendHeader failed.
>
>
> You cannot get to http://localhost:85/websql.  Also note that I 
> upgraded my existing database/software (SDBINST found the existing 
> database and I selected the upgrade option).
>
> Then I upgraded the web tools (to version 7.4.03.25), which changes 
> the port number to 9999.  I changed this back to 85, and started the 
> services.  When I log into websql, wahttp.exe aborts with the error 
> message:
>
> The instruction at "0x1f7e0949" referenced memory at "0x00fe022a".  
> The memory could not be "written".
>
> webdbm appears to operate correctly.
>
> Here is a partial listing from the httperr.log file:
>
> [02/Sep/2003:15:48:57]: Starting ErrLog (build 
> 123-046-179)[WAHTTP_Log.c: 205]
> [02/Sep/2003:15:48:57]: Listening on IP  on port 85[WAHTTP_Server.c: 1181]
> [02/Sep/2003:15:48:58]: DocumentRoot is: 
> e:\netvoyant\sapdb\indep_prog\web\Documents[WAHTTP_FileAgent.c: 143]
> [02/Sep/2003:15:48:58]: Init: Initialized[WAHTTP_Server.c: 1203]
> [02/Sep/2003:15:48:58]: Init: starting Web Server[WAHTTP_Server.c: 1353]
> [02/Sep/2003:15:48:58]: starting service loop[WAHTTP_Server.c: 958]
> [02/Sep/2003:15:49:42]: EXECPTION OCCURED:[WAHTTP_Log.c: 479]
> SymbolSearchPath:  
> C:\WINNT\system32;e:\netvoyant\sapdb\indep_prog\web\pgm;C:\WINNT
> ----> Register Dump <----
>   Eax=0x00000047 Ebx=0x00002000 Ecx=0x00fdc22c Edx=0x7ffb001c 
> Esi=0x00fd9a88 Edi=0x00000047
>   Eip=0x1f7e0949 Esp=0x00fd9a18 Ebp=0x00fd9a34
>   Cs=0x001b  Ss=0x0023  Ds=0x0023  Es=0x0023  Fs=0x0038  Gs=0x0000  
> Efl=0x10202
> ----> Module List <----
> |.text Start |.text End   | Module File Name
> | 0x00400000 | 0x004b7000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\wahttp.exe
> | 0x006c0000 | 0x006d6000 | C:\WINNT\system32\odbcint.dll
> | 0x00b40000 | 0x00b45000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\waecho.dll
> | 0x00b60000 | 0x00bf0000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\wdvhandler.dll
> | 0x00bf0000 | 0x00c51000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\WDVCAPI.dll
> | 0x00c90000 | 0x00d2b000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\webdbm.dll
> | 0x00d40000 | 0x00d82000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\websql.dll
> | 0x00d90000 | 0x00dbc000 | 
> e:\netvoyant\sapdb\indep_prog\web\pgm\DBFSAPI.dll
> | 0x018e0000 | 0x0197c000 | e:\netvoyant\sapdb\indep_prog\pgm\sqlod32.dll
> | 0x10000000 | 0x100da000 | e:\netvoyant\sapdb\indep_prog\web\pgm\WAPI.dll
> | 0x1f7d0000 | 0x1f804000 | C:\WINNT\system32\ODBC32.dll
> | 0x70bd0000 | 0x70c1c000 | C:\WINNT\system32\SHLWAPI.dll
> | 0x71700000 | 0x7178a000 | C:\WINNT\system32\COMCTL32.DLL
> | 0x72a00000 | 0x72a2d000 | C:\WINNT\system32\dbghelp.dll
> | 0x74fd0000 | 0x74fee000 | C:\WINNT\system32\msafd.dll
> | 0x75010000 | 0x75017000 | C:\WINNT\System32\wshtcpip.dll
> | 0x75020000 | 0x75028000 | C:\WINNT\system32\WS2HELP.DLL
> | 0x75030000 | 0x75044000 | C:\WINNT\system32\WS2_32.DLL
> | 0x75050000 | 0x75058000 | C:\WINNT\system32\WSOCK32.dll
> | 0x76000000 | 0x7600d000 | e:\netvoyant\sapdb\indep_prog\pgm\sqltcp.dll
> | 0x76010000 | 0x76076000 | 
> e:\netvoyant\sapdb\indep_prog\pgm\SqlUser74.dll
> | 0x76b30000 | 0x76b6e000 | C:\WINNT\system32\comdlg32.dll
> | 0x77920000 | 0x77943000 | C:\WINNT\system32\imagehlp.dll
> | 0x77a50000 | 0x77b3c000 | C:\WINNT\system32\ole32.dll
> | 0x77d30000 | 0x77d9e000 | C:\WINNT\system32\RPCRT4.DLL
> | 0x77e10000 | 0x77e75000 | C:\WINNT\system32\USER32.dll
> | 0x77f40000 | 0x77f7c000 | C:\WINNT\system32\GDI32.DLL
> | 0x77f80000 | 0x77ffb000 | C:\WINNT\system32\ntdll.dll
> | 0x78000000 | 0x78045000 | C:\WINNT\system32\MSVCRT.DLL
> | 0x782f0000 | 0x78538000 | C:\WINNT\system32\SHELL32.DLL
> | 0x7c000000 | 0x7c054000 | C:\WINNT\system32\MSVCR70.dll
> | 0x7c2d0000 | 0x7c332000 | C:\WINNT\system32\ADVAPI32.DLL
> | 0x7c4e0000 | 0x7c599000 | C:\WINNT\system32\KERNEL32.DLL
>
> The webslw.log file doesn't seem to have anything but a startup message.
>
> Also, is there a prescribed procedure for restarting a database after 
> a software upgrade?  It seems that I cannot just start the NT/Win2K 
> database service (it won't start), but need to start the database via 
> the command line (dbmcli) or by using webdbm.  Does this procedure 
> upgrade system tables or do something else under the covers the first 
> time the database is started?
>
> Thanks in advance for any help,
> Mark Johnson
>
>
>
>
>
>
>
>