Comments by Kalyan_A - CodeProject

Kalyan_A 6-Jan-13 9:23am View

Setting timeout is useful only when you know that the process will finish in said time. Looks like you have locking issues with simultaneous access.

Identify the source of timeout/locks (DB or front-end) and fix the underlying problem. setting a large enough timeout without identifying the problem may be counter productive.

Cheers

Kalyan_A 2-Jan-13 5:34am View

Check if the client IE has compatibility-mode button enabled. Check if clicking it renders it any different.

If things dont work out, you may have to take a copy of the old-working-report and redo the changes.

Kalyan_A 2-Jan-13 4:41am View

hi mate,

I do not think its possible. The OS will always open a URL with the default browser.

you may already know this. the reason it prompts for username/password is because the site (SSRS) is setup for basic or integrated security. IE being native to windows passes the windows credentials to the server. Even IE would prompt for a password if you provide FQDN unless the site is part of trusted websites or classified as intranet website.

i am not sure its possible unless the client uses a IE shortcut on desktop to access your site. The only suggestion i have is (repeat) -

1. Setup the homepage of the site for anonymous access (no username/password)
2. The homepage will check the browser and display an appropriate message. If its IE, transfer to the SSRS page. else, display a warning and a link to manually access the site.

Cant think of anything else. all the best.

Cheers

Kalyan_A 2-Jan-13 4:17am View

I just meant how is the old copy (if you have one) of the report rendering on client machine.

Also, what is the IE version on server? Are the versions on client and server the same?

Comments by Kalyan_A (Top 4 by date)