SQL Remove Old Backups: http

Showing posts with label http. Show all posts

Sunday, March 25, 2012

32 GB of Memory

Accroding to the following Article:
http://support.microsoft.com/?id=274750
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32 GB
of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB of
physical RAM by using the Physical Address Extensions (PAE) feature. You can
use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
This statement is a bit confusing. I am going to be upgrading our servers
from SP3a to SP4. I am planning to implement this on windows server 2003
Enterprise Edition. Will I be able to allocate 32 GB of memory to this
server. If so what steps do I take. Also will there be any limitations.
Also if there is any other documentation regarding this. Let me know.In BOOT.INI add the /PAE switch and do not use the /3GB switch. Reboot.
In SQL Server, run:
sp_configure 'awe enabled', 1
go
reconfigure with override
go
sp_configure 'min server memory (MB)', 30720
go
reconfigure with override
go
Stop and start SQL Server.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"JDS" <JDS@.discussions.microsoft.com> wrote in message
news:9449E5A9-D31E-4C5B-86C8-86B5E3686AFC@.microsoft.com...
Accroding to the following Article:
http://support.microsoft.com/?id=274750
Note The maximum amount of memory that can be supported on Windows Server
2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32 GB
of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB of
physical RAM by using the Physical Address Extensions (PAE) feature. You can
use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
Microsoft Windows Server 2003 Datacenter Edition.
This statement is a bit confusing. I am going to be upgrading our servers
from SP3a to SP4. I am planning to implement this on windows server 2003
Enterprise Edition. Will I be able to allocate 32 GB of memory to this
server. If so what steps do I take. Also will there be any limitations.
Also if there is any other documentation regarding this. Let me know.|||Tom
> sp_configure 'min server memory (MB)', 30720
Should it be max memory?
JDS
In addition to Tom's suggestion do not forget to download hotfix for SP4
http://support.microsoft.com/kb/899761
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ujghB0KyHHA.5592@.TK2MSFTNGP04.phx.gbl...
> In BOOT.INI add the /PAE switch and do not use the /3GB switch. Reboot.
> In SQL Server, run:
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'min server memory (MB)', 30720
> go
> reconfigure with override
> go
> Stop and start SQL Server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "JDS" <JDS@.discussions.microsoft.com> wrote in message
> news:9449E5A9-D31E-4C5B-86C8-86B5E3686AFC@.microsoft.com...
> Accroding to the following Article:
> http://support.microsoft.com/?id=274750
> Note The maximum amount of memory that can be supported on Windows Server
> 2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
> GB
> of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB of
> physical RAM by using the Physical Address Extensions (PAE) feature. You
> can
> use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
> Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
> Microsoft Windows Server 2003 Datacenter Edition.
>
> This statement is a bit confusing. I am going to be upgrading our servers
> from SP3a to SP4. I am planning to implement this on windows server 2003
> Enterprise Edition. Will I be able to allocate 32 GB of memory to this
> server. If so what steps do I take. Also will there be any limitations.
> Also if there is any other documentation regarding this. Let me know.
>|||Correct. Looks like my cut and paste missed the mark. :-(
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ORxSH0QyHHA.988@.TK2MSFTNGP02.phx.gbl...
Tom
> sp_configure 'min server memory (MB)', 30720
Should it be max memory?
JDS
In addition to Tom's suggestion do not forget to download hotfix for SP4
http://support.microsoft.com/kb/899761
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ujghB0KyHHA.5592@.TK2MSFTNGP04.phx.gbl...
> In BOOT.INI add the /PAE switch and do not use the /3GB switch. Reboot.
> In SQL Server, run:
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'min server memory (MB)', 30720
> go
> reconfigure with override
> go
> Stop and start SQL Server.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "JDS" <JDS@.discussions.microsoft.com> wrote in message
> news:9449E5A9-D31E-4C5B-86C8-86B5E3686AFC@.microsoft.com...
> Accroding to the following Article:
> http://support.microsoft.com/?id=274750
> Note The maximum amount of memory that can be supported on Windows Server
> 2003 is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32
> GB
> of physical RAM. Windows Server 2003 Datacenter Edition supports 64 GB of
> physical RAM by using the Physical Address Extensions (PAE) feature. You
> can
> use the 3 GB switch that is in the Boot.ini file with Microsoft Windows
> Server 2003, Microsoft Windows Server 2003 Enterprise Edition, or with
> Microsoft Windows Server 2003 Datacenter Edition.
>
> This statement is a bit confusing. I am going to be upgrading our servers
> from SP3a to SP4. I am planning to implement this on windows server 2003
> Enterprise Edition. Will I be able to allocate 32 GB of memory to this
> server. If so what steps do I take. Also will there be any limitations.
> Also if there is any other documentation regarding this. Let me know.
>|||What makes me more confused is your mention of "I am going to be
upgrading our servers from SP3a to SP4. ", any specific reason you
mentioned it, because you can allocate 32 GB of memory even if you are
on SP3a. Also you should be aware of Hot Add memory
Also just to add to Tom's reply, make sure you apply hotfix on SP4 for
AWE:
899761 FIX: Not all memory is available when AWE is enabled on a
computer that is running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/default.aspx?scid=kb;EN-US;899761|||Is it possible to take advantage of the additional memory on Windows Server
2000 Enterprise edition or 2003 only?
"dinu_babu@.hotmail.com" wrote:
> What makes me more confused is your mention of "I am going to be
> upgrading our servers from SP3a to SP4. ", any specific reason you
> mentioned it, because you can allocate 32 GB of memory even if you are
> on SP3a. Also you should be aware of Hot Add memory
> Also just to add to Tom's reply, make sure you apply hotfix on SP4 for
> AWE:
> 899761 FIX: Not all memory is available when AWE is enabled on a
> computer that is running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;899761
>
>

Saturday, February 11, 2012

2005 Database Mirroring & Witness

I'm devlving into 2005 and specifically mirroring.

Having read the following article (
http://www.microsoft.com/technet/pr...5/dbmirror.mspx ),
is mirroring a sensible option as it indicates that it should not be
used in a production environment, yet the SQL2005 seminars I've been to
indicate that this is a worthy option.

Do we also need a witness server, or can this be done (sensibly) with
two SQL2005 servers ?

Currently we have 2xSQL2000 (clustered) servers and a SAN for the data.
If we go down the route of mirroring, it looks like we can get rid of
the SAN and Cluster and use the mirroring instead.

Any advice on the pro's / cons would be appreciated.

Thanks

RyanRyan,

I haven't done too much with mirroring yet but

> Do we also need a witness server, or can this be done (sensibly) with
> two SQL2005 servers ?

It is physically possible to do this with 2 servers (in fact it is
physically possible to do it on 1 server) but it really doesn't make sense.
The server can only be live if it has a quorum (2 out of 3) agree that it is
the live server. If the primary server is one machine and the second
machine contains the mirror server and the witness server both and the
second machine goes off-line you have effectively taken the primary server
off-line as well since it will no longer have a quorum.

HTH,
John|||"Ryan" <ryanofford@.hotmail.com> wrote in message
news:1142346007.542792.217730@.e56g2000cwe.googlegr oups.com...
> I'm devlving into 2005 and specifically mirroring.
> Having read the following article (
> http://www.microsoft.com/technet/pr...5/dbmirror.mspx ),
> is mirroring a sensible option as it indicates that it should not be
> used in a production environment, yet the SQL2005 seminars I've been to
> indicate that this is a worthy option.

It's worth playing with.

BUT, it's beta. Which means if you use it in a production evironment and
something goes wrong, the amount of support that MS will provide is limited.

> Do we also need a witness server, or can this be done (sensibly) with
> two SQL2005 servers ?

Generally you should have a witness.

> Currently we have 2xSQL2000 (clustered) servers and a SAN for the data.
> If we go down the route of mirroring, it looks like we can get rid of
> the SAN and Cluster and use the mirroring instead.
> Any advice on the pro's / cons would be appreciated.
> Thanks
>
> Ryan|||What do we need licence wise for the witness server ? Will we be able
to use a standard licence ?|||You can use any edition for the witness.

--
Tom

----------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Ryan" <ryanofford@.hotmail.com> wrote in message
news:1142422233.452068.120450@.z34g2000cwc.googlegr oups.com...
What do we need licence wise for the witness server ? Will we be able
to use a standard licence ?|||Ryan,

> What do we need licence wise for the witness server ? Will we be able
> to use a standard licence ?

The witness can be any edition of SQL Server 2005 including the free Express
Edition.

HTH,
John

2003 Server SP1 broke Reporting Services

Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
request failed with HTTP status 401: Unauthorized." I've re-set the database
credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
Any help would be appreciated.Sounds like ASP.NET permissions issue. What is the application pool set to
run as?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"geoff" <geoff@.discussions.microsoft.com> wrote in message
news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> "The
> request failed with HTTP status 401: Unauthorized." I've re-set the
> database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> it.
> Any help would be appreciated.|||It is set to run as Network Service account. The ReportServer service is in
fact running as Network Service.
"Brian Welcker [MSFT]" wrote:
> Sounds like ASP.NET permissions issue. What is the application pool set to
> run as?
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "geoff" <geoff@.discussions.microsoft.com> wrote in message
> news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > "The
> > request failed with HTTP status 401: Unauthorized." I've re-set the
> > database
> > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > it.
> > Any help would be appreciated.
>
>|||Hi,
I get the same thing running SQL Server Reporting Services SP 1 on Server
2003 Enterprise Edition with SP 1.
The location of SQLRS is non-standard in that the site running SQLRS will
only respond to a FQDN through the host header. It all worked before so I
know it is not a configuration issue.
You can see the reports folder by entering http://xxx.xxxxx.xxx/reportserver
and then navigating to a report. Also, the scheduled report tasks run ok.
Here is a copy of the error from the log:
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.878.00</Product>
<Locale>en-US</Locale>
<TimeZone>GMT Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
<SystemName>SWIPER</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing MaxScheduleWait
to default value of '1' second(s) because it was not specified in
Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
DatabaseQueryTimeout to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing InstanceName to
default value of 'MSSQLSERVER.1' because it was not specified in
Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
ProcessRecycleOptions to default value of '0' because it was not specified
in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsScavengerCycle to default value of '30' second(s) because it
was not specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsDbCycle to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
RunningRequestsAge to default value of '30' second(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
CleanupCycleMinutes to default value of '10' minute(s) because it was not
specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
SecureConnectionLevel to default value of '1' because it was not specified
in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
WebServiceUseFileShareStorage to default value of 'False' because it was not
specified in Configuration file.
w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
status 401: Unauthorized.
w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 401:
Unauthorized.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!1b70!02/04/2005-09:20:58:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)
Cheers
Glen
"geoff" wrote:
> It is set to run as Network Service account. The ReportServer service is in
> fact running as Network Service.
> "Brian Welcker [MSFT]" wrote:
> > Sounds like ASP.NET permissions issue. What is the application pool set to
> > run as?
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > > "The
> > > request failed with HTTP status 401: Unauthorized." I've re-set the
> > > database
> > > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > > it.
> > > Any help would be appreciated.
> >
> >
> >|||I can browse as you suggest and the scheduled reports do run. I can browse
the reports folder as you suggest through .../reportserver, but I can do so
without using the FQDN as well. I can't get anything to work with .../reports
I have my SQL Report Server database on another box...don't know if this is
impacting anything.
Hopefully MSFT will help us out on this one.
"GlenConway" wrote:
> Hi,
> I get the same thing running SQL Server Reporting Services SP 1 on Server
> 2003 Enterprise Edition with SP 1.
> The location of SQLRS is non-standard in that the site running SQLRS will
> only respond to a FQDN through the host header. It all worked before so I
> know it is not a configuration issue.
> You can see the reports folder by entering http://xxx.xxxxx.xxx/reportserver
> and then navigating to a report. Also, the scheduled report tasks run ok.
> Here is a copy of the error from the log:
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.878.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>GMT Daylight Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> <SystemName>SWIPER</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing MaxScheduleWait
> to default value of '1' second(s) because it was not specified in
> Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> DatabaseQueryTimeout to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing InstanceName to
> default value of 'MSSQLSERVER.1' because it was not specified in
> Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> ProcessRecycleOptions to default value of '0' because it was not specified
> in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsScavengerCycle to default value of '30' second(s) because it
> was not specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsDbCycle to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> RunningRequestsAge to default value of '30' second(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> CleanupCycleMinutes to default value of '10' minute(s) because it was not
> specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> SecureConnectionLevel to default value of '1' because it was not specified
> in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> DisplayErrorLink to 'True' as specified in Configuration file.
> w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> WebServiceUseFileShareStorage to default value of 'False' because it was not
> specified in Configuration file.
> w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> status 401: Unauthorized.
> w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 401:
> Unauthorized.
> at
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!1b70!02/04/2005-09:20:58:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
> Cheers
> Glen
>
> "geoff" wrote:
> > It is set to run as Network Service account. The ReportServer service is in
> > fact running as Network Service.
> >
> > "Brian Welcker [MSFT]" wrote:
> >
> > > Sounds like ASP.NET permissions issue. What is the application pool set to
> > > run as?
> > >
> > > --
> > > Brian Welcker
> > > Group Program Manager
> > > Microsoft SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now get
> > > > "The
> > > > request failed with HTTP status 401: Unauthorized." I've re-set the
> > > > database
> > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find
> > > > it.
> > > > Any help would be appreciated.
> > >
> > >
> > >|||Same here,
same error, sysadmin is unauthorized to http://localhost/Reports,
I can browse and see the files...
any suggestion other than uninstall the SP1?
Thank you,
--
ejr
"geoff" <geoff@.discussions.microsoft.com> wrote in message
news:97FDD47E-4BCD-4A15-8FD0-B342920FAD78@.microsoft.com...
> I can browse as you suggest and the scheduled reports do run. I can
browse
> the reports folder as you suggest through .../reportserver, but I can do
so
> without using the FQDN as well. I can't get anything to work with
.../reports
> I have my SQL Report Server database on another box...don't know if this
is
> impacting anything.
> Hopefully MSFT will help us out on this one.
> "GlenConway" wrote:
> > Hi,
> >
> > I get the same thing running SQL Server Reporting Services SP 1 on
Server
> > 2003 Enterprise Edition with SP 1.
> >
> > The location of SQLRS is non-standard in that the site running SQLRS
will
> > only respond to a FQDN through the host header. It all worked before so
I
> > know it is not a configuration issue.
> >
> > You can see the reports folder by entering
http://xxx.xxxxx.xxx/reportserver
> > and then navigating to a report. Also, the scheduled report tasks run
ok.
> >
> > Here is a copy of the error from the log:
> >
> > <Header>
> > <Product>Microsoft SQL Server Reporting Services Version
> > 8.00.878.00</Product>
> > <Locale>en-US</Locale>
> > <TimeZone>GMT Daylight Time</TimeZone>
> > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> > <SystemName>SWIPER</SystemName>
> > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > <OSVersion>5.2.3790.0</OSVersion>
> > </Header>
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
MaxScheduleWait
> > to default value of '1' second(s) because it was not specified in
> > Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > DatabaseQueryTimeout to default value of '30' second(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
InstanceName to
> > default value of 'MSSQLSERVER.1' because it was not specified in
> > Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > ProcessRecycleOptions to default value of '0' because it was not
specified
> > in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsScavengerCycle to default value of '30' second(s) because
it
> > was not specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsDbCycle to default value of '30' second(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > RunningRequestsAge to default value of '30' second(s) because it was not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > CleanupCycleMinutes to default value of '10' minute(s) because it was
not
> > specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > SecureConnectionLevel to default value of '1' because it was not
specified
> > in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > DisplayErrorLink to 'True' as specified in Configuration file.
> > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > WebServiceUseFileShareStorage to default value of 'False' because it
was not
> > specified in Configuration file.
> > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> > status 401: Unauthorized.
> > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The request failed with HTTP status 401:
> > Unauthorized.
> > at
> >
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
Message
> > message, WebResponse response, Stream responseStream, Boolean asyncCall)
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at
> >
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level)
> > at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args)
> > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > at System.Web.UI.Control.OnInit(EventArgs e)
> > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!1b70!02/04/2005-09:20:58:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)
> >
> > Cheers
> >
> > Glen
> >
> >
> > "geoff" wrote:
> >
> > > It is set to run as Network Service account. The ReportServer service
is in
> > > fact running as Network Service.
> > >
> > > "Brian Welcker [MSFT]" wrote:
> > >
> > > > Sounds like ASP.NET permissions issue. What is the application pool
set to
> > > > run as?
> > > >
> > > > --
> > > > Brian Welcker
> > > > Group Program Manager
> > > > Microsoft SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > > >
> > > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now
get
> > > > > "The
> > > > > request failed with HTTP status 401: Unauthorized." I've re-set
the
> > > > > database
> > > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem
to find
> > > > > it.
> > > > > Any help would be appreciated.
> > > >
> > > >
> > > >|||Getting the same problem also on one of our test machines.
"ejr" wrote:
> Same here,
> same error, sysadmin is unauthorized to http://localhost/Reports,
> I can browse and see the files...
> any suggestion other than uninstall the SP1?
> Thank you,
> --
> ejr
>
> "geoff" <geoff@.discussions.microsoft.com> wrote in message
> news:97FDD47E-4BCD-4A15-8FD0-B342920FAD78@.microsoft.com...
> > I can browse as you suggest and the scheduled reports do run. I can
> browse
> > the reports folder as you suggest through .../reportserver, but I can do
> so
> > without using the FQDN as well. I can't get anything to work with
> .../reports
> >
> > I have my SQL Report Server database on another box...don't know if this
> is
> > impacting anything.
> >
> > Hopefully MSFT will help us out on this one.
> >
> > "GlenConway" wrote:
> >
> > > Hi,
> > >
> > > I get the same thing running SQL Server Reporting Services SP 1 on
> Server
> > > 2003 Enterprise Edition with SP 1.
> > >
> > > The location of SQLRS is non-standard in that the site running SQLRS
> will
> > > only respond to a FQDN through the host header. It all worked before so
> I
> > > know it is not a configuration issue.
> > >
> > > You can see the reports folder by entering
> http://xxx.xxxxx.xxx/reportserver
> > > and then navigating to a report. Also, the scheduled report tasks run
> ok.
> > >
> > > Here is a copy of the error from the log:
> > >
> > > <Header>
> > > <Product>Microsoft SQL Server Reporting Services Version
> > > 8.00.878.00</Product>
> > > <Locale>en-US</Locale>
> > > <TimeZone>GMT Daylight Time</TimeZone>
> > > <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> > > Services\LogFiles\ReportServerWebApp__04_02_2005_09_20_40.log</Path>
> > > <SystemName>SWIPER</SystemName>
> > > <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> > > <OSVersion>5.2.3790.0</OSVersion>
> > > </Header>
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration
> file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> MaxScheduleWait
> > > to default value of '1' second(s) because it was not specified in
> > > Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > DatabaseQueryTimeout to default value of '30' second(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> InstanceName to
> > > default value of 'MSSQLSERVER.1' because it was not specified in
> > > Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > ProcessRecycleOptions to default value of '0' because it was not
> specified
> > > in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsScavengerCycle to default value of '30' second(s) because
> it
> > > was not specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsDbCycle to default value of '30' second(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > RunningRequestsAge to default value of '30' second(s) because it was not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > CleanupCycleMinutes to default value of '10' minute(s) because it was
> not
> > > specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > SecureConnectionLevel to default value of '1' because it was not
> specified
> > > in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > DisplayErrorLink to 'True' as specified in Configuration file.
> > > w3wp!library!1b70!02/04/2005-09:20:40:: i INFO: Initializing
> > > WebServiceUseFileShareStorage to default value of 'False' because it
> was not
> > > specified in Configuration file.
> > > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: The request failed with HTTP
> > > status 401: Unauthorized.
> > > w3wp!ui!1b70!02/04/2005-09:20:47:: e ERROR: HTTP status code --> 500
> > > --Details--
> > > System.Net.WebException: The request failed with HTTP status 401:
> > > Unauthorized.
> > > at
> > >
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> Message
> > > message, WebResponse response, Stream responseStream, Boolean asyncCall)
> > > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > > methodName, Object[] parameters)
> > > at
> > >
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > > at
> Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > > at
> > > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > > methodname)
> > > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > > at
> > > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > > level)
> > > at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > > sender, EventArgs args)
> > > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > > at System.Web.UI.Control.OnInit(EventArgs e)
> > > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > > at System.Web.UI.Page.ProcessRequestMain()
> > > w3wp!ui!1b70!02/04/2005-09:20:58:: e ERROR: Exception in ShowErrorPage:
> > > System.Threading.ThreadAbortException: Thread was being aborted.
> > > at System.Threading.Thread.AbortInternal()
> > > at System.Threading.Thread.Abort(Object stateInfo)
> > > at System.Web.HttpResponse.End()
> > > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > > errMsg) at at System.Threading.Thread.AbortInternal()
> > > at System.Threading.Thread.Abort(Object stateInfo)
> > > at System.Web.HttpResponse.End()
> > > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> > > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > > errMsg)
> > >
> > > Cheers
> > >
> > > Glen
> > >
> > >
> > > "geoff" wrote:
> > >
> > > > It is set to run as Network Service account. The ReportServer service
> is in
> > > > fact running as Network Service.
> > > >
> > > > "Brian Welcker [MSFT]" wrote:
> > > >
> > > > > Sounds like ASP.NET permissions issue. What is the application pool
> set to
> > > > > run as?
> > > > >
> > > > > --
> > > > > Brian Welcker
> > > > > Group Program Manager
> > > > > Microsoft SQL Server Reporting Services
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > > >
> > > > > "geoff" <geoff@.discussions.microsoft.com> wrote in message
> > > > > news:B8F8971D-B8D8-4FDF-8E3F-980B20327DA5@.microsoft.com...
> > > > > > Installation of WS2003SP1 broke reporting services SP2Beta. I now
> get
> > > > > > "The
> > > > > > request failed with HTTP status 401: Unauthorized." I've re-set
> the
> > > > > > database
> > > > > > credentials via RSCONFIG. I think it's in IIS, but I can't seem
> to find
> > > > > > it.
> > > > > > Any help would be appreciated.
> > > > >
> > > > >
> > > > >
>
>|||Hi Guys,
Microsoft resolved this problem for us. We created a DWORD entry called
DisableLoopbackCheck to HKLM\System\CurrentControlSet\Control\Lsa. Setting
this key to a value of 1 fixed our issue.
For more information, see:
http://flarepath.blogspot.com/2005/04/2003-service-pack-1-and-sql-server.html
Thanks
Glen
"geoff" wrote:
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> request failed with HTTP status 401: Unauthorized." I've re-set the database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> Any help would be appreciated.|||Did the suggestion from GlenConway work for you? If not, I have another
solution that may work for you.
"geoff" wrote:
> Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> request failed with HTTP status 401: Unauthorized." I've re-set the database
> credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> Any help would be appreciated.|||adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
Any other suggestions?|||Thanks for the link Glen, this resolve my problem.
"GlenConway" wrote:
> Hi Guys,
> Microsoft resolved this problem for us. We created a DWORD entry called
> DisableLoopbackCheck to HKLM\System\CurrentControlSet\Control\Lsa. Setting
> this key to a value of 1 fixed our issue.
> For more information, see:
> http://flarepath.blogspot.com/2005/04/2003-service-pack-1-and-sql-server.html
> Thanks
> Glen
> "geoff" wrote:
> > Installation of WS2003SP1 broke reporting services SP2Beta. I now get "The
> > request failed with HTTP status 401: Unauthorized." I've re-set the database
> > credentials via RSCONFIG. I think it's in IIS, but I can't seem to find it.
> > Any help would be appreciated.|||I'm also looking for other option/suggestion.
The Report Manager works fine for adding role/user to reports/folders, but
the same operation in RS API has the 401 error. Other OS works fine too just
this 2003 SP1 machine.
Thanks,
Lianghong
"Khubieb" wrote:
> adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> Any other suggestions?|||Me too! We are able to access everything through
http://ServerName/reportserver but cannot get thru to
http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
Even after applying the Registry change AND rebooting the server, we are
still down. This is a production server with 100s of users - phone ringing
off the hook...any ideas?
Note that we have found some users are able to access the Reports Manager
while others are not... not sure why. We are continuing to work with IIS
security but nothing has been changed recently.
"Lianghong" wrote:
> I'm also looking for other option/suggestion.
> The Report Manager works fine for adding role/user to reports/folders, but
> the same operation in RS API has the 401 error. Other OS works fine too just
> this 2003 SP1 machine.
> Thanks,
> Lianghong
> "Khubieb" wrote:
> > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > Any other suggestions?|||What finally fixed this for us was going into IIS and for the 'ReportServer'
folder, we removed all permissions and then added them all back. After doing
this, the Reports Manager worked again for everyone.
We didn't change anything or give any new permissions, just removed and
re-added the permissions that were already there.
We are very concerned this will happen again in the future as we had done
nothing to that server in several days and this happenned apparently
unprovoked. It appears to be an IIS security issue - not a Reporting Services
issue.
"MoranTugTom" wrote:
> Me too! We are able to access everything through
> http://ServerName/reportserver but cannot get thru to
> http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
> Even after applying the Registry change AND rebooting the server, we are
> still down. This is a production server with 100s of users - phone ringing
> off the hook...any ideas?
> Note that we have found some users are able to access the Reports Manager
> while others are not... not sure why. We are continuing to work with IIS
> security but nothing has been changed recently.
> "Lianghong" wrote:
> > I'm also looking for other option/suggestion.
> > The Report Manager works fine for adding role/user to reports/folders, but
> > the same operation in RS API has the 401 error. Other OS works fine too just
> > this 2003 SP1 machine.
> >
> > Thanks,
> > Lianghong
> >
> > "Khubieb" wrote:
> >
> > > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > > Any other suggestions?|||I tried this as well with no avail. Still get 'cannot connect to data source'
when running report (with my user logged in). If I use windows it flys with
the same account. just doesn't make any sense.
"MoranTugTom" wrote:
> What finally fixed this for us was going into IIS and for the 'ReportServer'
> folder, we removed all permissions and then added them all back. After doing
> this, the Reports Manager worked again for everyone.
> We didn't change anything or give any new permissions, just removed and
> re-added the permissions that were already there.
> We are very concerned this will happen again in the future as we had done
> nothing to that server in several days and this happenned apparently
> unprovoked. It appears to be an IIS security issue - not a Reporting Services
> issue.
>
> "MoranTugTom" wrote:
> > Me too! We are able to access everything through
> > http://ServerName/reportserver but cannot get thru to
> > http://ServerName/reports. Keeps giving us the "401: Unauthorized" error.
> > Even after applying the Registry change AND rebooting the server, we are
> > still down. This is a production server with 100s of users - phone ringing
> > off the hook...any ideas?
> >
> > Note that we have found some users are able to access the Reports Manager
> > while others are not... not sure why. We are continuing to work with IIS
> > security but nothing has been changed recently.
> >
> > "Lianghong" wrote:
> >
> > > I'm also looking for other option/suggestion.
> > > The Report Manager works fine for adding role/user to reports/folders, but
> > > the same operation in RS API has the 401 error. Other OS works fine too just
> > > this 2003 SP1 machine.
> > >
> > > Thanks,
> > > Lianghong
> > >
> > > "Khubieb" wrote:
> > >
> > > > adding the "DisableLoopbackCheck" DWORD entry with its value set to "1" under
> > > > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" didn't work for me.
> > > > Any other suggestions?

Sunday, March 25, 2012

32 GB of Memory

Saturday, February 11, 2012

2005 Database Mirroring & Witness

2003 Server SP1 broke Reporting Services

Thursday, February 9, 2012

2003 Server SP1 broke Reporting Services

SQL Remove Old Backups

Blog Archive

About Me