SHOPSTREAM EXTENSIBLE FRAMEWORK HAS STOPPED WORKING

[GUTHTIRE]

We've been experiencing the "Shopstream Extensible Framework has stopped working" message intermittently for some time now. This crashes TeamWork SE. After reviewing the Windows Event log the error is associated with OC30.DLL. We've encountered the error on multiple PC's and have yet to come up with a testcase to recreate the error. The crashes occur multiple times a day.

We are running Windows 10 (with the latest Microsoft updates) on HP Touchscreen PCs.

Disabling Touchscreen seems to be a valid work-around for the problem. We have tested for over a week with no crashes! We then re-enabled Touchscreen and the crashes occurred again within a day.
Note: We don't use Touch Screen so disabling this functionality has no bearing on our operations.

Here's how to disable Touchscreen:
Device Manger -> HID -> right click HID - Compliant Touch Screen

[GUTHTIRE]

We've been experiencing the "Shopstream Extensible Framework has stopped working" message intermittently for some time now. This crashes TeamWork SE. After reviewing the Windows Event log the error is associated with OC30.DLL. We've encountered the error on multiple PC's and have yet to come up with a testcase to recreate the error. The crashes occur multiple times a day.

We are running Windows 10 (with the latest Microsoft updates) on HP Touchscreen PCs.

Disabling Touchscreen seems to be a valid work-around for the problem. We have tested for over a week with no crashes! We then re-enabled Touchscreen and the crashes occurred again within a day.
Note: We don't use Touch Screen so disabling this functionality has no bearing on our operations.

Here's how to disable Touchscreen:
Device Manger -> HID -> right click HID - Compliant Touch Screen

Forgot to add:
Device Manger -> HID -> right click HID - Compliant Touch Screen then click Disable

[Sauvageaus]

We have Windows 7 and have been noticing it to happen more then before. Also have 7.07 version of SE

[Silky7]

Thanks for the information. We've associated this error typically to the using the spell check component. We plan on replacing the core of that piece in the near future.

[Sauvageaus]

Thanks for the information. We've associated this error typically to the using the spell check component. We plan on replacing the core of that piece in the near future.

This is what happens to me, I'm not sure if it's only when I open FirstCall or just in general

[Silky7]

That is a different issue. See this thread for more information. http://www.managerforum.net/viewtopic.php?f=208&t=11785

[DynaBMan]

I have seen problems with the Framework stopping in the past. We have one host and two workstations. We recently had problems with our network wireless connection going down and almost every time we received the error message about Framework, it would be when the connection had gone down. We have replaced the wireless network with a more powerful and stable "business class" version and the error messages seemed to have stopped.

[ricmorin]

I have seen problems with the Framework stopping in the past. We have one host and two workstations. We recently had problems with our network wireless connection going down and almost every time we received the error message about Framework, it would be when the connection had gone down. We have replaced the wireless network with a more powerful and stable "business class" version and the error messages seemed to have stopped.

If you don't mind me asking, what did you use?

I have 2 wireless nodes here, one in the office that's part of the router and one in the shop that's simply an access point. The access point is constantly locking up and in need of rebooting.

[DynaBMan]

I have seen problems with the Framework stopping in the past. We have one host and two workstations. We recently had problems with our network wireless connection going down and almost every time we received the error message about Framework, it would be when the connection had gone down. We have replaced the wireless network with a more powerful and stable "business class" version and the error messages seemed to have stopped.

If you don't mind me asking, what did you use?

I have 2 wireless nodes here, one in the office that's part of the router and one in the shop that's simply an access point. The access point is constantly locking up and in need of rebooting.

We had a network guy come in and install the new system. The router is an ARRIS and we have a booster in the shop itself.

[ricmorin]

Thank you. I'll look into that brand.

[Sauvageaus]

I am not able to load Mitchell1 SE now, when I load the program all that happens is this:

[mastertechauto]

We had the same issue first thing this morning but eventually was able to get up and running. Not sure if it was something on our end or at Mitchell.

[ricmorin]

I had that issue on several workstations yesterday. A restart on the affected workstation returned normal operation. Not sure on the cause.

[motley06]

Same here. Came in early morning, went to open Mitchell, error message came up, closed and restarted, no further issues.

[brianp87]

I restarted twice with no change mine only started working when I opened it with the modem unplugged.

[ricmorin]

Looks like there was some licensing issues on M1's end.

[timbre4]

There was an issue on our side; we apologize for the inconvenience.

[localheroes]

We have been having the same problem since updating to 7.0.7. with Framework and lice4nsing issues. Also printer issues and revision graphic issues. We have 2 shops, same problems at each shop since 7.0.7. I know Mitchell pushed this out to address security issues, but it appears it was not well tested. Mitchell needs to release a more stable update. its now starting to get very frustrating.

[timbre4]

We apologize for any inconvenience.

The work for SE 7.0.5 was tested and confidence was good, having already distributed it to some users as 7.0.5 before the security issue hit. The only rushed part was the security aspect fixes which was added to this previous work (7.0.5) and had to be given a new update version number, 7.0.7. Without going into too much detail, SE releases from this point will work more efficiently under the hood.

Besides the security issue, the O'Reilly First Call catalog and our recent M1 server mishap caused much of the Extensible Framework issues reported here. These are wholly separate issues from the 7.0.7 software update.
Please work with support on resolving these specific issues as they are beyond the scope of the forum.

[Rich]

I am still running the "old school" 6.6.10. I have had zero issues. I can see some folks are frustrated with some recent issues. I can understand. but I am also sure that some where in the Mitchell office there are a group of large IQ'd people, eyes are sagging, hands are shaking, over dosing on coffee, stomachs darn near empty, as they bust their rear end to figure out the issue, and get it fixed.

One thing I will NEVER doubt is Mitchells goals to keep this system rockin and rollin and all of us beyond happy.