Image width is not in range. Valid range is from 1 to 2048

[LakshmananVenkatesan]

All,

We are facing an issue on ESRI sliverlight (v 3.1) based web applcication. Few of the users complaining that map is not being displayed in their machine. When I investigated fiddler log, map service (using 10.1) request throws 404 error . Below is the detailed

Error
Specified format is not supported
Code: 400
Image width is not in range. Valid range is from 1 to 2048.


Users are using dual monitors and different browser zoom levels, so few people are ok and few other facing trouble in viewing map layers, how to fix this issue for different screen resolutions and browser zoom levels?? I am looking for comprehensive solution for this issue. Thanks in advance

[DominiqueBroux]

Image width is not in range. Valid range is from 1 to 2048.

From ArcGIS server 10.1, the map services return their max image height and max image width, and the SL API is using that to constraint the image size.
So you should no more run into this issue with server 10.1 and arcgis SL 3.1. Could you check your server version?

[LakshmananVenkatesan]

I am sorry, that was typo. I am using ArcGIS server 10 SP4. Please let me know how to resolve the issue.

[DominiqueBroux]

I am sorry, that was typo. I am using ArcGIS server 10 SP4. Please let me know how to resolve the issue.

By migrating to 10.1 🙂

[LakshmananVenkatesan]

We have plans to migrate to 10.1, but not immedetialy, can you give me a solution using 10.0. I am asking end users to increase zoom % and work on but that does not help other people. Do you want me to create a ticket with ESRI on this?

[DaveTimmins]

For v10 you can change the maximum image height and width in the service configuration files (the default is 2048). See http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#//0093000000mr... and the MaxImageHeight and MaxImageWidth properties for the MapServer. Note that increasing these will affect the performance.

Cheers,

[LakshmananVenkatesan]

Hi Dave,

Thanks for your response. Now, this is getting tougher, if these changes brings performance impact then we may not able to do this. Do we have any other solution for this case?. Sorry to bother you, but any impact on performance surely not an acceptable solution for end users.

[DaveTimmins]

It is worth testing how the change will impact end users. The reason it will affect performance is that the server has to do more work to generate a larger image and there is more data to transfer over the network so you will have increased network latency. This may still perform to an acceptable level though, it really depends how complex your service is and how powerful your server is.

There aren't any other nice ways to do what you want though some examples in case you really want to investigate something different are changing your UI to make the map smaller, or you could write your own layer that requests the image in sections so each one is smaller. I wouldn't recommend these though.

Cheers,