This question is locked. New answers and comments are not allowed.
When opening an existing TP Project I receive this error: Error processing batch response. An internal read request was too small.
I'm running TP 2012.3.606.0, Standard Edition in IE 10.
Other users who were in TP, continue to work fine. As soon as you exit, you can't get back in. Our other TP projects are working fine, just this one - Collateral rewrite.
As I was writing this bug, the problem cleared. Can you tell what the cause is?
I'm running TP 2012.3.606.0, Standard Edition in IE 10.
Other users who were in TP, continue to work fine. As soon as you exit, you can't get back in. Our other TP projects are working fine, just this one - Collateral rewrite.
As I was writing this bug, the problem cleared. Can you tell what the cause is?
1 Answer, 1 is accepted
0
Hi John,
Sorry to hear that you encountered this issue. This is a known issue, but unfortunately our team hasn't managed to reproduce it locally. I also want to recommend you our HTML version of TeamPulse where this issue does not exist. We have also recently released a new version - TeamPulse R3 2013 and i suggest you to take a look.
For now I would like to suggest you to workaround the problem by following these steps:
1. Navigate to the settings screen for your project in the xView site.
- If you know the ID of your project you can directly navigate to this URL:http://[teampulse-url]/xView/Settings/Index/{id}
- If you don't know the ID of your project, first go here: http://[teampulse-url]/xView, then find your project in the list, hover your mouse over the name of it, and click the "gear" icon (see attached screenshot named ModifyProjectSettings.png)
2. From the settings screen, change the Default Burndown Type, then click Save Changes.
3. Try again to reload the TeamPulse application.
Another way the people have gotten around this issue is with an IIS reset. Hopefully the steps provided above will help you out.
If you have further issues don't hesitate to contact us.
Regards,
Ivan
Telerik
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
Sorry to hear that you encountered this issue. This is a known issue, but unfortunately our team hasn't managed to reproduce it locally. I also want to recommend you our HTML version of TeamPulse where this issue does not exist. We have also recently released a new version - TeamPulse R3 2013 and i suggest you to take a look.
For now I would like to suggest you to workaround the problem by following these steps:
1. Navigate to the settings screen for your project in the xView site.
- If you know the ID of your project you can directly navigate to this URL:http://[teampulse-url]/xView/Settings/Index/{id}
- If you don't know the ID of your project, first go here: http://[teampulse-url]/xView, then find your project in the list, hover your mouse over the name of it, and click the "gear" icon (see attached screenshot named ModifyProjectSettings.png)
2. From the settings screen, change the Default Burndown Type, then click Save Changes.
3. Try again to reload the TeamPulse application.
Another way the people have gotten around this issue is with an IIS reset. Hopefully the steps provided above will help you out.
If you have further issues don't hesitate to contact us.
Regards,
Ivan
Telerik
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.