RS first did work for me after installation on my notebook, but some silly
changes of our network admin ruined everything:
RS does not run any more, gave me some access denied errors. Complete RS
Re-Installation told me at the end that it could not initialize RS: "Setup
could not initialize the Report Server - you must manually initialize Report
server before using it for the first time." But Rsactivate did not cure it.
It give an "
Error starting Webservice:
The Reportserver Webservice has not generated a public key. The service was
eventually not started successfully. See Log files for further Information.
I did look into the log files and work along half a dozen knowledgebase
articles and re-installed RS several times and even .NET framework. NO
SUCCESS. Answers in this newsgroup DID NOT HELP. I've noticed several
requests for the same problem - there was NEVER an answer that lead to a
successful solution.
I cannot access localhost reportserver. It keeps reporting access rights
problems all time. Yesterday, after looking at the .LOG files again I gave
full access rights to the Reporting Services directories and everything
below to the LOCAL SERVICE and the SYSTEM accounts. NO SUCCESS again:
RS is running, but when I launch localhost/reportserver I get the following
(translated from German):
Server error in application '/ReportServer'.
--
Program directory 'C:\Program files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\' cannot be accessed. The directory is not available
or it cannot be accessed because of safety settings.
Description: When executing the current Web request an unprocessed error
occurred. Check Batch control to display further Information on this error
and find out where in the Code the error was caused.
Exception details: System.Web.HttpException: Program directory 'C:\Program
files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\' cannot be
accessed. The directory is not available or it cannot be accessed because of
safety settings.
Source error:
When executing the current Web request an unprocessed error occurred.
Information on the source and the Position of the exception can be displayed
using the exception batch control.
batch control:
[HttpException (0x80004005): Program directory 'C:\Program files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportServer\' cannot be accessed. The
directory is not available or it cannot be accessed because of safety
settings.]
System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +263
[HttpException (0x80004005): ASP.NET-Initialisation error]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +964
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +128
--
Version information: Microsoft .NET Framework Version:1.1.4322.573;
ASP.NET-Version:1.1.4322.573
ASP.NET is working - I tested it by running a sample application of ChartFX.
I even did remove the write protection from these directories: same result.
Today I did establish full rights for IWAM, IUSR and ASPNET. And I did set
the default website to (All Unassigned). NO CHANGE.
Now I have reached the end of the road. Please someone tell me the right way
how to define the access rights correctly, and in which sequence, in my
case for having
RS and SQL Server and AS installed together on 1 machine (XP pro).
Any comments appreciated.
HelmutThis is a multi-part message in MIME format.
--=_NextPart_000_00B5_01C4BCC8.A27CB760
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Forgive if you have already tried these:... I looked for a dot net =framework security thing, but couldn't find it... It seems like I had to =go to dot not config and set up an application security piece at one =time... Sorry but I could not find any info on that ( perhaps I =remember incorrectly.)
HTTP 404 File or directory not found
This error indicates that there is a problem with the virtual directory =configuration. In IIS, navigate to the report server virtual directory, =and right-click Properties. On the Virtual Directory tab, click =Configuration, select the extension, and click Edit. Make sure that =Check that the file exists (or Verify that the file exists) is cleared.
HTTP 500 Internal server error
Reporting Services requires version 1.1.4322 of the .NET Framework. This =error can occur when the report server or Report Manager virtual =directories are mapped to version 1.0.3705. To check the application =mapping, navigate to the report server virtual directory, and =right-click Properties. On the Virtual Directory tab, click =Configuration, scroll to the .aspx extension, and read the Executable =Path value. If it is set to v1.0.3705, you must configure the virtual =directory to use 1.1.4322. Follow the instructions provided in Knowledge =Base Article 306005 to map v1.1.4322 to IIS.
-- Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Helmut Knappe" <HK_noSPAM@.biware.com> wrote in message =news:clq9mt$ari$1@.svr7.m-online.net...
> Hi all,
> > RS first did work for me after installation on my notebook, but some =silly
> changes of our network admin ruined everything:
> > RS does not run any more, gave me some access denied errors. Complete =RS
> Re-Installation told me at the end that it could not initialize RS: ="Setup
> could not initialize the Report Server - you must manually initialize =Report
> server before using it for the first time." But Rsactivate did not =cure it.
> It give an "
> Error starting Webservice:
> The Reportserver Webservice has not generated a public key. The =service was
> eventually not started successfully. See Log files for further =Information.
> I did look into the log files and work along half a dozen =knowledgebase
> articles and re-installed RS several times and even .NET framework. NO
> SUCCESS. Answers in this newsgroup DID NOT HELP. I've noticed several
> requests for the same problem - there was NEVER an answer that lead to =a
> successful solution.
> > I cannot access localhost reportserver. It keeps reporting access =rights
> problems all time. Yesterday, after looking at the .LOG files again I =gave
> full access rights to the Reporting Services directories and =everything
> below to the LOCAL SERVICE and the SYSTEM accounts. NO SUCCESS again:
> > RS is running, but when I launch localhost/reportserver I get the =following
> (translated from German):
> Server error in application '/ReportServer'.
> --
> Program directory 'C:\Program files\Microsoft SQL =Server\MSSQL\Reporting
> Services\ReportServer\' cannot be accessed. The directory is not =available
> or it cannot be accessed because of safety settings.
> Description: When executing the current Web request an unprocessed =error
> occurred. Check Batch control to display further Information on this =error
> and find out where in the Code the error was caused.
> > Exception details: System.Web.HttpException: Program directory ='C:\Program
> files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\' =cannot be
> accessed. The directory is not available or it cannot be accessed =because of
> safety settings.
> > Source error:
> When executing the current Web request an unprocessed error occurred.
> Information on the source and the Position of the exception can be =displayed
> using the exception batch control.
> > batch control:
> [HttpException (0x80004005): Program directory 'C:\Program =files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\' cannot be accessed. =The
> directory is not available or it cannot be accessed because of safety
> settings.]
> System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +263
> [HttpException (0x80004005): ASP.NET-Initialisation error]
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +964
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) =+128
> --
> Version information: Microsoft .NET Framework Version:1.1.4322.573;
> ASP.NET-Version:1.1.4322.573
> > ASP.NET is working - I tested it by running a sample application of =ChartFX.
> I even did remove the write protection from these directories: same =result.
> > > Today I did establish full rights for IWAM, IUSR and ASPNET. And I did =set
> the default website to (All Unassigned). NO CHANGE.
> > Now I have reached the end of the road. Please someone tell me the =right way
> how to define the access rights correctly, and in which sequence, in =my
> case for having
> RS and SQL Server and AS installed together on 1 machine (XP pro).
> > Any comments appreciated.
> Helmut
> > > > >
--=_NextPart_000_00B5_01C4BCC8.A27CB760
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Forgive if you have already tried these:... I looked =for a dot net framework security thing, but couldn't find it... It seems like I =had to go to dot not config and set up an application security piece at one =time... Sorry but I could not find any info on that ( perhaps I remember incorrectly.)
HTTP 404 File or directory not =found
This error indicates that there is a =problem with the virtual directory configuration. In IIS, navigate to the report server =virtual directory, and right-click Properties. On the Virtual Directory tab, =click Configuration, select the extension, and click Edit. Make sure that =Check that the file exists (or Verify that the file exists) is cleared.
HTTP 500 Internal server =error
Reporting Services requires version =1.1.4322 of the .NET Framework. This error can occur when the report server or Report =Manager virtual directories are mapped to version 1.0.3705. To check the =application mapping, navigate to the report server virtual directory, and =right-click Properties. On the Virtual Directory tab, click Configuration, scroll to =the .aspx extension, and read the Executable Path value. If it is set to =v1.0.3705, you must configure the virtual directory to use 1.1.4322. Follow the instructions provided in Knowledge Base Article 306005 to map v1.1.4322 =to IIS.
-- Wayne Snyder, MCDBA, SQL =Server MVPMariner, Charlotte, NCwww.mariner-usa.com(Please respond only to the newsgroups.)
I support the Professional Association =of SQL Server (PASS) and it'scommunity of SQL Server =professionals.www.sqlpass.org
"Helmut Knappe"
--=_NextPart_000_00B5_01C4BCC8.A27CB760--|||This is a multi-part message in MIME format.
--=_NextPart_000_000E_01C4BD93.160672A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello Wayne,
thank you for your answer - no, I haven't checked these. However the =settings were correct: The check function (for 404) was cleared already. =For the http 500 error there was no aspx extension, only one setting for =a * extension, but I guess this covers all. This was pointing to the =1.1.4322 directory.
I'm about to re-install whatever is needed to make it work. The =questions are:
1. What should I re-install ?
- Reporting Services
- SQL Server
- .NET framework
- ... ?
- Windows XP
2. which service packs should I use?
- Windows XP SP 2
- SQL Server 3a
- Reporting Services SP 1
- ...
3. in which sequence should I re-install?
4. which accounts should I use for what?
Any answer pointing in the right direction, to the right document etc. =is welcome.
Regards,
Helmut
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> schrieb im =Newsbeitrag news:%23dx8roOvEHA.2116@.TK2MSFTNGP14.phx.gbl...
Forgive if you have already tried these:... I looked for a dot net =framework security thing, but couldn't find it... It seems like I had to =go to dot not config and set up an application security piece at one =time... Sorry but I could not find any info on that ( perhaps I =remember incorrectly.)
HTTP 404 File or directory not found
This error indicates that there is a problem with the virtual =directory configuration. In IIS, navigate to the report server virtual =directory, and right-click Properties. On the Virtual Directory tab, =click Configuration, select the extension, and click Edit. Make sure =that Check that the file exists (or Verify that the file exists) is =cleared.
HTTP 500 Internal server error
Reporting Services requires version 1.1.4322 of the .NET Framework. =This error can occur when the report server or Report Manager virtual =directories are mapped to version 1.0.3705. To check the application =mapping, navigate to the report server virtual directory, and =right-click Properties. On the Virtual Directory tab, click =Configuration, scroll to the .aspx extension, and read the Executable =Path value. If it is set to v1.0.3705, you must configure the virtual =directory to use 1.1.4322. Follow the instructions provided in Knowledge =Base Article 306005 to map v1.1.4322 to IIS.
-- Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Helmut Knappe" <HK_noSPAM@.biware.com> wrote in message =news:clq9mt$ari$1@.svr7.m-online.net...
> Hi all,
> > RS first did work for me after installation on my notebook, but some =silly
> changes of our network admin ruined everything:
> > RS does not run any more, gave me some access denied errors. =Complete RS
> Re-Installation told me at the end that it could not initialize RS: ="Setup
> could not initialize the Report Server - you must manually =initialize Report
> server before using it for the first time." But Rsactivate did not =cure it.
> It give an "
> Error starting Webservice:
> The Reportserver Webservice has not generated a public key. The =service was
> eventually not started successfully. See Log files for further =Information.
> I did look into the log files and work along half a dozen =knowledgebase
> articles and re-installed RS several times and even .NET framework. =NO
> SUCCESS. Answers in this newsgroup DID NOT HELP. I've noticed =several
> requests for the same problem - there was NEVER an answer that lead =to a
> successful solution.
> > I cannot access localhost reportserver. It keeps reporting access =rights
> problems all time. Yesterday, after looking at the .LOG files again =I gave
> full access rights to the Reporting Services directories and =everything
> below to the LOCAL SERVICE and the SYSTEM accounts. NO SUCCESS =again:
> > RS is running, but when I launch localhost/reportserver I get the =following
> (translated from German):
> Server error in application '/ReportServer'.
> --
> Program directory 'C:\Program files\Microsoft SQL =Server\MSSQL\Reporting
> Services\ReportServer\' cannot be accessed. The directory is not =available
> or it cannot be accessed because of safety settings.
> Description: When executing the current Web request an unprocessed =error
> occurred. Check Batch control to display further Information on this =error
> and find out where in the Code the error was caused.
> > Exception details: System.Web.HttpException: Program directory ='C:\Program
> files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\' =cannot be
> accessed. The directory is not available or it cannot be accessed =because of
> safety settings.
> > Source error:
> When executing the current Web request an unprocessed error =occurred.
> Information on the source and the Position of the exception can be =displayed
> using the exception batch control.
> > batch control:
> [HttpException (0x80004005): Program directory 'C:\Program =files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\' cannot be =accessed. The
> directory is not available or it cannot be accessed because of =safety
> settings.]
> System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +263
> [HttpException (0x80004005): ASP.NET-Initialisation error]
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +964
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest =wr) +128
> --
> Version information: Microsoft .NET Framework Version:1.1.4322.573;
> ASP.NET-Version:1.1.4322.573
> > ASP.NET is working - I tested it by running a sample application of =ChartFX.
> I even did remove the write protection from these directories: same =result.
> > > Today I did establish full rights for IWAM, IUSR and ASPNET. And I =did set
> the default website to (All Unassigned). NO CHANGE.
> > Now I have reached the end of the road. Please someone tell me the =right way
> how to define the access rights correctly, and in which sequence, =in my
> case for having
> RS and SQL Server and AS installed together on 1 machine (XP pro).
> > Any comments appreciated.
> Helmut
> > > > >
--=_NextPart_000_000E_01C4BD93.160672A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello Wayne,
thank you for your answer - no, I =haven't checked these. However the settings were correct: The check function =(for 404) was cleared already. For the http 500 error there was no aspx extension, =only one setting for a * extension, but I guess this covers all. This was =pointing to the 1.1.4322 directory.
I'm about to re-install whatever is =needed to make it work. The questions are:
1. What should I re-install =?
- Reporting Services
- SQL =Server
- .NET =framework
- ... ?
- Windows =XP
2. which service packs should I =use?
- Windows XP SP =2
- SQL Server =3a
- Reporting Services =SP 1
- ...
3. in which sequence should I re-install?
4. which accounts should I use for what?
Any answer pointing in the right =direction, to the right document etc. is welcome.
Regards,
Helmut
"Wayne Snyder"
Forgive if you have already tried these:... I =looked for a dot net framework security thing, but couldn't find it... It seems =like I had to go to dot not config and set up an application security piece at =one time... Sorry but I could not find any info on that ( perhaps I =remember incorrectly.)
HTTP 404 File or directory not =found
This error indicates that there is a =problem with the virtual directory configuration. In IIS, navigate to the report =server virtual directory, and right-click Properties. On the Virtual =Directory tab, click Configuration, select the extension, and click Edit. Make sure =that Check that the file exists (or Verify that the file exists) is cleared.
HTTP 500 Internal server =error
Reporting Services requires version =1.1.4322 of the .NET Framework. This error can occur when the report server or Report =Manager virtual directories are mapped to version 1.0.3705. To check the =application mapping, navigate to the report server virtual directory, and =right-click Properties. On the Virtual Directory tab, click Configuration, scroll =to the .aspx extension, and read the Executable Path value. If it is set to v1.0.3705, you must configure the virtual directory to use 1.1.4322. =Follow the instructions provided in Knowledge Base Article 306005 to map =v1.1.4322 to IIS.
-- Wayne Snyder, MCDBA, SQL =Server MVPMariner, Charlotte, NCwww.mariner-usa.com(Please respond only to the newsgroups.)
I support the Professional =Association of SQL Server (PASS) and it'scommunity of SQL Server =professionals.www.sqlpass.org
"Helmut Knappe"
--=_NextPart_000_000E_01C4BD93.160672A0--|||This is a multi-part message in MIME format.
--=_NextPart_000_0080_01C4BD8D.F3B2DB80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I guess the best place to go would be here
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/RSINST=
ALL/htm/gs_ins_overview_v1_3rky.asp
-- Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Helmut Knappe" <HK_noSPAM@.biware.com> wrote in message =news:clsolg$i02$1@.svr7.m-online.net...
Hello Wayne,
thank you for your answer - no, I haven't checked these. However the =settings were correct: The check function (for 404) was cleared already. =For the http 500 error there was no aspx extension, only one setting for =a * extension, but I guess this covers all. This was pointing to the =1.1.4322 directory.
I'm about to re-install whatever is needed to make it work. The =questions are:
1. What should I re-install ?
- Reporting Services
- SQL Server
- .NET framework
- ... ?
- Windows XP
2. which service packs should I use?
- Windows XP SP 2
- SQL Server 3a
- Reporting Services SP 1
- ...
3. in which sequence should I re-install?
4. which accounts should I use for what?
Any answer pointing in the right direction, to the right document etc. =is welcome.
Regards,
Helmut
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> schrieb im =Newsbeitrag news:%23dx8roOvEHA.2116@.TK2MSFTNGP14.phx.gbl...
Forgive if you have already tried these:... I looked for a dot net =framework security thing, but couldn't find it... It seems like I had to =go to dot not config and set up an application security piece at one =time... Sorry but I could not find any info on that ( perhaps I =remember incorrectly.)
HTTP 404 File or directory not found
This error indicates that there is a problem with the virtual =directory configuration. In IIS, navigate to the report server virtual =directory, and right-click Properties. On the Virtual Directory tab, =click Configuration, select the extension, and click Edit. Make sure =that Check that the file exists (or Verify that the file exists) is =cleared.
HTTP 500 Internal server error
Reporting Services requires version 1.1.4322 of the .NET Framework. =This error can occur when the report server or Report Manager virtual =directories are mapped to version 1.0.3705. To check the application =mapping, navigate to the report server virtual directory, and =right-click Properties. On the Virtual Directory tab, click =Configuration, scroll to the .aspx extension, and read the Executable =Path value. If it is set to v1.0.3705, you must configure the virtual =directory to use 1.1.4322. Follow the instructions provided in Knowledge =Base Article 306005 to map v1.1.4322 to IIS.
-- Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Helmut Knappe" <HK_noSPAM@.biware.com> wrote in message =news:clq9mt$ari$1@.svr7.m-online.net...
> Hi all,
> > RS first did work for me after installation on my notebook, but =some silly
> changes of our network admin ruined everything:
> > RS does not run any more, gave me some access denied errors. =Complete RS
> Re-Installation told me at the end that it could not initialize =RS: "Setup
> could not initialize the Report Server - you must manually =initialize Report
> server before using it for the first time." But Rsactivate did not =cure it.
> It give an "
> Error starting Webservice:
> The Reportserver Webservice has not generated a public key. The =service was
> eventually not started successfully. See Log files for further =Information.
> I did look into the log files and work along half a dozen =knowledgebase
> articles and re-installed RS several times and even .NET =framework. NO
> SUCCESS. Answers in this newsgroup DID NOT HELP. I've noticed =several
> requests for the same problem - there was NEVER an answer that =lead to a
> successful solution.
> > I cannot access localhost reportserver. It keeps reporting access =rights
> problems all time. Yesterday, after looking at the .LOG files =again I gave
> full access rights to the Reporting Services directories and =everything
> below to the LOCAL SERVICE and the SYSTEM accounts. NO SUCCESS =again:
> > RS is running, but when I launch localhost/reportserver I get the =following
> (translated from German):
> Server error in application '/ReportServer'.
> --
> Program directory 'C:\Program files\Microsoft SQL =Server\MSSQL\Reporting
> Services\ReportServer\' cannot be accessed. The directory is not =available
> or it cannot be accessed because of safety settings.
> Description: When executing the current Web request an unprocessed =error
> occurred. Check Batch control to display further Information on =this error
> and find out where in the Code the error was caused.
> > Exception details: System.Web.HttpException: Program directory ='C:\Program
> files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\' =cannot be
> accessed. The directory is not available or it cannot be accessed =because of
> safety settings.
> > Source error:
> When executing the current Web request an unprocessed error =occurred.
> Information on the source and the Position of the exception can be =displayed
> using the exception batch control.
> > batch control:
> [HttpException (0x80004005): Program directory 'C:\Program =files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\' cannot be =accessed. The
> directory is not available or it cannot be accessed because of =safety
> settings.]
> System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) =+263
> [HttpException (0x80004005): ASP.NET-Initialisation error]
> System.Web.HttpRuntime.FirstRequestInit(HttpContext context) =+964
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest =wr) +128
> --
> Version information: Microsoft .NET Framework =Version:1.1.4322.573;
> ASP.NET-Version:1.1.4322.573
> > ASP.NET is working - I tested it by running a sample application =of ChartFX.
> I even did remove the write protection from these directories: =same result.
> > > Today I did establish full rights for IWAM, IUSR and ASPNET. And I =did set
> the default website to (All Unassigned). NO CHANGE.
> > Now I have reached the end of the road. Please someone tell me the =right way
> how to define the access rights correctly, and in which sequence, =in my
> case for having
> RS and SQL Server and AS installed together on 1 machine (XP pro).
> > Any comments appreciated.
> Helmut
> > > > >
--=_NextPart_000_0080_01C4BD8D.F3B2DB80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I guess the best place to go would be here
http://msdn.microsoft.com/li=brary/default.asp?url=3D/library/en-us/RSINSTALL/htm/gs_ins_overview_v1_3=rky.asp
-- Wayne Snyder, MCDBA, SQL Server MVPMariner, =Charlotte, NChttp://www.mariner-usa.com">www.mariner-usa.com(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it'scommunity of SQL Server professionals.http://www.sqlpass.org">www.sqlpass.org
"Helmut Knappe"
Hello Wayne,
thank you for your answer - no, I =haven't checked these. However the settings were correct: The check function =(for 404) was cleared already. For the http 500 error there was no aspx =extension, only one setting for a * extension, but I guess this covers all. This =was pointing to the 1.1.4322 directory.
I'm about to re-install whatever is =needed to make it work. The questions are:
1. What should I re-install =?
- Reporting Services
- SQL =Server
- .NET =framework
- ... =?
- Windows =XP
2. which service packs should I =use?
- Windows XP SP =2
- SQL Server =3a
- Reporting =Services SP 1
- ...
3. in which sequence should I re-install?
4. which accounts should I use for what?
Any answer pointing in the right =direction, to the right document etc. is welcome.
Regards,
Helmut
"Wayne Snyder"
Forgive if you have already tried these:... I =looked for a dot net framework security thing, but couldn't find it... It seems =like I had to go to dot not config and set up an application security piece =at one time... Sorry but I could not find any info on that ( perhaps I =remember incorrectly.)
HTTP 404 File or directory not =found
This error indicates that there is a =problem with the virtual directory configuration. In IIS, navigate to the report =server virtual directory, and right-click Properties. On the Virtual =Directory tab, click Configuration, select the extension, and click Edit. Make sure =that Check that the file exists (or Verify that the file exists) is cleared.
HTTP 500 Internal server =error
Reporting Services requires version =1.1.4322 of the .NET Framework. This error can occur when the report server or =Report Manager virtual directories are mapped to version 1.0.3705. To check =the application mapping, navigate to the report server virtual =directory, and right-click Properties. On the Virtual Directory tab, click =Configuration, scroll to the .aspx extension, and read the Executable Path value. =If it is set to v1.0.3705, you must configure the virtual directory to use =1.1.4322. Follow the instructions provided in Knowledge Base Article 306005 to =map v1.1.4322 to IIS.
-- Wayne Snyder, MCDBA, SQL =Server MVPMariner, Charlotte, NCwww.mariner-usa.com(Please respond only to the newsgroups.)
I support the Professional =Association of SQL Server (PASS) and it'scommunity of SQL Server professionals.www.sqlpass.org
"Helmut Knappe"
--=_NextPart_000_0080_01C4BD8D.F3B2DB80--
No comments:
Post a Comment