EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB10697: "Server <ServerName> has temporarily become unavailable" error message appears when running large reports in 3-tier through MicroStrategy Desktop 10.x.


Community Admin

• Strategy


Users receive the following error message when running reports with large data sets in 3-tier using MicroStrategy Desktop. The same report executes successfully in MicroStrategy Web:

SYMPTOM:
Users receive the following error message when running reports with large data sets in 3-tier using Strategy Developer. The same report executes successfully in Strategy Web:
Error: Server <ServerName> has temporarily become unavailable
In the DSSErrors.log, the following error message is detected around the time that the Strategy Developer users report the problem:
2004-10-07 12:33:54.357-06:00 MSINetStream::net_read(), socket recv() error, error code = 10055
CAUSE:
This issue occurs because the data returning from the Strategy Intelligence Server is too large for the client (Developer) machine to handle as it lacks sufficient buffer space.
 
It is possible that the same report may execute without any errors on a different client machine.
 
ACTION:
The fix entails packaging the packets coming to the Network Classes code (from the serialization code) before they are sent to the client into 20 MB lumps and breaking them into 20 MB chunks if they are larger in size. As this figure may affect the performance of the Narrowcast Server services, users can create a registry setting to change it under "HKLM\Software\MicroStrategy\Data Sources\CastorServer" in the registry. Users should create a DWORD entry "NetChunkingSize" and set its value to the desired MB in hexadecimal.
 
By default the "NetChunkingSize" is not present in the registry and 20MB is used as the chunk size, users should not alter this value unless they are positive that it is the cause of the performance problems.
 
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user`s own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 5, 2017

Last Updated:

April 5, 2017