SQL EXPRESS Reporting Server (Access Denied - Windows 2000 Server Domain Controller)
Apr 4, 2007
Subject problem has me quite vexed.
I am receiving the following error when attempting to access reporting services... to sum things up real nice and tidy-
I get three login prompts - then the access denied response. It is almost as if it is unable to authenticate the user... anyway... here's the actual error response, I'd really appreciate any input/insight/resolution.
Server Error in '/Reports' Application.
Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
how to configure sql express 2008 R2 on windows server 2008 R2 domain controller?? and one more thing, what log on should I use for sql express service in sql server configuration manager on domain controller??
I am currently runinng Sql Server 2000 on a Windows 2003 domain controller. I cannot access my local sql server using windows authentication. All i receive is a cannot generate SSPI context error. I understand this is probably related to a security policy issue on the domain controller. Also Sqlserveragent service will not remain running and shutdowns immediately after it is started. This also produces an SSPI context error in the error log. If anyone can help with my configuartion of windows server 2003 such that sql server will recognize a valid sysadmin role for my domain admin account it would be greatly appreciated.
I've just got RS Enterprise Edition. Installed it in a Test Server, ok. Installed it in a DEV server, having some errors.
My DEV server is an "ALL in 1" server, which is also a Domian Controller. While Test Server is not a DC.
The installation was succesful but when I open RS Manager thru the web, it gives me a ASP.NET error:
Access to the path "D:Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportManagerin" is denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path "D:Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportManagerin" is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
I tried doing everything I can possible think of from the error message advice, including adding rights to ASPNET user from ISS to that particular folder...no success.
What I'm suspecting is I can't install RS in a DC box. But I can't find this info anyway in the web.
Anyone can point me to the correct direction or any advice?
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success. - Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server ------------------------------
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
If my SQL Server authentication is windows integrated authentication, whenever my application makes a connection to SQL server does it contact the windows active directory domain controller to authenticate the windows user account? How does windows integrated authentication work in the background?
I have 2 questions, the first one is more of a DC/AD issue, but I don't think there is a forum for that. But that question leads directly into my other question which involves SQL Server. I hope someone can give me some feedback.
We have a small network of about 12 users, and we are running SBS 2003 as our DC and Exchange server. We are going to start doing a lot of heavy lifting with data so we got another box to run Server 2003 Standard and SQL Server 2005 Standard. But now it's been suggested that we also install a second DC on the new SQL box. I am opposed because a DC should be on it's own box, and the SQL Server will need all of the available resources. I don't really think we need a second domain controller anyway, considering we have such a small office and good backups.
So my questions are: does anyone have an opinion as to whether or not we really need a second domain controller in our 12 person Small Business Server environment. I'm thinking there wouldn't be a whole lot of benefit. We certainly don't need it to share the load, and a SBS dc cannot give up it's FSMO roles so i don't see how a second dc would be able to properly serve as a failover should the first one go down.
My second question is: what kind of impact on the SQL Server would there be by installing a DC? I know it's not Microsoft recommended to have them on the same box.
I want to install SQL Express 2K5 on a lightly used second Windows 2003 SP1 DC. I know about the warning not to do this type of install. However, the group is small and their budget does not allow for another server just for one application. With that being said, the error message I keep getting is "can't create local groups......" (I know that you do not have local groups with AD). So, is there a work around to this issue or can someone point me in the right direction as how to install on a domain controller? Thanks in advance for your time!!!
I have a customer that was using Sql 2005 Express on a W2k3 server. They then decided to turn the server in to a second domain controller. When they did this Sql Express stopped working, I'm guess because the account the service was running as nolonger existed (Network Service account). Because of this they demoted it back to just a member server, but still the sql express service wouldn't start.
When I look at their server now I have noticed that the Sql2005$ accounts Sql express created during installation are all missing.
What I want to do now is set the Sql express setvice to use a domain account (using the SqlServer configuration manager), but I'm concerned that because the sql2005$ groups are missing things won't run as expected.
Should I be worried about these accounts?
What would happen when it becomes a domain controller anyway, won't these local account disappear and hence my new sqlexpress service account wouldn't have permission to the sql server data folders??
Hello everyone, I have searched the forum regarding this topic and have found numerous good threads about installing SQL Express on a DC. My question is, I am assuming that if installing SQL Express on a Domain Controller is not recommended, that installing the MSDE 2000 on a Domain Controller is not recommended either?
I saw a lot of webcast about security in Sql Server and many of those talk about that is not recomendable install Sql Server on Windows Server Domain Controller. Actually, I don't know Why not? Someone can explain me, please?
I would like to install SQL server 2005 cluster on Windows 2003 cluster. Is domain controller (AD and DNS) necessary for the SQL server 2005 cluster? If yes, may I install it on one of the SQL server 2005 cluster nodes? Thanks in advance
Hi! I understand that this topic is one of the most discussed topics ever. However i could not find the relevant information after going through (almost) all the posts so far. Hence this post. I am getting the 'SQL Server does not exist or access denied' error when I am trying to access SQL Server from a WINDOWS SERVICE. SQL Server and the Windows service are running on two different machines. (When they are on the same machine, it works). All the solutions I found so far are related to web apps. What should I do in the case of a windows service? My connection string uses SQL server authentication. (I tried with windows authentication. Its not working either.). Under what login does windows services run and how can I add it to valid SQL server logins?
I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver. The linked server has been defined and working for months when used from a SQL Server authenticated session. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. Here are the error messages:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA".
The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.
In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box.
So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above.
Hi guys. I created a database "MyDatabase" using an AD Account "user01" which is a member of a domain group "GroupA". I have created a login in my SQL Server 2005 for this AD group. I have also added the said login as a user of my database. I created other AD users and put them in the same group. When I try to access the database using the other users, I get this message
The server principal "MyDomainuser02" is not able to access the database "MyDatabase" under the current security context.
This KB tells me that my situation is triggered by the first case in which the owner of the database is windows authenticated. I have already set the database to be TRUSTWORTHY. I haven't tried CERTIFICATES though. I believe I haven't done anything complex to warrant this solution.
I'm really lost with the myriads of principals and securables that SQL2005 has. All I want is just to execute a certain set of stored procedures. I can't do this because I can't even execute "USE MyDatabase". What are the permissions I need to give to "GroupA" ?
Can anyone help me with a problem I have with SSRS 2005? How do I configure SQL Server 2005 Reporting Services to deliver subscription e-mails to addresses external to my windows domain?
I've been having trouble configuring the Report Server e-mail delivery component to send subscription e-mails to addresses outside the domain on which the report server is hosted.
For e.g. since my local windows domain is named "smartsystems.com", I have found that the Report Manager does not have any problems sending subscription mails to "eawagu@smartsystems.com" but throws up an error whenever I include "eawagu@yahoo.com" in the recipients' list.
After installing SQL Server express to my WinXP machine, when I attempt to restore a database from a 2000 backup, I get the following error:
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTEST.MDF'. (Microsoft.SqlServer.Express.Smo)
I know this has been asked and addressed in many other posts, but I havnt found the answer to this scenario. I have a server running on my internal network, I have a wireless router that has ports 80 and 5801(my sql port) forwarded to my server internally. So, from my website I am attempting to make some requests to my server, but all I ever get at these Error:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied errors. My connection string looks like this: Private DBConn As OleDbConnection Dim DBCommand As OleDbCommand = New OleDbCommand Try DBConn = New OleDbConnection("Provider=SQLOLEDB;Data Source=external IP,5801;Initial Catalog=DataWarehouse;User Id=WEBUSER;Password=*****") DBCommand.CommandText = "SELECT * from Users" DBCommand.Connection = DBConn DBConn.Open() DBConn.Close() Catch Response.Write("Error:" & Err.Description) End Try End Sub I know I have a service running on port 5801 and the port is open in my firewall, also I have sqlserver.exe as an exception in my firewall. I have been browing the web and trying different ideas for the better part of a week. Just wondering if anyone has run into this problem or if its my server or my web hosting company who has the problem. Thanks in advance for any help. Kyle
I have been for years using the following code locally in native ASP (except different UID and PWD and file path for the msado15.dll) with SQL Server 2000 on XP to do my development and then I upload to the web site later (uses different objConn etc when live). I've now tried to use the same for SQL Server Express and Vista and always get the "does not exist or access denied" error ( 2147467259).
I only want to use SQL Server locally from the machine I'm developing on as I upload the tested "ASP" code to the server which runs it. The SQL Server Browser is running and I have checked the Firewall exclusions for sqlservr.exe. Also I installed it with out Windows Logon (same as I had for SQL Server 2000).
Any ideas, I tried using the Data Source=localhost instead of explicitly defing the path except that had no affect either, I also changed the rshstest_data.mbf to rshstest.mbf as well also to no affect as there appears a difference with this in 2000 and Express?
Any suggestions would be appreciated, thanks..
<!-- METADATA TYPE="typelib" FILE="e:Program FilesCommon FilesSystemadomsado15.dll" --> <% on Error resume next objConn.Close Set objConn = Nothing Dim objConn Set objConn = Server.CreateObject("ADODB.Connection") objConn.Open "Provider=SQLOLEDB;Persist Security Info=False;" & _ "User ID=xx;Password=xx;Initial Catalog=rshstest;" & _ "Initial File Name=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData shstest_data.mdf" ' "Data Source=localhost;"
I cannot connect to the remote SQL Server 2000 running on this machine that has just been upgraded to the W2003 server. Everything worked perfectly before the upgrade on W2000. All the logins, firewall setting stayed the same. Can ping the machine. But when trying to register/link, or connect thru ODBC, I got the error SQL server does not exist or access denied. We don't have SQL server SP3 installed.
I have recently downloaded SQL Server Express which I have installed using Windows authentication mode. I cannot seem to be able to make a connection to SQL Server from Dreamweaver or Microsoft Visual Web Developer as I am getting an error Server does not exist or access is denied....
I am relatively new to all of this, so would appreciate any advice....
When I installed SQL Server Express I chose Windows Authentication. When I fire up SQL Express and view Security option - the installation program has set up an sa login with a random password. I did not set this password, but think this might be a reason why I can't connect. To rectify the problem I tried creating a new user in SQL Server Express with a password that I specified. On going in to check the settings, I notice SQL Server Express has gone and changed it from the password that I set up.
Now when I try and connect to SQL Server Express I specify the following in the connection paramaters
Server: BGIRLSQLEXPRESS
Database The database name that I've created
User: the new user that I created
Password: the password I created as part of new user setup
Now I get error message Server does not exist or access denied
Is the problem to do with passwords or perhaps one of the many parameters one seems to have to set up? How can I change a password if I didn't create it? Is there anywhere I can reset it?
PLEASE HELP - I have literally spent 3 days attempting to get this working and am about to give up entirely. Due to my lack of experience, I need very specific step by step instructions..
We have a SQL Server 7.0 system in NT 4.0 environment. We upgraded our users to Access 2000 and started to work with this. Now we installed a new server which is Windows 2000 based and the domain is different from the SQL servers domain. We then installed Access 2000 on Windows 2000 to use with terminal server. But I noticed that there was a problem with the program. I then looked at the program which was written on Access 2000 and saw that the tables and views can't be seen. The program runs but I can't see the views and tables. Another thing is access disconects from SQL Server when I want to see the tables. So what can be the problem.
In one part there is an Access 2000 on Windows 2000 server. On the other part SQL Server 7.0 on Windows NT 4.0. And Access can't see the tables in SQL server.
I am using an unattended install script to install the database on the client machine. All the settings look correct. But my application cannot access the db -
Error: Cannot open database requested by the login.
Now when I install SQL Server Express manually, it works fine. I have the service running under local system and enabled user instances is true. I cannot figure out the problem(been working on it for 2 days).
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master) -A sql server 2005 on a win server 2003 in "sub domain" AD -A linked server to "sub domain" AD -A linked server login using a "sub domain" admin acccount -A view to this linked server -A grant on masterDomain/Domain Users to the database -A grant on subDomain/Domain Users to the database -We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts. Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT * FROM OPENQUERY(ADSI, 'SELECT displayname, givenName, sn, cn (etc...) FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com'' WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
I successfully got SQL 2005 Express with reporting services running under VISTA. Developed some reports in the VISTA environment. However, my target system is a Windows 2000 server. We installed SQL 2005 w/reporting services onto the Windows 2000 server. SQL2005 Database is up and running. Reporting Services are running, IIS RRS virtual directories are built, RRS databases are built. I can do everything except deploy reports from Business Intelligent Studio. I can preview reports, just cannot deploy. The Reporting Services indicate 1 failure in its configuration; the Web Service Identity. It is loaded with <server>ASPNET. I cannot get rid of this error. I assume this is the problem. After digging around I found that Windows 2000 does not have an ASPNET user, it uses the IWAM user instead. Reporting services did not run at all till I changed the rs config file and put the IWAM user in as <WebServiceAccount>.
Does anyone have Reporting services 2005 running on Windows 2000 server? Anyone know how to fix the Web Service Identity error I am getting?
I have a windows app I am deploying by CD along with SQL Server - when I manually installed sql server my app can access the db (named instance, local system, mixed mode). I used the exact same settings to do an unattended install for sql express and it does not work. All the settings in the db look the same. Does anyone know what it could be?
I have been through virtually every last posting on installing SQL Server Express with Advanced Services in this site and still have no success accessing the Reporting Services site: http://localhost.reports$sqlexpress. I get a the correct background to the site as in the tutorials, but only get "ERROR - unable to connect to the remote server", which may be indicative because this is all installed on my local machine (Dell AMD Athlon 64 X2 Dual Core 4000+ 2.11 Ghz, 1GB, Windows Ultimate). I have gone through How to install ... on a Windows Vista-based computer, KB934164, and most recently, How to configure .. to allow remote connections, kb 914277, in hopes of addressing the "remote server" issue. I still can't get past this obstacle. PLEASE HELP!! :-)
I have downloaded SQL Server 2005 express from microsoft's site and tried to install in windows 2000 service pack 4 but having an unexpected error. The screenshot and log file is attached. Please suggest.
The error log is as shown:
Microsoft SQL Server 2005 Setup beginning at Fri May 05 21:36:51 2006 Process ID : 1008 e:469a4a9ba4bfdc9d2db501289fb676setup.exe Version: 2005.90.2047.0 Running: LoadResourcesAction at: 2006/4/5 21:34:50 Complete: LoadResourcesAction at: 2006/4/5 21:34:50, returned true Running: ParseBootstrapOptionsAction at: 2006/4/5 21:34:50 Loaded DLL:e:469a4a9ba4bfdc9d2db501289fb676xmlrw.dll Version:2.0.3609.0 Complete: ParseBootstrapOptionsAction at: 2006/4/5 21:36:51, returned false Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run: Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Wed Oct 26 16:38:20 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Wed Oct 26 16:38:20 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x800706b5 (1717) Windows Error Text: The interface is unknown.
Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Wed Oct 26 16:37:25 2005 Function Name: sqls::CryptSameUserSameMachine::ProtectData Source Line Number: 50
1717 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:20 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "1008"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2006/4/5 21:36:51 Complete: ValidateWinNTAction at: 2006/4/5 21:36:51, returned true Running: ValidateMinOSAction at: 2006/4/5 21:36:51 Complete: ValidateMinOSAction at: 2006/4/5 21:36:51, returned true Running: PerformSCCAction at: 2006/4/5 21:36:51 Complete: PerformSCCAction at: 2006/4/5 21:36:51, returned true Running: ActivateLoggingAction at: 2006/4/5 21:36:51 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:20 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 02AFCFC0Unable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44
Class not registered. Failed to create CAB file due to datastore exception Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:20 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "1008"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupBootstrapOptionsScope.HostSetup Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Message pump returning: 2
Steps to install SSX (& Reporting Serivces) on 64 bit Windows Vista Ultimate
I struggled quite a bit over the past few days to complete this install. The sequence of steps is less obvious than those for Windows XP Pro on a 32 bit machine.
I recorded all the steps in one place in cookbook style for non-technical (but database capable) users like myself. I have referenced appropriate other postings and sources for detail steps. These are steps I found useful, you may be in a different situation.
My environment is as follows: -New HP dv9000 w/ 2GHz and 2GB memory -Factory installed Windows Vista Ultimate. Note this includes .NET Framework 2.0 so I did not have to deal with installing that. -I have no extant databases or SQL Server that I am trying to convert or upgrade!
Setup Steps Before Install: 1) Turn off User Account Control. At present, I am a one-user operation with close control over my system and there seemed to be issues with getting reporting services set up right with UAC. I may come back and modify this step later on and certainly would change this for any releasable systems.
1a)Go to Control Panel Home --> User Accounts --> Turn User Account Control on or off. 1b)Unselect Use User Acount Control. 2)Set up your IIS 7.0 for Reporting Services. IIS 7.0 has IIS 6.0 Compatibility features turned off out of the box. You will turn them on with this step. This is needed for both Reporting services and to enable the Adminscripts that are used in Step 3 below.
2a) Use the Control Panel --> Programs --> Turn Windows features on and off function. This is quite nicely desribed with screen shots at: http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=957 These steps worked for me although they are labeled Vista Beta 2.
3)Set up your 64 bit machine to run 32 bit ASP.NET This capability is needed to make sure you pass the System Configuration Check for Reporting Services. I don't know the full implications of this step and wonder if it might eventually bite me if I have to flip-flop between 32 and 64 bit ASP.NET or have them both run at the same time.
3a) Open a command line window by: Start --> Accessories -- Cmd Prompt 3b) In this window type: cscript %SystemDrive%inetpubAdminScriptsadsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
At some point, you may wish to go back to 64 bit. For that, see the posting by MihaelaE as an Answer in the SQL Server Reporting Services Forum under a thread started by fagster on 3/8/2007.
Now to actually install SQL Server.
1) Download the 64 bit SSX. This step fooled me for a while as the 64-bit downloads are 'below the fold' on the web page.
1a) Go to the SSX download page: http://msdn.microsoft.com/vstudio/express/sql/download/
1b) Scroll down the page and below Step 5, Register, you will see this text which takes you to the download you want: "* For the 64-bit install of SQL Server 2005 Express Edition, click here." 1c) Follow the "click here" to get the download.
2) Install the package from step 1c and you will get SQL Server Express.
2a) The install may fail and complain about not finding a valid SQL Server Native Client Install, sqlncli_x64.msi. You will have to extract the files manually and then run the sqlncli_64.msi package by itself. Then you can go back to step 2 and should be successful. To do this, see post of Mike Wachal on 4/5/2007 to SQL Server Express Forum, titled "Cannot Install SQL Server Express on Vista Ultimate -- cannot find MS SQL Server Native Client".
3) Now add in the SQL Server Management Studio Express 64 bit version.
3a) Go to the SSX download page: http://msdn.microsoft.com/vstudio/express/sql/download/
3b) Scroll down the page and below Step 5, Register you will see this text which takes you to the download you want: "* For the 64-bit install of SQL Server 2005 Management Studio Express, click here."
3c) Follow the "click here" to get the download.
4) Now add the SQL Server Reporting Services.
4a) Go to the SSX download page: http://msdn.microsoft.com/vstudio/express/sql/download/
4b) Scroll to Step 3 Download and Install (in the middle of the page) and download SQL Server Express Edition with Advanced Services SP2. 4c) Install, but at the Feature Selection screen, disable all components EXCEPT Reporting Services. You already have the other components installed. 4d) In the install, you will get a screen called "Report Server Installation Options". Go ahead and select the "Install but do not configure the server" radio button.
5) Go ahead and configure SQL Server Reporting Services. I'm not highly skilled in this area so I recommend the SQL Server Express Video "Learning Video 10: Getting Started with Reporting Services". This is found at: http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx I found this video to be cogent and useful.
That's what it took me to get SQL Server Express installed with reporting services on a 64 bit Vista Ultimate system. Sorry if this is so long but I wanted to cover all the steps that hung me up.
To forum moderators: If I have any errors that will lead people astray, I'm more than happy to correct them.
This posting is "AS IS" with no warrantees and caveat emptor.