can't backup database

I have SQL2000 running on a member 2003server.
Have setup a maintenance plan but our primary database as well as the Main
database are not getting backed up among other things.
Looking at the history log I see many errors:
Check data and index linkage errors out with the message "Repair statement
not processed. Database needs to be in single user mode"
Backup transaction log "Backup can not be performed on this database.
This sub task is ignored"
I don't even have error messages for the backups that aren't happening for
these 2.
All the other databases, Northwind, model, msdb, and pubs are doing fine.
What am I missing here?> Check data and index linkage errors out with the message "Repair statement
> not processed. Database needs to be in single user mode"
Remove the "attempt to repair minor problems" from the integrity check part of the maint plan.
> Backup transaction log "Backup can not be performed on this database.
> This sub task is ignored"
Don't attempt to backup of the log of databases in simple recovery model.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:B631B1DA-9D97-4FB6-886C-BD26ABE249CF@.microsoft.com...
>I have SQL2000 running on a member 2003server.
> Have setup a maintenance plan but our primary database as well as the Main
> database are not getting backed up among other things.
> Looking at the history log I see many errors:
> Check data and index linkage errors out with the message "Repair statement
> not processed. Database needs to be in single user mode"
> Backup transaction log "Backup can not be performed on this database.
> This sub task is ignored"
> I don't even have error messages for the backups that aren't happening for
> these 2.
> All the other databases, Northwind, model, msdb, and pubs are doing fine.
> What am I missing here?|||Why do I need to remove the "attempt to repair minor problems"? Why is this
option available if it only screws up the whole maintenance plan?
Why does it say that database needs to be in single user mode'
How does one make a database into single user mode'
And your last statement is ? to me as well: "Don't attempt to backup the
log of the databases in simple recovery model." What the heck does that
mean'
You didn't address why my databases are not even getting backed up nor why
there is no error message as to why they're not getting backed up.
Please forgive me, I am not an SQL guru, only know enough to keep this
shit running, but I've had no problems in running all these things in prior
maintenance plans in the past.
Please be a bit more thourough in your explanations. Thanks man.
"Tibor Karaszi" wrote:
> > Check data and index linkage errors out with the message "Repair statement
> > not processed. Database needs to be in single user mode"
> Remove the "attempt to repair minor problems" from the integrity check part of the maint plan.
>
> > Backup transaction log "Backup can not be performed on this database.
> > This sub task is ignored"
> Don't attempt to backup of the log of databases in simple recovery model.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
> news:B631B1DA-9D97-4FB6-886C-BD26ABE249CF@.microsoft.com...
> >I have SQL2000 running on a member 2003server.
> >
> > Have setup a maintenance plan but our primary database as well as the Main
> > database are not getting backed up among other things.
> >
> > Looking at the history log I see many errors:
> >
> > Check data and index linkage errors out with the message "Repair statement
> > not processed. Database needs to be in single user mode"
> >
> > Backup transaction log "Backup can not be performed on this database.
> > This sub task is ignored"
> >
> > I don't even have error messages for the backups that aren't happening for
> > these 2.
> >
> > All the other databases, Northwind, model, msdb, and pubs are doing fine.
> >
> > What am I missing here?
>|||> Why do I need to remove the "attempt to repair minor problems"? Why is
> this
> option available if it only screws up the whole maintenance plan?
The same reason some laptops, and the spark plugs on '78 datsun b210s, were
prone to catching fire. Sadly, not every scenario is completely tested. At
least in this case the outcome is not potential death, but merely a
suggestion to uncheck a checkbox.
> Why does it say that database needs to be in single user mode'
Because for some repair options that's just what is required. You wouldn't
expect to talk on your cell phone while the tech is trying to fix it?
> How does one make a database into single user mode'
ALTER DATABASE dbname SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
> And your last statement is ? to me as well: "Don't attempt to backup
> the
> log of the databases in simple recovery model." What the heck does that
> mean'
That means if your database is in simple recovery mode, don't back up the
log. It's pretty pointless since the log is useless in this case.
> You didn't address why my databases are not even getting backed up nor
> why
> there is no error message as to why they're not getting backed up.
We don't know the answer to the question. We can merely suggest ways you
can avoid the errors. I think Tibor's suggestions are sound, and you should
try them instead of complaining...
A

Can't access linked server, except from

Hi, (excuse my poor english).
I want to access data stored on a SQL2000 server using
"SELECT * FROM openquery(SQL2000srv, ..." from a
connection on my SQL2005 server.
I checked "Allow remote connections" on both servers, and
configured Nammed pipes as prefered protocol.
Security is Windows authentification only for both servers.
If I test my query on Management studio on my 2005 server,
everything is OK. But when I test from any other machine,
I have this error : (sorry, I translated it from french :
OLE DB 'SQLNCLI' from linked server returns 'Connection timeout'.
Msg 5, level 16, state 1, Line 0
Nammed pipes : can't open connection to SQL Server [5]. ".).
I can connect to both servers using any connection, so it's not
a user security problem, I think.
Do you have any clues ?
Thank you,
Jid.Hi Jide,
you have to ensure that Named Pipes is turned on as a Client Protocol.
You do this by opening up SQL Server Configuration Manager from the Sql
Server program group.
Underneath the SQL Native Client Configuration you find the Client Protocols
- here the Named Pipes protocol have to be enabled...
That may be the reason - at least its disabled at default.
Regards,
Mogens Nielsen
WM-data Danmark
"jidehem" wrote:

> Hi, (excuse my poor english).
> I want to access data stored on a SQL2000 server using
> "SELECT * FROM openquery(SQL2000srv, ..." from a
> connection on my SQL2005 server.
> I checked "Allow remote connections" on both servers, and
> configured Nammed pipes as prefered protocol.
> Security is Windows authentification only for both servers.
> If I test my query on Management studio on my 2005 server,
> everything is OK. But when I test from any other machine,
> I have this error : (sorry, I translated it from french :
> OLE DB 'SQLNCLI' from linked server returns 'Connection timeout'.
> Msg 5, level 16, state 1, Line 0
> Nammed pipes : can't open connection to SQL Server [5]. ".).
> I can connect to both servers using any connection, so it's not
> a user security problem, I think.
> Do you have any clues ?
> Thank you,
> Jidé.
>
>|||Mogens Nielsen - WM-Data A/S wrote:
> Hi Jide,
> you have to ensure that Named Pipes is turned on as a Client Protocol.
> You do this by opening up SQL Server Configuration Manager from the
> Sql Server program group.
> Underneath the SQL Native Client Configuration you find the Client
> Protocols - here the Named Pipes protocol have to be enabled...
> That may be the reason - at least its disabled at default.
Nammed pipes was already my prefered protocol for both servers
and in Client configuration utility. But thank you for your answer.
Another idea ?
Jid.|||Thought it was the simple problem like not turning named pipes on. I don't
think I've got any other good ideas...
Well, you could try connect by using an IP-adress instead of using the
server name, but then again - you shouldn't be able to connect through the
enterprise manager.
I think this is not of much help...
Maybe someone else has a clue !?
"jidehem" wrote:

> Mogens Nielsen - WM-Data A/S wrote:
> Nammed pipes was already my prefered protocol for both servers
> and in Client configuration utility. But thank you for your answer.
> Another idea ?
> Jidé.
>
>|||Mogens Nielsen - WM-Data A/S wrote:
> I think this is not of much help...
> Maybe someone else has a clue !?
Thank you again for your answers. I found the problem :
it's was "double hop" authentification problem.
In active directory, you need to activate delegation for
the user of the account of the SQL Server service, and for
the computer.
I have manually registred with setspn my linked server:
setspn -A MSSQLSvc/server.mydomaine.local:1433 account
(and not :
setspn -A MSSQLSvc/server:1433 account
nor
setspn -A MSSQLSvc/server:1433 mydomaine\account).
Now, all is OK.
Jid.

Cann't uninstall an instance

I once tried to uninstall a single default instance of sql2000, using
the installation CD. Unfortunately, it was taking forever and I killed
the process. After I rebooted the server and tried to uninstall again, I
got the error, saying uninstall file could not be found, or something
was missing...
I tried to re-install the default instance to correct it. However, I
could not get the default instance back. As a result, I could not
re-install it and I could not uninstall it.
How can I manually uninstall the instance?
Thank you.
I found myself an article and will go from there...
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/default...290991&sd=tech
Jluo wrote:
> I once tried to uninstall a single default instance of sql2000, using
> the installation CD. Unfortunately, it was taking forever and I killed
> the process. After I rebooted the server and tried to uninstall again, I
> got the error, saying uninstall file could not be found, or something
> was missing...
> I tried to re-install the default instance to correct it. However, I
> could not get the default instance back. As a result, I could not
> re-install it and I could not uninstall it.
> How can I manually uninstall the instance?
> Thank you.
>

Cann't uninstall an instance

I once tried to uninstall a single default instance of sql2000, using
the installation CD. Unfortunately, it was taking forever and I killed
the process. After I rebooted the server and tried to uninstall again, I
got the error, saying uninstall file could not be found, or something
was missing...
I tried to re-install the default instance to correct it. However, I
could not get the default instance back. As a result, I could not
re-install it and I could not uninstall it.
How can I manually uninstall the instance?
Thank you.I found myself an article and will go from there...
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/defaul...;290991&sd=tech
Jluo wrote:
> I once tried to uninstall a single default instance of sql2000, using
> the installation CD. Unfortunately, it was taking forever and I killed
> the process. After I rebooted the server and tried to uninstall again, I
> got the error, saying uninstall file could not be found, or something
> was missing...
> I tried to re-install the default instance to correct it. However, I
> could not get the default instance back. As a result, I could not
> re-install it and I could not uninstall it.
> How can I manually uninstall the instance?
> Thank you.
>

Cann't uninstall an instance

I once tried to uninstall a single default instance of sql2000, using
the installation CD. Unfortunately, it was taking forever and I killed
the process. After I rebooted the server and tried to uninstall again, I
got the error, saying uninstall file could not be found, or something
was missing...
I tried to re-install the default instance to correct it. However, I
could not get the default instance back. As a result, I could not
re-install it and I could not uninstall it.
How can I manually uninstall the instance?
Thank you.I found myself an article and will go from there...
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/default.aspx?scid=kb;en-us;290991&sd=tech
Jluo wrote:
> I once tried to uninstall a single default instance of sql2000, using
> the installation CD. Unfortunately, it was taking forever and I killed
> the process. After I rebooted the server and tried to uninstall again, I
> got the error, saying uninstall file could not be found, or something
> was missing...
> I tried to re-install the default instance to correct it. However, I
> could not get the default instance back. As a result, I could not
> re-install it and I could not uninstall it.
> How can I manually uninstall the instance?
> Thank you.
>

Cannot update replication once live - have to recreate!

I have set up a transactional replication from SQL2000 (W2K) to SQL2005
(W2K3). Once it's running, if I add a new field to the publisher, it doesn't
appear in the subscriber tables. I have tried everything including
re-inititalising the job, stopping and starting agents - nothing works. All I
am left with is deleting then recreating the entire replication job which is
time consuming and annoying.
Somebody out there must have the answer to me inadequacy!
Thanks in advance,
Will, Leeds UK
Will,
I need to understand how you did this. How did you add the new field? Did
you use sp_repladdcolumn?
Also, when you say reinitializing the job I'm not sure what you mean. Do you
mean restart the snapshot agent? If so, this is not reinitialization. If the
subscription is marked for reinitialization, this is something different.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi, basically we replicate live databases onto a separate server for
reporting. Occasionally we modify the live database (add a new field say) and
need the replication job to reflect this change. At the moment, every time we
make a change we have to remove replication, delete the reporting database
copy, then re-add replication. The live databases are on SQL 2000 and
reporting copies on SQL2005.
I haven't tried sp_repladdcolumn yet. I have just been using various actions
from SQL Management Studio.
I am a little confused as to the 'official method' to achieve what I want!
What I do know is that our current method works BUT is very tedious...
Thanks
Will
"Paul Ibison" wrote:

> Will,
> I need to understand how you did this. How did you add the new field? Did
> you use sp_repladdcolumn?
> Also, when you say reinitializing the job I'm not sure what you mean. Do you
> mean restart the snapshot agent? If so, this is not reinitialization. If the
> subscription is marked for reinitialization, this is something different.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

Cannot start the Reporting Service

I am currently working on a windows 2003 server with SQL2000 (developers edition). My Sqlserver and Report Server are on two different machines.

This was working yesterday but frustratingly not this morning.

Everytime I try to start the Reporting Server service, it gives me the following message:

"The Report Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

Is there a way around this? - any help would be greatly appreciated .

Anyone?|||If you are still seeing this issue...I found a solution for a similiar error (a different service, but the same error). Had to clear out the Application log in Event Viewer. See if that helps.|||Possibly best not to delete the contents of the event logs, as this may provide a pointer towards solving your problem. Open the eventlogs, then start the service, find the error that is logged for it. If you post that here it may give more of an idea.
|||

I'm facing a very similar problem. I've installed, uninstalled and reinstalled SQL server 2005 Developer Edition twice now. In each case Report Server can't be started. I've looked in the logs and the pertinent errors seem to be the following:

ReportingServicesService!library!4!6/16/2006-15:28:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.
ReportingServicesService!servicecontroller!4!6/16/2006-15:28:33:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.

In the other log file is the following error:

ReportingServicesService!library!8!6/16/2006-15:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights., ;
Info:

Looking at the time stamp, I believe the later is just a result of the UnknownUserNameException:

SQL Server works fine, I can work with the database in the Management Studio and access them through ASP.NET without a problem (or at least I could before I uninstalled a couple of times!!)

.Net framework 2.0 is installed. I have a Gig of RAM, plenty of hard disk and XP Prof Ed SP 2.

I'm at a total loss on how to get it to work on this machine. Any help would be greatly appreciated!!

Bob O'Dell

|||

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

|||

ASPNET user did appear as a user and I tried different permissions to no avail. What finally worked was to uninstall Report Services (actually I uninstalled ALL of SQL server) and then reinstalled the .NET framework. After that I reinstalled SQL Server and Report Services. Everything seemed to work after that. I'm not sure what was wrong, but I'm off and running now!

Thanks for the help

|||

James Wu - MSFT wrote:

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

This was the 'trick' I was looking for. Now I'm able to start the Reporting Service. Many thanks!!

Cannot start the Reporting Service

I am currently working on a windows 2003 server with SQL2000 (developers edition). My Sqlserver and Report Server are on two different machines.

This was working yesterday but frustratingly not this morning.

Everytime I try to start the Reporting Server service, it gives me the following message:

"The Report Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

Is there a way around this? - any help would be greatly appreciated .

Anyone?|||If you are still seeing this issue...I found a solution for a similiar error (a different service, but the same error). Had to clear out the Application log in Event Viewer. See if that helps.|||Possibly best not to delete the contents of the event logs, as this may provide a pointer towards solving your problem. Open the eventlogs, then start the service, find the error that is logged for it. If you post that here it may give more of an idea.
|||

I'm facing a very similar problem. I've installed, uninstalled and reinstalled SQL server 2005 Developer Edition twice now. In each case Report Server can't be started. I've looked in the logs and the pertinent errors seem to be the following:

ReportingServicesService!library!4!6/16/2006-15:28:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.
ReportingServicesService!servicecontroller!4!6/16/2006-15:28:33:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.

In the other log file is the following error:

ReportingServicesService!library!8!6/16/2006-15:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights., ;
Info:

Looking at the time stamp, I believe the later is just a result of the UnknownUserNameException:

SQL Server works fine, I can work with the database in the Management Studio and access them through ASP.NET without a problem (or at least I could before I uninstalled a couple of times!!)

.Net framework 2.0 is installed. I have a Gig of RAM, plenty of hard disk and XP Prof Ed SP 2.

I'm at a total loss on how to get it to work on this machine. Any help would be greatly appreciated!!

Bob O'Dell

|||

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

|||

ASPNET user did appear as a user and I tried different permissions to no avail. What finally worked was to uninstall Report Services (actually I uninstalled ALL of SQL server) and then reinstalled the .NET framework. After that I reinstalled SQL Server and Report Services. Everything seemed to work after that. I'm not sure what was wrong, but I'm off and running now!

Thanks for the help

|||

James Wu - MSFT wrote:

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

This was the 'trick' I was looking for. Now I'm able to start the Reporting Service. Many thanks!!

Cannot start the Reporting Service

I am currently working on a windows 2003 server with SQL2000 (developers edition). My Sqlserver and Report Server are on two different machines.

This was working yesterday but frustratingly not this morning.

Everytime I try to start the Reporting Server service, it gives me the following message:

"The Report Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.

Is there a way around this? - any help would be greatly appreciated .

Anyone?|||If you are still seeing this issue...I found a solution for a similiar error (a different service, but the same error). Had to clear out the Application log in Event Viewer. See if that helps.|||Possibly best not to delete the contents of the event logs, as this may provide a pointer towards solving your problem. Open the eventlogs, then start the service, find the error that is logged for it. If you post that here it may give more of an idea.
|||

I'm facing a very similar problem. I've installed, uninstalled and reinstalled SQL server 2005 Developer Edition twice now. In each case Report Server can't be started. I've looked in the logs and the pertinent errors seem to be the following:

ReportingServicesService!library!4!6/16/2006-15:28:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.
ReportingServicesService!servicecontroller!4!6/16/2006-15:28:33:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.

In the other log file is the following error:

ReportingServicesService!library!8!6/16/2006-15:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights., ;
Info:

Looking at the time stamp, I believe the later is just a result of the UnknownUserNameException:

SQL Server works fine, I can work with the database in the Management Studio and access them through ASP.NET without a problem (or at least I could before I uninstalled a couple of times!!)

.Net framework 2.0 is installed. I have a Gig of RAM, plenty of hard disk and XP Prof Ed SP 2.

I'm at a total loss on how to get it to work on this machine. Any help would be greatly appreciated!!

Bob O'Dell

|||

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

|||

ASPNET user did appear as a user and I tried different permissions to no avail. What finally worked was to uninstall Report Services (actually I uninstalled ALL of SQL server) and then reinstalled the .NET framework. After that I reinstalled SQL Server and Report Services. Everything seemed to work after that. I'm not sure what was wrong, but I'm off and running now!

Thanks for the help

|||

James Wu - MSFT wrote:

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help.

aspnet_regiis.exe -i -enable

This was the 'trick' I was looking for. Now I'm able to start the Reporting Service. Many thanks!!

Cannot run SRS 2000 and WSS3 on same server

I have a single Win2k3 server that was running SQL2000, SQL Reporting
Services 2000, and Windows SharePoint Services 2.
I upgraded the WSS2 to WSS3. When I try to navigate to http://myserver/Reports
I get an error "Server Error in /Reports Application". With the error
message Unrecognized attribute 'Type'. The source error has this line
highlighted...
<sectionGroup name="System.Workflow.ComponentModel.WorkflowCompiler"
type="System.Workflow.ComponentModel.Compiler.WorkflowCompilerConfigurationSectionGroup,
System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35">
The source file identified in the error is c:\inetpub\wwwroot
\web.config
I assumed that the Reports application couldn't understand the
web.config entry because it now included Freamework v2 information.
The first thing that I tried was to change the ASP.Net settings in IIS
for Reports and ReportServer to v2.
Now when I navigate to http://myserver/Reports the reports I can see
the reports listed properly. But, when I try to execute a report I
get the following Reporting Services Error...
Failed to load expression host assembly. Details: StrongName cannot
have an empty string for the assembly name. (rsProcessingError)
>From looking at other postings it appears that this error is due to me
setting the Reports and ReportServer applications to ASP.Net v2.
So, I am stuck. If I set the applications to v2 I can see the site
but cannot run the reports. If I set te applications to v1.1 then I
cannot see the site at all.
Is there are way to allow Reporting Services 2000 to exist with WSS3?
Thanks for your help
IANI suggest you read through this article about "Troubleshooting a
Side-by-Side Installation of Reporting Services and Windows SharePoint
Services"
http://msdn2.microsoft.com/en-us/library/aa179370(SQL.80).aspx
It refers to RS 2000 and WSS 2.0, but it might give you some clues as how to
set it up. I'm not sure if you can exclude sites in WSS 3.0 though, so you
might have to move the RS virtual directories to their own web site, at
least to create a new web application, to make sure you can change which
.NET framework they use.
Hope this gives you something to work with.
Kaisa M. Lindahl Lervik
<iani4profit@.gmail.com> wrote in message
news:1173135063.253461.175400@.j27g2000cwj.googlegroups.com...
>I have a single Win2k3 server that was running SQL2000, SQL Reporting
> Services 2000, and Windows SharePoint Services 2.
> I upgraded the WSS2 to WSS3. When I try to navigate to
> http://myserver/Reports
> I get an error "Server Error in /Reports Application". With the error
> message Unrecognized attribute 'Type'. The source error has this line
> highlighted...
> <sectionGroup name="System.Workflow.ComponentModel.WorkflowCompiler"
> type="System.Workflow.ComponentModel.Compiler.WorkflowCompilerConfigurationSectionGroup,
> System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral,
> PublicKeyToken=31bf3856ad364e35">
> The source file identified in the error is c:\inetpub\wwwroot
> \web.config
> I assumed that the Reports application couldn't understand the
> web.config entry because it now included Freamework v2 information.
> The first thing that I tried was to change the ASP.Net settings in IIS
> for Reports and ReportServer to v2.
> Now when I navigate to http://myserver/Reports the reports I can see
> the reports listed properly. But, when I try to execute a report I
> get the following Reporting Services Error...
> Failed to load expression host assembly. Details: StrongName cannot
> have an empty string for the assembly name. (rsProcessingError)
>>From looking at other postings it appears that this error is due to me
> setting the Reports and ReportServer applications to ASP.Net v2.
> So, I am stuck. If I set the applications to v2 I can see the site
> but cannot run the reports. If I set te applications to v1.1 then I
> cannot see the site at all.
> Is there are way to allow Reporting Services 2000 to exist with WSS3?
> Thanks for your help
> IAN
>|||WSS3 does not have the "exclude sites" functionality any more.
My short term (hopefully) solution is to host the report sites on a
new site that is unrelated to SharePoint. The bad part is that I will
need to update all of the links to the various reports throughout my
web sites, etc.
Thanks for your feedback.
IAN

Cannot restore a copy of SQL2000 to SQL2005

I ran into a weird problem trying to restore a backup copy of SQL2000
database into the new SQL2005 server. I copied the backup file
"databasename.bak" to the backup folder of the new SQL2005 server but cannot
see it using browse in restore function.
help!!!
BillI would say that was not exactly the same directory or there is a
permissions issue. Verify the complete path or try some other location.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Bill Nguyen" wrote:

> I ran into a weird problem trying to restore a backup copy of SQL2000
> database into the new SQL2005 server. I copied the backup file
> "databasename.bak" to the backup folder of the new SQL2005 server but cann
ot
> see it using browse in restore function.
> help!!!
> Bill
>
>|||Ben;
You're correct. I looked into the wrong folder.
After that, I ran into a different problem though:
I upgraded the SQLserver 2005 to SP1 ans tried to restore a copy of SQL2000
from another server to it. SQL 05 refused to restore saying that the backup
is for another SQLserver instance! I don't remember running into this
problem last time I did the same task.
Any idea why?
Thanks again.
Bill
Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:B1063714-ACF3-461D-885C-FCE372E210D4@.microsoft.com...[vbcol=seagreen]
> I would say that was not exactly the same directory or there is a
> permissions issue. Verify the complete path or try some other location.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Bill Nguyen" wrote:
>

Cannot restore a copy of SQL2000 to SQL2005

I ran into a weird problem trying to restore a backup copy of SQL2000
database into the new SQL2005 server. I copied the backup file
"databasename.bak" to the backup folder of the new SQL2005 server but cannot
see it using browse in restore function.
help!!!
BillI would say that was not exactly the same directory or there is a
permissions issue. Verify the complete path or try some other location.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Bill Nguyen" wrote:
> I ran into a weird problem trying to restore a backup copy of SQL2000
> database into the new SQL2005 server. I copied the backup file
> "databasename.bak" to the backup folder of the new SQL2005 server but cannot
> see it using browse in restore function.
> help!!!
> Bill
>
>|||Ben;
You're correct. I looked into the wrong folder.
After that, I ran into a different problem though:
I upgraded the SQLserver 2005 to SP1 ans tried to restore a copy of SQL2000
from another server to it. SQL 05 refused to restore saying that the backup
is for another SQLserver instance! I don't remember running into this
problem last time I did the same task.
Any idea why?
Thanks again.
Bill
Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:B1063714-ACF3-461D-885C-FCE372E210D4@.microsoft.com...
> I would say that was not exactly the same directory or there is a
> permissions issue. Verify the complete path or try some other location.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Bill Nguyen" wrote:
>> I ran into a weird problem trying to restore a backup copy of SQL2000
>> database into the new SQL2005 server. I copied the backup file
>> "databasename.bak" to the backup folder of the new SQL2005 server but
>> cannot
>> see it using browse in restore function.
>> help!!!
>> Bill
>>