March 11, 2009 at 1:46 am
Hello,
We have sql server 2000 default instance including reporting services.In this case we need to must upgrade database engine n reporting services together as Upgrade document says.
we are going for in-place upgrade for reporting services from 2000 to 2005. For this we need to must the follow the below as Upgrade document says.
1.Security for the virtual directories must be set to Integrated Windows Authentication; Anonymous Access is not supported for an in-place upgrade.
2.The default Application Mappings should be set as follows:
a.For the report server virtual directory, the wild card mapping must point to the v1.1 aspnet_isapi.dll executable and no other script maps should exist.
b.For the Report Manager virtual directory, the .asax and .aspx extensions must point to the v1.1 aspnet_isap.dll executable
.
In our sql 2000,I checked the report server and reports properties in IIS,
1.Reports->properties->directory security(Here anonymous Access is enabled and integrated windows authentication is NOT selected. )
2.Report server->properties->directory security(Here anonymous Access is enabled and integrated windows authentication is NOT selected. )
Report Server wild card is maaped to c:\windows\microsoft.net\framework\v1.1.4322\aspnet_isapi.dll.
But in the report manager properties there is no wild card mappings?nothing is mapped there.
Can I change this Anonymous access to Integrated Windows authentication?
Can I map the wild card for Report manager(Reports) same as Report server(c:\windows\microsoft.net\framework\v1.1.4322\aspnet_isapi.dll)?
As the SQL2005UpgradeTechRef says that if you have default instance of sql 2000 and reporting services were installed, they must be upgraded together to sql 2005 and NO anonymous access and wild card should point to the v1.1 aspnet_isapi.dll executable and no other script maps should exist.
But we have sql 2000 default instance with reporting services, so must do in-place.But not qualifying other condition mentioned above. So please suggest me what are the steps I need follow in this suituation
March 11, 2009 at 11:12 am
Hi,
Any body has some solution please......
March 12, 2009 at 8:27 am
I cannot answer your RS query, but I can give some general advice about in-place upgrades from SQL 2000 to SQL 2005.
A significant number of upgrades will fail during the installation of SQL Server 2005, leaving SQL Server totally unusable. The only solutions are either restore your system disks back to a previous image (and try another way to upgrade), or uninstall SQL Server and start with a fresh install.
This problem does not hit all in-place upgrades, but maybe 30% of upgrades are likely to fail. Your upgrade strategy should include planning for what you will do when you get this issue. Many people decide the risks around this are not good, and decide to always do a fresh install on to a new installation of Windows.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply