Walter.Koller
Level 12
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
16-03-21
10:32 AM
Status:
New
Now in times when remote working became more common, the network code of BP should be stable and should handle errors.
When switching networks, going into suspend/wake up, it can happen BP gets out of sync and an indefinite number of error messages are displayed with the only option to force kill the BP process in task manager.
When working via VPN with limited bandwidth BP may run out of sync when refreshing Control view or even when logging into BP.
After this error, .Net connection is in 'faulted state' that might need computer restart to resolve
This happened in 6.4. I know there have been some improvements done in later versions.
When switching networks, going into suspend/wake up, it can happen BP gets out of sync and an indefinite number of error messages are displayed with the only option to force kill the BP process in task manager.
When working via VPN with limited bandwidth BP may run out of sync when refreshing Control view or even when logging into BP.
After this error, .Net connection is in 'faulted state' that might need computer restart to resolve
This happened in 6.4. I know there have been some improvements done in later versions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
