Errors with SRS in Sharepoint Integration Mode

Hi Everyone,

Our project has two servers. One server is running WSS 3.0 and the SQL Reporting Services web front-end. We have a second server that operates all the databases involved (WSS Content, SRS, and our application specific DB).

We do not have a domain controller in our architecture. The WSS site is configured to use SQL authentication to connnect and modify the WSS Content database. We installed SRS, SRS service pack 2, and the Sharepoint add-in. We are using forms authentication for our WSS site. We would like to use SRS in Sharepoint Integration mode, but we are unable to create datasources, view reports, etc. SRS is configured to use the "Trusted Account" in WSS Central Admin.

When we attempt to create a new datasource, and we received an error stating the object moved and to check that SRS is in Sharepoint integration mode.

When we attempt to view a report, we get an error stating:

"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode."

I have a feeling this has to do with the Windows Service Account and the Web Service Identity for SRS. What type of account should we use since we do not have a domain?

Thank you,

Michael milazzo

As explained here, in Trusted Account mode, WSS sends the requests to the Report Server under the identity of the SharePoint application. By default, the IIS 6.0 application pool runs under NT AUTHORITY\Network Service. Since you don't have a domain setup, try changing the application domain identity to a local Windows user account which has the same name and password as a privileged account on the Report Server that has access to the report catalog. If you had domain setup, the request could have gone under Domain\WSS machine name$ and you could have granted access to that account.

Errors 5105-5170 when creating large datafile

Greetings.
We recently added a second RAID array to our four-way server to add another
filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
data file to a new filegroup on this new array. It ran for about 12 hours
and then came back with the following two errors:
Error 5105: Device activation error. The physical file name
'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
by 393000.00 MB on disk 'Clarity_Data2'.
Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
because it already exists. ALTER DATABASE failed. Some disk names listed in
the statement were not found. Check that the names exist and are spelled
correctly before rerunning the statement. Extending database by 393000.00 MB
on disk 'Clarity_Data2'.
First of all, the drive, folder, and now the file do exist. What happened
here to make this fail? Is there a way for me to successfully get this file
added to my database without going through the 12+ hour ALTER again?
Secondly, I would have thought that creating the new datafile would not have
taken that long to run, even though it was 400GB in size. It's a RAID 5
array on its own controller on a four-way box running Windows Server 2003.
Any thoughts?
Thanks.
Dale.
P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
DEFAULTDATA registry keys. There was no default set up for this server, so I
don't think that is related.Was RAID array already build when you have started to add a new data file ?
I'm sorry for silly question, but when you will create an RAID array, it will
accessible immediately, but RAID controller will build it up in a background.
It always good to wait when building processs will finished before work with
new array.This actually can cause performance issue as well as accessibility
issues.
Regards.
"Dale M." wrote:
> Greetings.
> We recently added a second RAID array to our four-way server to add another
> filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
> data file to a new filegroup on this new array. It ran for about 12 hours
> and then came back with the following two errors:
> Error 5105: Device activation error. The physical file name
> 'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
> by 393000.00 MB on disk 'Clarity_Data2'.
> Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
> because it already exists. ALTER DATABASE failed. Some disk names listed in
> the statement were not found. Check that the names exist and are spelled
> correctly before rerunning the statement. Extending database by 393000.00 MB
> on disk 'Clarity_Data2'.
> First of all, the drive, folder, and now the file do exist. What happened
> here to make this fail? Is there a way for me to successfully get this file
> added to my database without going through the 12+ hour ALTER again?
> Secondly, I would have thought that creating the new datafile would not have
> taken that long to run, even though it was 400GB in size. It's a RAID 5
> array on its own controller on a four-way box running Windows Server 2003.
> Any thoughts?
> Thanks.
> Dale.
> P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
> DEFAULTDATA registry keys. There was no default set up for this server, so I
> don't think that is related.|||Yes, it was already built. It had been online for most of a day already.
"SkyWalker" wrote:
> Was RAID array already build when you have started to add a new data file ?
> I'm sorry for silly question, but when you will create an RAID array, it will
> accessible immediately, but RAID controller will build it up in a background.
> It always good to wait when building processs will finished before work with
> new array.This actually can cause performance issue as well as accessibility
> issues.
> Regards.
> "Dale M." wrote:
> > Greetings.
> >
> > We recently added a second RAID array to our four-way server to add another
> > filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
> > data file to a new filegroup on this new array. It ran for about 12 hours
> > and then came back with the following two errors:
> > Error 5105: Device activation error. The physical file name
> > 'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
> > by 393000.00 MB on disk 'Clarity_Data2'.
> >
> > Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
> > because it already exists. ALTER DATABASE failed. Some disk names listed in
> > the statement were not found. Check that the names exist and are spelled
> > correctly before rerunning the statement. Extending database by 393000.00 MB
> > on disk 'Clarity_Data2'.
> >
> > First of all, the drive, folder, and now the file do exist. What happened
> > here to make this fail? Is there a way for me to successfully get this file
> > added to my database without going through the 12+ hour ALTER again?
> > Secondly, I would have thought that creating the new datafile would not have
> > taken that long to run, even though it was 400GB in size. It's a RAID 5
> > array on its own controller on a four-way box running Windows Server 2003.
> >
> > Any thoughts?
> >
> > Thanks.
> > Dale.
> >
> > P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
> > DEFAULTDATA registry keys. There was no default set up for this server, so I
> > don't think that is related.

Errors 5105-5170 when creating large datafile

Greetings.
We recently added a second RAID array to our four-way server to add another
filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
data file to a new filegroup on this new array. It ran for about 12 hours
and then came back with the following two errors:
Error 5105: Device activation error. The physical file name
'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
by 393000.00 MB on disk 'Clarity_Data2'.
Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
because it already exists. ALTER DATABASE failed. Some disk names listed i
n
the statement were not found. Check that the names exist and are spelled
correctly before rerunning the statement. Extending database by 393000.00 M
B
on disk 'Clarity_Data2'.
First of all, the drive, folder, and now the file do exist. What happened
here to make this fail? Is there a way for me to successfully get this file
added to my database without going through the 12+ hour ALTER again?
Secondly, I would have thought that creating the new datafile would not have
taken that long to run, even though it was 400GB in size. It's a RAID 5
array on its own controller on a four-way box running Windows Server 2003.
Any thoughts?
Thanks.
Dale.
P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
DEFAULTDATA registry keys. There was no default set up for this server, so
I
don't think that is related.Was RAID array already build when you have started to add a new data file ?
I'm sorry for silly question, but when you will create an RAID array, it wil
l
accessible immediately, but RAID controller will build it up in a background
.
It always good to wait when building processs will finished before work with
new array.This actually can cause performance issue as well as accessibility
issues.
Regards.
"Dale M." wrote:

> Greetings.
> We recently added a second RAID array to our four-way server to add anothe
r
> filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
> data file to a new filegroup on this new array. It ran for about 12 hours
> and then came back with the following two errors:
> Error 5105: Device activation error. The physical file name
> 'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending databa
se
> by 393000.00 MB on disk 'Clarity_Data2'.
> Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
> because it already exists. ALTER DATABASE failed. Some disk names listed
in
> the statement were not found. Check that the names exist and are spelled
> correctly before rerunning the statement. Extending database by 393000.00
MB
> on disk 'Clarity_Data2'.
> First of all, the drive, folder, and now the file do exist. What happened
> here to make this fail? Is there a way for me to successfully get this fi
le
> added to my database without going through the 12+ hour ALTER again?
> Secondly, I would have thought that creating the new datafile would not ha
ve
> taken that long to run, even though it was 400GB in size. It's a RAID 5
> array on its own controller on a four-way box running Windows Server 2003.
> Any thoughts?
> Thanks.
> Dale.
> P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
> DEFAULTDATA registry keys. There was no default set up for this server, s
o I
> don't think that is related.|||Yes, it was already built. It had been online for most of a day already.
"SkyWalker" wrote:
[vbcol=seagreen]
> Was RAID array already build when you have started to add a new data file
?
> I'm sorry for silly question, but when you will create an RAID array, it w
ill
> accessible immediately, but RAID controller will build it up in a backgrou
nd.
> It always good to wait when building processs will finished before work wi
th
> new array.This actually can cause performance issue as well as accessibili
ty
> issues.
> Regards.
> "Dale M." wrote:
>

Errors 5105-5170 when creating large datafile

Greetings.
We recently added a second RAID array to our four-way server to add another
filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
data file to a new filegroup on this new array. It ran for about 12 hours
and then came back with the following two errors:
Error 5105: Device activation error. The physical file name
'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
by 393000.00 MB on disk 'Clarity_Data2'.
Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
because it already exists. ALTER DATABASE failed. Some disk names listed in
the statement were not found. Check that the names exist and are spelled
correctly before rerunning the statement. Extending database by 393000.00 MB
on disk 'Clarity_Data2'.
First of all, the drive, folder, and now the file do exist. What happened
here to make this fail? Is there a way for me to successfully get this file
added to my database without going through the 12+ hour ALTER again?
Secondly, I would have thought that creating the new datafile would not have
taken that long to run, even though it was 400GB in size. It's a RAID 5
array on its own controller on a four-way box running Windows Server 2003.
Any thoughts?
Thanks.
Dale.
P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
DEFAULTDATA registry keys. There was no default set up for this server, so I
don't think that is related.
Was RAID array already build when you have started to add a new data file ?
I'm sorry for silly question, but when you will create an RAID array, it will
accessible immediately, but RAID controller will build it up in a background.
It always good to wait when building processs will finished before work with
new array.This actually can cause performance issue as well as accessibility
issues.
Regards.
"Dale M." wrote:

> Greetings.
> We recently added a second RAID array to our four-way server to add another
> filegroup to our 400GB database. Using SQL EM, I tried adding a new 400GB
> data file to a new filegroup on this new array. It ran for about 12 hours
> and then came back with the following two errors:
> Error 5105: Device activation error. The physical file name
> 'f:\MSSQL\data\Clarity_Data2_Data.NDF' may be incorrect. Extending database
> by 393000.00 MB on disk 'Clarity_Data2'.
> Error 5170: Cannot create file 'f:\MSSQL\data\Clarity_Data2_Data.NDF'
> because it already exists. ALTER DATABASE failed. Some disk names listed in
> the statement were not found. Check that the names exist and are spelled
> correctly before rerunning the statement. Extending database by 393000.00 MB
> on disk 'Clarity_Data2'.
> First of all, the drive, folder, and now the file do exist. What happened
> here to make this fail? Is there a way for me to successfully get this file
> added to my database without going through the 12+ hour ALTER again?
> Secondly, I would have thought that creating the new datafile would not have
> taken that long to run, even though it was 400GB in size. It's a RAID 5
> array on its own controller on a four-way box running Windows Server 2003.
> Any thoughts?
> Thanks.
> Dale.
> P.S. The only info I found on this in the KB mentioned the DEFAULTLOG and
> DEFAULTDATA registry keys. There was no default set up for this server, so I
> don't think that is related.
|||Yes, it was already built. It had been online for most of a day already.
"SkyWalker" wrote:
[vbcol=seagreen]
> Was RAID array already build when you have started to add a new data file ?
> I'm sorry for silly question, but when you will create an RAID array, it will
> accessible immediately, but RAID controller will build it up in a background.
> It always good to wait when building processs will finished before work with
> new array.This actually can cause performance issue as well as accessibility
> issues.
> Regards.
> "Dale M." wrote:

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and am
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
--
Paul G
Software engineer.sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:
>Hi I am trying to give database access to a second database for a user and am
>getting the error (Error 21002 username allready exists). Anyhow seems that
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Hi thanks for the response. the error I am getting now is 15023 user or role
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
--
Paul G
Software engineer.
"Hari Prasad" wrote:
> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> > Hi I am trying to give database access to a second database for a user and
> > am
> > getting the error (Error 21002 username allready exists). Anyhow seems
> > that
> > I ran into the problem before and ran a command from query analyzer and it
> > seemed to fix it. Anyhow can not remember the command I used.
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>|||it worked, thanks.
--
Paul G
Software engineer.
"Hari Prasad" wrote:
> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> > Hi I am trying to give database access to a second database for a user and
> > am
> > getting the error (Error 21002 username allready exists). Anyhow seems
> > that
> > I ran into the problem before and ran a command from query analyzer and it
> > seemed to fix it. Anyhow can not remember the command I used.
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and a
m
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
--
Paul G
Software engineer.sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:

>Hi I am trying to give database access to a second database for a user and
am
>getting the error (Error 21002 username allready exists). Anyhow seems tha
t
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Hi thanks for the response. the error I am getting now is 15023 user or rol
e
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch wi
th
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>|||it worked, thanks.
--
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch wi
th
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and am
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
Paul G
Software engineer.
sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.
|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:

>Hi I am trying to give database access to a second database for a user and am
>getting the error (Error 21002 username allready exists). Anyhow seems that
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.
|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'
|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.
|||Hi thanks for the response. the error I am getting now is 15023 user or role
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>
|||it worked, thanks.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>