Hi Guys,
Hoping someone may be able to help point me in the right direction to overcome my issue. Using a modified version of the web datawindow com object "pbdwr110.dll" on a web server. Calling the object from cshtml to create forms/reports etc.
This has been working great until recently a client upgraded to windows 2019 server. The com object seems to install fine through component services however getting lots of random COMException when using it.
These 2 entries seems to be reoccurring quite often in the event log.
Faulting application path: C:\Windows\SysWOW64\dllhost.exe
Faulting module path: C:\mypathsysfolder\PBVM110.DLL
Faulting application path: C:\Windows\SysWOW64\dllhost.exe
Faulting module path: C:\mypathsysfolder\PBSHR110.dll
Any suggestions on how to track down further as event log gives no help on reason for crash?
Thanks Michael
Yes, the Web DW was really "Kool" and so was Distributed PB. I helped build an all "web" based application system at Agriculture Canada using both of those features. It had 4 DPB servers that could each handle 1,000 *concurrent* web sessions. There were 10K users on the system at multiple peak periods of the day. The DPB servers never faulted - pushing 800 peak concurrent DB threads each over to an Oracle DBMS. We even wrote our own round-robin load balancing for web session handling. All the report viewing was done via the Web DW & pure HTML generated by DPB NVUO's & HTML based DWO's housed in DataStores.
Yes, Sybase (John Strano) demoed the HTML5 DW at my Ottawa PB User group circa PB 12.5 => PB 15. However, SAP forced Sybase into stripping the features down in PB15 and releasing it as PB12.6. Unfortunately, the HTML5 DW was a casualty.
For web based PDF generation the Web DW was very effective. You can still build PB Web based Apps & do Web based PDF generation using Roland's product ...
http://www.topwizprogramming.com/topwizweb.html
The PBSHR DLL is mainly PB's runtime module for interfacing the runtime "C" calls over to the various MS-Windows API's.
Regards ... Chris
Good news is the comexceptions have stopped, I think the "local service" account didn't have sufficient rights to do what was needed.
My webdatawindow will live on for a little longer!
Don't forget to hug a DW today! ;-)