Bartender 2021 on Windows 10 Crashes 追蹤

0
Avatar
Rod Bolt

I've just installed Bartender 2021 onto a clients Windows 10 unit, they had some files from their 2016 version which I had to adjust and re-connect the database. It was ok to open up all 25 files at once with no issue, but when I left for lunch and came back and went to open up each file individually it would load the files and I'd get Windows 10 circle cursor of death and the program would crash, I would then try and open up the file again and the same thing would happen. I then would try one of their other files and same thing. But then for some reason on the 4 or 5 try the file would open and then had no issues opening up other files. I thought that was strange. I then closed everything, waited about 2 minutes and had the exact same crashing issue again. I tried opening up the software without a file and it opened up first time.

Not all the files use databases or have any filters, but when opening up from a file it seems to crash for a few times and then opens.

Any ideas?

10 意見

0
Avatar
Tony Ross
評論操作 永久連結

I am getting the same issue.  I have been using the 2021 software for about 2 months.  Was opening files and printing from the files yesterday 3/12/21 and now today I can not open any file without the program crashing my entire computer.

0
Avatar
Pete Thane
評論操作 永久連結

It sounds like your problem Tony maybe connected to the latest Windows update. Microsoft have stopped the rollout st it is effecting a lot of different software products that use printer drivers. I would suggest you check out this and uninstall the update.

I hope this helps

https://support.seagullscientific.com/hc/en-us/articles/1500003505421-Printing-causes-a-Blue-Screen-BSOD-error-APC-INDEX-MISMATCH-for-win32kfull-sys-following-a-Windows-10-update 

0
Avatar
Rod Bolt
評論操作 永久連結

That is a next level to mine, I just get Bartender crashing and not the whole computer.

0
Avatar
Rod Bolt
評論操作 永久連結

Thanks Pete for helping Tony out but any idea why Bartender would crash on Windows 10 when just opening files? I've got both new installs and upgrades now having the same issues and one of my clients has 3 different computers running Bartender Professional and it is crashing on all 3 computers upon just opening a file, they get the Microsoft spinning blue circle and then it crashes. One of my other clients has to attempt to open up their files like 6 times before a file will stay stable enough to stay open.

0
Avatar
Pete Thane
評論操作 永久連結

Yes your problem started before this latest Windows update and it is something I would suggest, if you haven't already done so, that you raise directly with your regional Seagull Tech Support team to help diagnose

0
Avatar
Tony Ross
評論操作 永久連結

Uninstall Windows Update KB5000802

Open Settings > Update & Security > Windows Update.Click on ‘View Update History’Click on ‘Uninstall updates’ link.Locate the update (KB5000802) and click on ‘Uninstall’.

 

I did this and got my system back up and running.

 

0
Avatar
Pete Thane
評論操作 永久連結

Glad your is back up and running, Tony. 

Mine seemed to be working correctly until I selected a ZDesigner driver (that I have installed only for support purposes) and then I got the blue screen too. The Seagull drivers didnt trigger this so there seems to be some differing results depending on the individual PC and install.

 

Ross,

As suggested above I would suggest you approach your regional Seagull Tech Support team for help as your fault pre-dates last weeks update issue. 

What you could try is look at permissions for the printer drivers etc, make sure all the Services are running (you can do this via Administration Console and the Windows Services section)  and try opening BarTender Designer from the Windows Start button program group and then creata a brand new label just with say a default 12345678 barcode or "Sample Text" text field and save that locally on the the PC and then close and open BarTender and then open the label and see if that works.

I did have an issue with 2019 I think it was on a customer's site that if they double clicked on a label format in a network folder to open BarTender and the label then this caused a crash, but if they opened BarTender and then the label then this worked. I never got to the bottom of why this was happening but just said that was the way to do it. In fact I think I got them to use Print Station as then they had to open the files in that way and everything was fine after that. 

 Not mush help I know, but maybe worth a try or else speak to Seagull Tech.

Pete

0
Avatar
Alexey Emelyanov
評論操作 永久連結

Hi. We are updating BarTender from 10.1 to 2021. The Designer crashes on starting when try create a new label. When I press 'Finish' on 'New Document Wizard'.

Administration Console works and I was able to configure license server.

Windows Update (KB5000802) is not installed.

Logs from Event Viewer\windows logs\application:

Faulting application name: BarTend.exe, version: 11.2.166.48, time stamp: 0x605e615f
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xe06d7363
Fault offset: 0x0000000000034b89
Faulting process id: 0x4154
Faulting application start time: 0x01d75787da045982
Faulting application path: C:\Program Files\Seagull\BarTender 2021\BarTend.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: f7d0a749-a471-44e6-9219-e28c498e3dbf
Faulting package full name:
Faulting package-relative application ID:

 

Application: BarTend.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
at <Module>.wWinMainCRTStartup()

From BtMag.txt:

2021-06-02 12:51:13 6668 Error Miscellaneous OK BarTender Image Dump: Exception UNKNOWN EXCEPTION CODE 0xE06D7363 occurred at address 0x00007FFC9CF94B89 inside module C:\WINDOWS\System32\KERNELBASE.dll loaded with base address 0x00007FFC9CF60000. (x64 PID:9288) 0: 00000001407DF828 MethodBase:0000000000000000 ! 1: 00000001407E036D MethodBase:0000000000000000 ! 2: 00000001407E0813 MethodBase:0000000000000000 ! 3: 00007FFC9D06B887 MethodBase:00007FFC9D06B6A0 KERNELBASE.dll!UnhandledExceptionFilter 4: 00007FFC9F895270 MethodBase:00007FFC9F893EC0 ntdll.dll!memset 5: 00007FFC9F87C776 MethodBase:00007FFC9F87C6E0 ntdll.dll!_C_specific_handler 6: 00007FFC9F89217F MethodBase:00007FFC9F892060 ntdll.dll!_chkstk 7: 00007FFC9F841454 MethodBase:00007FFC9F841020 ntdll.dll!RtlRaiseException 8: 00007FFC9F8411A5 MethodBase:00007FFC9F841020 ntdll.dll!RtlRaiseException 9: 00007FFC9CF94B89 MethodBase:00007FFC9CF94B20 KERNELBASE.dll!RaiseException 10: 00007FFC8F466210 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 11: 00000001402A4A42 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 12: 0000000140074180 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 13: 00007FFC6959C1A4 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 14: 00007FFC695EE072 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 15: 00007FFC8F451080 MethodBase:00007FFC8F466180 VCRUNTIME140.dll!CxxThrowException 16: 00007FFC8F4526B5 MethodBase:00007FFC8F451150 VCRUNTIME140_1.dll!_NLG_Return2 17: 00007FFC9F891506 MethodBase:00007FFC9F891060 ntdll.dll!RtlCaptureContext2 18: 00007FFC695B3453 MethodBase:00007FFC9F891060 ntdll.dll!RtlCaptureContext2 19: 00007FFC695B3824 MethodBase:00007FFC9F891060 ntdll.dll!RtlCaptureContext2 20: 00007FFC69458CC9 MethodBase:00007FFC9F891060 ntdll.dll!RtlCaptureContext2 21: 00007FFC9E0FE858 MethodBase:00007FFC9E0FE460 USER32.dll!CallWindowProcW 22: 00007FFC9E0FE299 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW 23: 00007FFC6959C0F2 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW 24: 00007FFC6959C9F5 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW 25: 00007FFC695CF580 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW 26: 000000014090D6D6 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW 27: 00007FFC24A9C668 MethodBase:00007FFC9E0FE040 USER32.dll!DispatchMessageW
2021-06-02 12:51:14 6668 Error Miscellaneous OK BarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_009288_0000.dmp'

0
Avatar
Pete Thane
評論操作 永久連結

Hi Alexay,

If the Windows update is not installed then it sounds like you a different issue and I would suggest contacting Seagulls Tech Support team directly to try and resolve it. 

Pete

0
Avatar
Al Perez
版主
評論操作 永久連結

Hi Alexay, thanks for reaching out to us. Unfortunately, the dump files can't be read by the Technical Support team - instead, I would check your Administration Console app and under the System Database properties, run the System Database Wizard option.

While your database connection may look like it's possibly ok, only by running the Wizard will you know if your logged-on user account has permission to administer the System database. If you do not have permission to administer it, this also has the potential of causing crashes. In fact, this may be a better first step before we look into other causes.

For more on configuring permissions, please see our article, https://support.seagullscientific.com/hc/en-us/articles/204791668-Configuring-permissions-to-a-System-Database-Video-5-45- .

If you continue to have issues, consider opening a ticket with Technical Support for further review!

登入寫評論。