2nd Try: Restore Database Dialog missing Backups (Archive BIT)

I have a strange problem with restoring files. I have one SQL server
installation that does not show any .BAK files that no longer have the
archive bit set. Is there a switch somewhere that I can throw to
change this back?
I have 3 other SQL server installations in different places that do
not have this issue.
Thanks,
Doug"Doug Crabtree" <not@.gonna.tell> wrote in message
news:GPKdnbA9tLgxur_cRVn-rw@.comcast.com...
> I have a strange problem with restoring files. I have one SQL server
> installation that does not show any .BAK files that no longer have the
> archive bit set. Is there a switch somewhere that I can throw to
> change this back?
> I have 3 other SQL server installations in different places that do
> not have this issue.
You can change the archive bit from a command prompt with the ATTRIB
command. It sounds like you may have backup software running that is
resetting the bit. This should not prevent you from restoring any backup
files, perhaps there is something else going on here?
Steve|||I can reset the bit, our backup is indeed changing it.
But the problem remains that the dialog that shows the backups does not show
those without the bit. Only 1 server does it. All our other servers show
it regardless of the archive bit. I was just hoping somebody out there knew
why this was happening.
Thanks,
Doug
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:%23qtYktIhEHA.2908@.TK2MSFTNGP10.phx.gbl...
> You can change the archive bit from a command prompt with the ATTRIB
> command. It sounds like you may have backup software running that is
> resetting the bit. This should not prevent you from restoring any backup
> files, perhaps there is something else going on here?
> Steve
>|||AFAIK, the restore dialog doesn't care at all whether the backup files archive bit is set or not.
Actually, it doesn't even care whether the file in question *exists*. My guess is that your problem
is elsewhere. You might want to troubleshoot this by doing a backup, verify that EM show this, set
the archive bit and check EM again.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Doug Crabtree" <not@.gonna.tell> wrote in message news:tcydnc2FZ7rZ_r_cRVn-vQ@.comcast.com...
> I can reset the bit, our backup is indeed changing it.
> But the problem remains that the dialog that shows the backups does not show
> those without the bit. Only 1 server does it. All our other servers show
> it regardless of the archive bit. I was just hoping somebody out there knew
> why this was happening.
> Thanks,
> Doug
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:%23qtYktIhEHA.2908@.TK2MSFTNGP10.phx.gbl...
> > You can change the archive bit from a command prompt with the ATTRIB
> > command. It sounds like you may have backup software running that is
> > resetting the bit. This should not prevent you from restoring any backup
> > files, perhaps there is something else going on here?
> >
> > Steve
> >
> >
>|||I have tried that. It dissapears from the selection dialog when the archive
bit is not set. When set, it appears again.
Strange...
Thanks anyway,
Doug
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ePeJe3OhEHA.3272@.TK2MSFTNGP11.phx.gbl...
> AFAIK, the restore dialog doesn't care at all whether the backup files
archive bit is set or not.
> Actually, it doesn't even care whether the file in question *exists*. My
guess is that your problem
> is elsewhere. You might want to troubleshoot this by doing a backup,
verify that EM show this, set
> the archive bit and check EM again.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/|||Strange indeed. Can you point me to exactly what dialog you refer to (how to you "click" to get
there) and I'll give it a spin. I've never encountered this, or even thought about the archive bit
being relevant...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Doug Crabtree" <not@.gonna.tell> wrote in message news:nOOdnVUDjKWVzr7cRVn-qA@.comcast.com...
> I have tried that. It dissapears from the selection dialog when the archive
> bit is not set. When set, it appears again.
> Strange...
> Thanks anyway,
> Doug
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:ePeJe3OhEHA.3272@.TK2MSFTNGP11.phx.gbl...
> > AFAIK, the restore dialog doesn't care at all whether the backup files
> archive bit is set or not.
> > Actually, it doesn't even care whether the file in question *exists*. My
> guess is that your problem
> > is elsewhere. You might want to troubleshoot this by doing a backup,
> verify that EM show this, set
> > the archive bit and check EM again.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
>|||In Enterprise Manager, Right click on Databases, and select All Tasks ->
Restore Database...
"Restore Database" Dialog Box
Restore as database: <<DBNAME>>
From Device selected
Restore backup set (Database - complete) selected
Click Select Devices button
"Choose Restore Devices" Dialog Box
Disk selected
Click Add button
"Choose Restore Destination" dialog box:
File Name (click the ...)
"Backup Device Location - <<SERVERNAME>>" Dialog box:
They don't show.
----
--
Interesting, though ... I copied one of the backups to another disk, turned
off the archive bit, and it showed there. Something about that drive?
Permissions? We have the Server running as an administrator's account.
Would that have anything to do with it?
Thanks,
Doug
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OtgmcOShEHA.1156@.TK2MSFTNGP10.phx.gbl...
> Strange indeed. Can you point me to exactly what dialog you refer to (how
to you "click" to get
> there) and I'll give it a spin. I've never encountered this, or even
thought about the archive bit
> being relevant...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/|||I tried your steps and I could not reproduce, the file did show, regardless of what I set the "the file is
ready for ..." option in Explorer (I assume this is the ol' archive bit).
I did a Profiler trace and it seems like EM is executing xp_dirtree to get this list. This might give you
something to go on when searching KB, Google etc.
Also, opening a case with MS might be an option.
I doubt is has anything to do with permissions. But who know...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Doug Crabtree" <not@.gonna.tell> wrote in message news:np-dnVZYZaxf9b7cRVn-ig@.comcast.com...
> In Enterprise Manager, Right click on Databases, and select All Tasks ->
> Restore Database...
> "Restore Database" Dialog Box
> Restore as database: <<DBNAME>>
> From Device selected
> Restore backup set (Database - complete) selected
> Click Select Devices button
> "Choose Restore Devices" Dialog Box
> Disk selected
> Click Add button
> "Choose Restore Destination" dialog box:
> File Name (click the ...)
> "Backup Device Location - <<SERVERNAME>>" Dialog box:
> They don't show.
> ----
> --
> Interesting, though ... I copied one of the backups to another disk, turned
> off the archive bit, and it showed there. Something about that drive?
> Permissions? We have the Server running as an administrator's account.
> Would that have anything to do with it?
> Thanks,
> Doug
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OtgmcOShEHA.1156@.TK2MSFTNGP10.phx.gbl...
> > Strange indeed. Can you point me to exactly what dialog you refer to (how
> to you "click" to get
> > there) and I'll give it a spin. I've never encountered this, or even
> thought about the archive bit
> > being relevant...
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
>|||Interesting problem indeed -- can you use the "native" T-SQL RESTORE to
perform the database restore?
Steve
"Doug Crabtree" <not@.gonna.tell> wrote in message
news:np-dnVZYZaxf9b7cRVn-ig@.comcast.com...
> In Enterprise Manager, Right click on Databases, and select All Tasks ->
> Restore Database...
> "Restore Database" Dialog Box
> Restore as database: <<DBNAME>>
> From Device selected
> Restore backup set (Database - complete) selected
> Click Select Devices button
> "Choose Restore Devices" Dialog Box
> Disk selected
> Click Add button
> "Choose Restore Destination" dialog box:
> File Name (click the ...)
> "Backup Device Location - <<SERVERNAME>>" Dialog box:
> They don't show.
> ----
--
> --
> Interesting, though ... I copied one of the backups to another disk,
turned
> off the archive bit, and it showed there. Something about that drive?
> Permissions? We have the Server running as an administrator's account.
> Would that have anything to do with it?
> Thanks,
> Doug
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:OtgmcOShEHA.1156@.TK2MSFTNGP10.phx.gbl...
> > Strange indeed. Can you point me to exactly what dialog you refer to
(how
> to you "click" to get
> > there) and I'll give it a spin. I've never encountered this, or even
> thought about the archive bit
> > being relevant...
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
>|||I can acutally just type in the name of the file in the "Choose Restore
Destination" Dialog Box. It will restore it, they just don't show in the
dir tree.
Doug
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:uxhb6pUhEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Interesting problem indeed -- can you use the "native" T-SQL RESTORE to
> perform the database restore?
> Steve

2005Express trying to enable Full text indexing.

We have an installation of SQL2005 Express that was loaded via the "SQL2005Express with advanced services" download .exe.

Full text indexing wasn't enabled during installation.

It says to go to add/remove programs. Going that route when it goes to install FTI it says that it can't find the installation files in what looks to be the origonal "TEMP" folder created and removed during installation.

If I run the program installer from the download again it states that SQL is already installed and to use "add/remove programs".

We are stuck at this point. Is there an ISO available that could be burned to disk?

Thanks in advance.

We've seen this error a few times during Express reinstalls and I haven't heard of a nice solution. One option is to backup your databases, uninstall your Express instance and reinstall it with FTI enabled.

Thanks,
Sam Lester (MSFT)

|||

What you should be able to do is run the original program installer from a command line with the "\X" switch. This will display a dialog that will allow you to extract the files inside the package to wherever you want. You should be able to put them anywhere you like on you local hard drive. Then when you use Add/Remove programs to maintain your Express instance, and it asks for the files, make sure you browse to the "Setup" directory underneath where you extracted the bits. That should work without you having to uninstall your existing instance.

|||This will also be documented in the requirementssqlexp2005.htm file located at the root of the folder where you extracted out the bits. It is under the section titled "Modifying SQL Server Express Installed Components".|||After unpackaging using /x I get the following error, when trying to add FTI via the "add remove programs".

"The file G:\myfilepath is not a valid installation package for the product Microsoft SQL Server 2005 (SQLEXPRESS). Try to find the installation package 'sqlrun_sql.msi' in a folder in which you can install Microsoft SQL Server 2005 (SQLEXPRESS)."

The file is there in the folder.

Any other ideas short of uninstalling/reinstalling?|||

You need to make sure to browse to the "Setup" folder underneath where you extracted. If the setup folder is not there, than the extraction may not be correct. G:\myfilepath should contain a setup.exe file, and then a setup folder. In the setup folder there should be a bunch of MSIs, one of which is sqlrun_sql.msi.

Also, make sure the Sqlexpr.exe you are running to extract is the same as what was used initially to install. If the editions don't match than you could see that error as well. For example, don't mix and match SQL Express with SQL Express with Advanced Services.

|||I did point to the file in the setup folder (it was there).

This is the same .exe that was downloaded one month ago.|||I just tried this out myself and it does appear to work, so hopefully this should be easy to resolve. Could you post two logs so I can see what might be failing for you? Both the latest *_WI.log and *_SQL.log files would be needed (located in %programfiles%\microsoft sql server\90\setup bootstrap\log), thank you!|||

Sorry, I'm new here and didn't realize you can't post attachments. Here is what I need from the *_WI.log. Search for this string:

Doing action: ResolveSource

And then copy and paste the contents of the log up until this string:

ResolveSource. Return value

Let's just start with that, and then see if I need the *_SQL.log.

2005 SP1 Installation Fails - MSP 1612 - 'Unableto install MSI fil

any ideas what is responsible for this? we have installed sp1 on several
other machines without an issue...thanks
08/09/2007 13:30:33.795 Hotfix package launched
08/09/2007 13:30:55.029 Attempting to install instance: SQL Server Native
Client
08/09/2007 13:30:55.029 Attempting to install target: <hostname>
08/09/2007 13:30:55.029 Attempting to install file: sqlncli.msi
08/09/2007 13:30:55.061 Attempting to install file:
\\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
08/09/2007 13:30:55.061 Creating MSI install log file at:
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
08/09/2007 13:30:55.061 Successfully opened registry key:
Software\Policies\Microsoft\Windows\Installer
08/09/2007 13:30:55.061 Failed to read registry key: Debug
08/09/2007 13:30:55.264 MSP returned 1612: The installation source for this
product is not available. Verify that the source exists and that you can
access it.
08/09/2007 13:30:55.264 Successfully opened registry key:
Software\Policies\Microsoft\Windows\Installer
08/09/2007 13:30:55.279 Failed to read registry key: Debug
08/09/2007 13:30:55.279 Unable to install MSI file:
\\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
08/09/2007 13:30:55.279 The following exception occurred: Unable to install
Windows Installer MSI file Date: 08/09/2007 13:30:55.279 File:
\depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 1191Are you by any chance using network connection to install the SP1? If yes,
have you tried to copy the MSI to local system first, and then run it that
way?
Lucas
"Craig" wrote:
> any ideas what is responsible for this? we have installed sp1 on several
> other machines without an issue...thanks
> 08/09/2007 13:30:33.795 Hotfix package launched
> 08/09/2007 13:30:55.029 Attempting to install instance: SQL Server Native
> Client
> 08/09/2007 13:30:55.029 Attempting to install target: <hostname>
> 08/09/2007 13:30:55.029 Attempting to install file: sqlncli.msi
> 08/09/2007 13:30:55.061 Attempting to install file:
> \\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
> 08/09/2007 13:30:55.061 Creating MSI install log file at:
> C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
> 08/09/2007 13:30:55.061 Successfully opened registry key:
> Software\Policies\Microsoft\Windows\Installer
> 08/09/2007 13:30:55.061 Failed to read registry key: Debug
> 08/09/2007 13:30:55.264 MSP returned 1612: The installation source for this
> product is not available. Verify that the source exists and that you can
> access it.
> 08/09/2007 13:30:55.264 Successfully opened registry key:
> Software\Policies\Microsoft\Windows\Installer
> 08/09/2007 13:30:55.279 Failed to read registry key: Debug
> 08/09/2007 13:30:55.279 Unable to install MSI file:
> \\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
> 08/09/2007 13:30:55.279 The following exception occurred: Unable to install
> Windows Installer MSI file Date: 08/09/2007 13:30:55.279 File:
> \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 1191
>|||We do have the SP local. thought this might be a solution
(http://support.microsoft.com/kb/918357/en-us) but no such luck...
"Lucas Kartawidjaja" wrote:
> Are you by any chance using network connection to install the SP1? If yes,
> have you tried to copy the MSI to local system first, and then run it that
> way?
> Lucas
> "Craig" wrote:
> > any ideas what is responsible for this? we have installed sp1 on several
> > other machines without an issue...thanks
> >
> > 08/09/2007 13:30:33.795 Hotfix package launched
> > 08/09/2007 13:30:55.029 Attempting to install instance: SQL Server Native
> > Client
> > 08/09/2007 13:30:55.029 Attempting to install target: <hostname>
> > 08/09/2007 13:30:55.029 Attempting to install file: sqlncli.msi
> > 08/09/2007 13:30:55.061 Attempting to install file:
> > \\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
> > 08/09/2007 13:30:55.061 Creating MSI install log file at:
> > C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
> > 08/09/2007 13:30:55.061 Successfully opened registry key:
> > Software\Policies\Microsoft\Windows\Installer
> > 08/09/2007 13:30:55.061 Failed to read registry key: Debug
> > 08/09/2007 13:30:55.264 MSP returned 1612: The installation source for this
> > product is not available. Verify that the source exists and that you can
> > access it.
> > 08/09/2007 13:30:55.264 Successfully opened registry key:
> > Software\Policies\Microsoft\Windows\Installer
> > 08/09/2007 13:30:55.279 Failed to read registry key: Debug
> > 08/09/2007 13:30:55.279 Unable to install MSI file:
> > \\<hostname>\d$\d24f5f9ba366431b25cc05\HotFixSqlncli\Files\sqlncli.msi
> > 08/09/2007 13:30:55.279 The following exception occurred: Unable to install
> > Windows Installer MSI file Date: 08/09/2007 13:30:55.279 File:
> > \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 1191
> >

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing this
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
Emma
Hi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:

> The initial installation of 2005 was to the C drive of the server. I want to
> uninstall and reinstalling on the D drive. What is the best way of doing this
> and still retain all the information already setup in the database? Example,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing thi
s
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
EmmaHi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:

> The initial installation of 2005 was to the C drive of the server. I want
to
> uninstall and reinstalling on the D drive. What is the best way of doing t
his
> and still retain all the information already setup in the database? Exampl
e,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 Installation location

The initial installation of 2005 was to the C drive of the server. I want to
uninstall and reinstalling on the D drive. What is the best way of doing this
and still retain all the information already setup in the database? Example,
user security and scheduled jobs?
Thanks,
EmmaHi Emma
You can backup the databases and restore them onto the new instance see:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms190749.aspx
http://msdn2.microsoft.com/en-us/library/ms190255.aspx
If you are not changing the location of the user database files, restoring
master should recover them. If you then want to move them elsewhere they can
be detached/attached in the new location.
Make sure that you have the same build for the new version as the old one.
You may also want to check for orphaned users in each database
http://support.microsoft.com/kb/274188
John
"Emma" wrote:
> The initial installation of 2005 was to the C drive of the server. I want to
> uninstall and reinstalling on the D drive. What is the best way of doing this
> and still retain all the information already setup in the database? Example,
> user security and scheduled jobs?
> Thanks,
> Emma
>

2005 Failover Cluster SAN drives best practices

I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
currently have two nodes and I am planning on adding more instances to
run on the other node.
First, I am not sure I have setup my existing default instance the best
way for my cluster. I currently only have one 'Physical Disk' in the
cluster group which is a LUN on our SAN. Both the data files and log
files are stored there. What is the best practice to move the logs onto
another spindle? Do I have to just create another LUN?
I am about to add a few more instances. Does each one need to have it's
own LUN?
There is a limited amount of drive letters that I can create. Is there
a way to share a LUN between instances? I seem to remember reading a
feature of 2005 that was related to this but, for the life of me, I
cannot find it again.
Any help would be appreciated!
Thank you
Karl> What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
You should at least put yout transaction log files on a separate LUN from
your data LUN. This doesn't guarantee that your data and log would be placed
on separate spindles inside SAN because both LUNs can be carved from the same
set of disks, but at least it gives you some separation.
> I am about to add a few more instances.
> Does each one need to have it's own LUN?
Each clustered instance will be implemented a separate cluster resource
group with its own disk resource(s). Since you can't have the same read/write
disk as two separate disk resources in different resource groups, each
clustered instance needs its own LUN.
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances?
You can't really share drive letters. But SQL2005 fully supports mounted
volumes in a cluster. These volumes don't have to be assigned separate drive
letters. As long as they are made disk resources, and are mounted under a
root drive letter, you can have multiple volumes in a resource group (or an
instance) with as few as one drive letter per instance.
Linchi
"Karl" wrote:
> I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
> currently have two nodes and I am planning on adding more instances to
> run on the other node.
> First, I am not sure I have setup my existing default instance the best
> way for my cluster. I currently only have one 'Physical Disk' in the
> cluster group which is a LUN on our SAN. Both the data files and log
> files are stored there. What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
> I am about to add a few more instances. Does each one need to have it's
> own LUN?
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances? I seem to remember reading a
> feature of 2005 that was related to this but, for the life of me, I
> cannot find it again.
> Any help would be appreciated!
> Thank you
> Karl
>

2005 DB backwards-compatible to 2000?

I've attached an SQL2000 db to an SQL2005 Std installation and am curious if
that process can go the other way. Can you detach from 2005 and attach to
2000 without any issues?
Earl wrote:
> Can you detach from 2005 and attach to
> 2000 without any issues?
No. One cannot attach a higher version database to a lower version SQL
Server. The 2005 file format is incompatible with SQL Server 2000.
If you have to migrate backwards, use SSIS to copy the objects and data from
SQL Server 2005 to SQL Server 2000.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200612/1
|||No, You can not do that because of architectural changes.
Thanks
Hari
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:%23ye9a5kHHHA.3540@.TK2MSFTNGP02.phx.gbl...
> I've attached an SQL2000 db to an SQL2005 Std installation and am curious
> if that process can go the other way. Can you detach from 2005 and attach
> to 200use of 0 without any issues?
>
|||Ahhh, thanks Chris and Hari. Tis' the answer I need.
"Chris O'C via droptable.com" <u29189@.uwe> wrote in message
news:6aacc6ece6f0b@.uwe...
> Earl wrote:
> No. One cannot attach a higher version database to a lower version SQL
> Server. The 2005 file format is incompatible with SQL Server 2000.
> If you have to migrate backwards, use SSIS to copy the objects and data
> from
> SQL Server 2005 to SQL Server 2000.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200612/1
>

2005 DB backwards-compatible to 2000?

I've attached an SQL2000 db to an SQL2005 Std installation and am curious if
that process can go the other way. Can you detach from 2005 and attach to
2000 without any issues?Earl wrote:
> Can you detach from 2005 and attach to
> 2000 without any issues?
No. One cannot attach a higher version database to a lower version SQL
Server. The 2005 file format is incompatible with SQL Server 2000.
If you have to migrate backwards, use SSIS to copy the objects and data from
SQL Server 2005 to SQL Server 2000.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200612/1|||No, You can not do that because of architectural changes.
Thanks
Hari
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:%23ye9a5kHHHA.3540@.TK2MSFTNGP02.phx.gbl...
> I've attached an SQL2000 db to an SQL2005 Std installation and am curious
> if that process can go the other way. Can you detach from 2005 and attach
> to 200use of 0 without any issues?
>|||Ahhh, thanks Chris and Hari. Tis' the answer I need.
"Chris O'C via droptable.com" <u29189@.uwe> wrote in message
news:6aacc6ece6f0b@.uwe...
> Earl wrote:
> No. One cannot attach a higher version database to a lower version SQL
> Server. The 2005 file format is incompatible with SQL Server 2000.
> If you have to migrate backwards, use SSIS to copy the objects and data
> from
> SQL Server 2005 to SQL Server 2000.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200612/1
>

2005 DB backwards-compatible to 2000?

I've attached an SQL2000 db to an SQL2005 Std installation and am curious if
that process can go the other way. Can you detach from 2005 and attach to
2000 without any issues?Earl wrote:
> Can you detach from 2005 and attach to
> 2000 without any issues?
No. One cannot attach a higher version database to a lower version SQL
Server. The 2005 file format is incompatible with SQL Server 2000.
If you have to migrate backwards, use SSIS to copy the objects and data from
SQL Server 2005 to SQL Server 2000.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200612/1|||No, You can not do that because of architectural changes.
Thanks
Hari
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:%23ye9a5kHHHA.3540@.TK2MSFTNGP02.phx.gbl...
> I've attached an SQL2000 db to an SQL2005 Std installation and am curious
> if that process can go the other way. Can you detach from 2005 and attach
> to 200use of 0 without any issues?
>|||Ahhh, thanks Chris and Hari. Tis' the answer I need.
"Chris O'C via SQLMonster.com" <u29189@.uwe> wrote in message
news:6aacc6ece6f0b@.uwe...
> Earl wrote:
>> Can you detach from 2005 and attach to
>> 2000 without any issues?
> No. One cannot attach a higher version database to a lower version SQL
> Server. The 2005 file format is incompatible with SQL Server 2000.
> If you have to migrate backwards, use SSIS to copy the objects and data
> from
> SQL Server 2005 to SQL Server 2000.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200612/1
>

2005 Datepicker control and dateformat

Hi, we have an installation of MSSQL reporting services where users
can select data based on date ranges. Since upgrading to 2005 we now
have a nice new Date picker control alongside textareas which accept
MSSQL datetime values.
This is all very nice but the date picker automatically formats the
date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
I
have checked the regional settings of both the browser/ server etc.
Scouring the Internet seems to point that this is a post SP2 problem
but there seems to be no fix other than making the datefields a type
of nvarchar and then converting them to dates in the Stored
Procedure.
If there really is no fix, how can I just disable this date picker
control? In 2000 people just entered the dates manually, this was
fine
but know there is a date picker control people are obviously going to
use it.
Thanks
RexOn Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> Hi, we have an installation of MSSQL reporting services where users
> can select data based on date ranges. Since upgrading to 2005 we now
> have a nice new Date picker control alongside textareas which accept
> MSSQL datetime values.
> This is all very nice but the date picker automatically formats the
> date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> I
> have checked the regional settings of both the browser/ server etc.
> Scouring the Internet seems to point that this is a post SP2 problem
> but there seems to be no fix other than making the datefields a type
> of nvarchar and then converting them to dates in the Stored
> Procedure.
> If there really is no fix, how can I just disable this date picker
> control? In 2000 people just entered the dates manually, this was
> fine
> but know there is a date picker control people are obviously going to
> use it.
> Thanks
> Rex
Aside from the workarounds you have attempted, that is also all I can
think of. If I understand you correctly, to remove the date time
picker in a specific report you would just select the Layout view ->
Report drop-down tab -> Report Parameters... and select the parameter
you want to remove the date time picker for and then change the Data
type: to something other than DateTime. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
> On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
>
>
> > Hi, we have an installation of MSSQL reporting services where users
> > can select data based on date ranges. Since upgrading to 2005 we now
> > have a nice new Date picker control alongside textareas which accept
> > MSSQL datetime values.
> > This is all very nice but the date picker automatically formats the
> > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > I
> > have checked the regional settings of both the browser/ server etc.
> > Scouring the Internet seems to point that this is a post SP2 problem
> > but there seems to be no fix other than making the datefields a type
> > of nvarchar and then converting them to dates in the Stored
> > Procedure.
> > If there really is no fix, how can I just disable this date picker
> > control? In 2000 people just entered the dates manually, this was
> > fine
> > but know there is a date picker control people are obviously going to
> > use it.
> > Thanks
> > Rex
> Aside from the workarounds you have attempted, that is also all I can
> think of. If I understand you correctly, to remove the date time
> picker in a specific report you would just select the Layout view ->
> Report drop-down tab -> Report Parameters... and select the parameter
> you want to remove the date time picker for and then change the Data
> type: to something other than DateTime. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant- Hide quoted text -
> - Show quoted text -
Hi Enrique, thanks for your help. I have found a fix which seems to
work so I'm posting here to help anyone in the future who comes across
the problem.
In the folder where Reporting Services is installed fin a file called
ReportView.aspx
e.g.
c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
\ReportServer\Pages\ReportViewer.aspx
Open up this file and add the following to the Page Directive
Culture="en-AU"
This seemed to solve my problem
Regards
Rex|||On Jul 5, 10:17 pm, Markus...@.gmail.com wrote:
> On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
>
> > On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> > > Hi, we have an installation of MSSQL reporting services where users
> > > can select data based on date ranges. Since upgrading to 2005 we now
> > > have a nice new Date picker control alongside textareas which accept
> > > MSSQL datetime values.
> > > This is all very nice but the date picker automatically formats the
> > > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > > I
> > > have checked the regional settings of both the browser/ server etc.
> > > Scouring the Internet seems to point that this is a post SP2 problem
> > > but there seems to be no fix other than making the datefields a type
> > > of nvarchar and then converting them to dates in the Stored
> > > Procedure.
> > > If there really is no fix, how can I just disable this date picker
> > > control? In 2000 people just entered the dates manually, this was
> > > fine
> > > but know there is a date picker control people are obviously going to
> > > use it.
> > > Thanks
> > > Rex
> > Aside from the workarounds you have attempted, that is also all I can
> > think of. If I understand you correctly, to remove the date time
> > picker in a specific report you would just select the Layout view ->
> > Report drop-down tab -> Report Parameters... and select the parameter
> > you want to remove the date time picker for and then change the Data
> > type: to something other than DateTime. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant- Hide quoted text -
> > - Show quoted text -
> Hi Enrique, thanks for your help. I have found a fix which seems to
> work so I'm posting here to help anyone in the future who comes across
> the problem.
> In the folder where Reporting Services is installed fin a file called
> ReportView.aspx
> e.g.
> c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> \ReportServer\Pages\ReportViewer.aspx
> Open up this file and add the following to the Page Directive
> Culture="en-AU"
> This seemed to solve my problem
> Regards
> Rex
Very nice tidbit to know. So basically, that manually changed your
regional settings I guess.
Regards,
Enrique Martinez
Sr. Software Consultant

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?

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?