One machine logs cs-uri-queries using + as the space and another in the same farm logs them using %20
I only noticed when searching for a specific document being accessed - one server was giving out 0 hits, which I thought odd, given that the farm is supposed to be load balanced.
I'm guessing its an IIS configuration rather than a logging issue - any ideas where this is set?
I'm trying to fix/patch the ASPNET 1.1 framework problem with the user-adgent string being too long.
Is there a ISAPI filter that could shape the USER-AGENT header before passing in to ASPNET?
The reports are getting rendered in HTML 3.2 instead of 4.0. Which stops the toolbar from appearing.
Has anybody managed to fix this issue?
Are there any tools for DFS troubleshooting? Some searches suggest network monitoring, but if you dont know how to read the scans with DFS in mind it seems a bit pointless.
When I log on to this machine any browsing web or windows only recognises "My Computer" and "Internet", everything that is not on the local machine is "Internet".
A colleague logs on and the zone is shown correctly in the status bar.
My profile works on other machines fine
Attempts to fix have included: Deleting the profile from the machine Removing the server from the Domain, deleting the AD machine account, reconnect.
Other may be connected issues: Browsing to http://localhost - I get challenged for uname/pass. Still says "Internet" in the status bar. When I go to ADD the website to the Intranet Zone. I get a dialog that says "There was an unexpected error with your zone settings. Unable to add this site."
We have an established Intranet based on WSS with two front ends and a database.
Currently all authentication is NTLM.
We have installed Reporting Services In Integration Mode.
RS works as long as the web front end that has RS installed on it handles the transactions.
If the front end without RS handles the request then we get an UNAUTHORIZED error.
In attempting to fix this problem, web searches etc. - have alluded to the problem being caused by the farm needing to perfrom 'double-hop' authentication - which cannot happen via NTLM.
So we need to configure the Intranet farm to accept Kerberos authentication.
I've found this helpful guide But it takes the stance that we are starting the farm from scratch.
So we need to know whether there are any risks involved in retroactively configuring Kerberos? Will NTLM carry on as before while and after we have carried out the steps to enable Kerberos?
We have a Intranet Farm with two load balanced front end servers and a separate database, Report server is installed on box 1, so enysys data extenstions can access the sharepoint DOM.
IIS-BOX 1 + Report Server
IIS_BOX 2
SQL Server
The problem is RS fails if the user is accessing box 2, through the load balancer. If we remove Box 2 from the LB - then RS works. Put it back and it intermittently fails.
Anybody got any idea if this topology should work and how to resolve the problem?