Assistance with SBClient compatibility for newer Windows OS

Hi All!

We have a application (SEMtek developed by Entrinsik) utilizing Universe 11.3 and SB 5.5, with the client being SBC 5.5 (currently).  We've gone through multiple upgrades, however I believe our limit has been reached for UV and SB+ due to some programing limitation in the produce that are no longer being developed.  We've had this running for 15+ years, so all iterations of the supporting software along the line.

We're using SBClient uding the GUI for SB.  We've had no issues with SBC up until newer versions of Windows 10 and similar time frame Server OSs.  In Server 2016, all items the app uses in SBC seem to work fine.  In newer releases of Windows 10 and Server 2019, SBC the main interfaces seem to work fine, but some sub menu items completely crashes and closes out the app without error.  I have ticket in with our VAR Entrinsik and will be digging myself to see if I can find what processes this death clicks are using.  Just thought I'd post here to see if someone has any obvious suggestions.

I have attempted several different terminal types and config setting to no avail, but open to try anything.

Thanks,

Glen

Hey Glen,

We don't have many known issues with SBClient version 5 and OS compatibility in newer Windows OS's.  The most we typically encounter are issues with integration with newer versions of Office, which typically are due to 32-bit vs 64-bit struggles.  

I can suggest you run /CLEAN.SBHSTATE to clear out local GUI definitions and have SBClient re-download them, perhaps the sub menu items just need to be redownloaded to work properly.  

I also suggest you enable some SBClient logging to see if perhaps an error is caught on the terminal but closes too quick to read.  In SBClient go to Help -> Troubleshooting -> Log Options...  Here you can turn on the Terminal Send and Terminal Receive Logs which capture anything sent to/from the terminal.

-Andrew Clay

Hi Andrew,

Thanks for the prompt reply.

/CLEAN.SBHSTATE didn't do anything.  It was a clean install, of SBC so I didn't expect it would.  Enabled logging, but now I need to figure out how to get the logs.  Our VAR setup our new VDI environment and has us locked out of C:\\ so I need to figure that out.  LOL!  I'll update should I find anything.  Thanks for the help!  - G

Hi Andrew,

I have a system that I can recreate the issue every time.  Server 2019.  Here is an excerpt from the working log file.  The one that doesn't work, appears to be identical up until the section I have Bolded and underlined.  That is the next step that crashes SBC.

Nothing seems to be happening differently aside from the command works.  No idea if the below will mean anything to you, assuming it will mean more to you than me.  Thanks - Glen 

RCVE Working:

MA)
4ROOT
47
40
4COURSE
3COURSE
2L049
3BRO
3BRO
2658L23
3FAC
3BDG
3BDG
2658L23-BOS
3ORDER
3ORDER
2355507
3INS
3NL
4ROOT
3COURSE
3ROOT
3BRO
3ROOT
3ROOT
3BDG
3ROOT
3ORDER
3ROOT
3ROOT
4Course
3PHARMACEUTICAL/BIOTECH PATENT LAW
3Brochure
3
3Facility
3Budget
3658L23-BOS Program Budget
3Order
3Order # 355507, Seminar (658L23-BOS)
3Instructor
3Interest Inq
47
37
37
37
37
37
37
37
37
37
37
3_Xÿ _Ua_X_Us43
1SB.HANDLER.60
1gui_status_line
1$progress$
4 _Xÿ _Ua_X_Ui25
1SB.HANDLER.60
1gui_input
1_Xÿ _Ua_X_Us34
1SB.HANDLER.60
1gui_kill_form
13
31
30_Xÿ _Ua_X_Us23
1SB.HANDLER.60
1gui_lfk
1_Xÿ _Ua_X_Us43
1SB.HANDLER.60
1gui_status_line
1$progress$
4 _Xÿ _Ua_Xÿ_Ug31
1SB.HANDLER.60
1gui_disable_form_Xÿ _Ua_X_Us58
1SB.HANDLER.60
1gui_button_bars
18
4MSTB
3MSTB
311526
336340.046_Xÿ _Ua_X_Us124
1SB.HANDLER.60
1gui_disp_formset
13
3Apples_USA_SM_I*BR*BROCH.ENTRY.GUI1
357604
3
3Brochure Maintenance
31
20
3
3
3
3
3Screen 1
3MSTB_MSTB_Xÿ _Ua_Xÿ_f30;0};\\ÿ  _Ua_X_Us59
1SB.HANDLER.60
1gui_set_attr
3@FORM*14*1
1input_flag
2focus
40
21_Xÿ _Ua_X_U3658L23_X_U3658L23_Xÿ_U3ÿ658L23Public SessionL049SUMMIT ON BIOSIMILARS & INNOVATOR BIOLOGICSSUMMIT ON BIOSIMILARS & INNOVATOR BIOLOGICSJOE GALLAGHER    2Shannon Kao27/06/23<none>      BOS_X_U3Public Session_X_Ui40
1SB.HANDLER.60
1gui_input
114
33
40
4L049
41
31_Xÿ

Working SEND log.  Bold section on second line is what gets added for working instance.

MSTB
1
1O
4button_bar;;;;
4110;999;999;MSTB
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 

1
1
4tree_select
4BRO
2658L23
10 
1
11
10 
1
10
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 
1
11
10 
1
10
31
10