Showing posts with label attempting. Show all posts
Showing posts with label attempting. Show all posts

Friday, March 23, 2012

ReportServer Error - Please help!

How should I resolve the following error message when attempting to access
ReportServer? (i.e. http://wardteserv/reportserver or /reports)
ERROR:
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 'C.0.8.38'. The expected
version is 'C.0.8.39'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)So it looks like you installed a new version of RS 2005 and attached to an
older version of the DB. There isn't a supported way to upgrade from
intermin builds like this. In this case you are fairly lucky in that the
Database changes are fairly easy and you should be able to make them
manually.
Here they are:
In the ReportServer DB run the following T-SQL:
ALTER TABLE [dbo].[ServerParametersInstance] ADD [ParentID] nvarchar(32)
NULL
also update the following Stored procs:
CREATE PROCEDURE [dbo].[StoreServerParameters]
@.ServerParametersID nvarchar(32),
@.Path nvarchar(425),
@.CurrentDate datetime,
@.Timeout int,
@.Expiration datetime,
@.ParametersValues image,
@.ParentParametersID nvarchar(32) = NULL
AS
DECLARE @.ExistingServerParametersID as nvarchar(32)
SET @.ExistingServerParametersID = (SELECT ServerParametersID from
[dbo].[ServerParametersInstance] WHERE ServerParametersID =@.ServerParametersID)
IF @.ExistingServerParametersID IS NULL -- new row
BEGIN
INSERT INTO [dbo].[ServerParametersInstance]
(ServerParametersID, ParentID, Path, CreateDate, ModifiedDate, Timeout,
Expiration, ParametersValues)
VALUES
(@.ServerParametersID, @.ParentParametersID, @.Path, @.CurrentDate,
@.CurrentDate, @.Timeout, @.Expiration, @.ParametersValues)
END
ELSE
BEGIN
UPDATE [dbo].[ServerParametersInstance]
SET Timeout = @.Timeout,
Expiration = @.Expiration,
ParametersValues = @.ParametersValues,
ModifiedDate = @.CurrentDate,
Path = @.Path,
ParentID = @.ParentParametersID
WHERE ServerParametersID = @.ServerParametersID
END
GO
CREATE PROCEDURE [dbo].[GetServerParameters]
@.ServerParametersID nvarchar(32)
AS
DECLARE @.now as DATETIME
SET @.now = GETDATE()
SELECT Child.Path, Child.ParametersValues, Parent.ParametersValues
FROM [dbo].[ServerParametersInstance] Child
LEFT OUTER JOIN [dbo].[ServerParametersInstance] Parent
ON Child.ParentID = Parent.ServerParametersID
WHERE Child.ServerParametersID = @.ServerParametersID
AND Child.Expiration > @.now
GO
finally change the GetDBVersion stored proc to:
CREATE PROCEDURE [dbo].[GetDBVersion]
@.DBVersion nvarchar(32) OUTPUT
AS
set @.DBVersion = 'C.0.8.39'
GO
That should get you up and running.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:864DDB7A-6271-42D8-B8C5-E5EB71E5E374@.microsoft.com...
> How should I resolve the following error message when attempting to access
> ReportServer? (i.e. http://wardteserv/reportserver or /reports)
> ERROR:
> 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 'C.0.8.38'. The expected
> version is 'C.0.8.39'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)
>|||Can anyone please tell What does this table ServerParametersInstance does in SSRS 2005
From http://www.google.co.in/search?q=ServerParametersInstance&hl=en&safe=off&filter=
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

ReportServer directory not available outside firewall

We are attempting to expose our reports to the internet without much luck.
The domain name is not set up yet, so we are accessing by IP. There are 2
virtual folders - Reports and ReportServer are set up with Windows
authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
prompted, login and then see the list of reports. When I click on a report,
I get prompted again, but login fails and I get 401. Where should I start
looking? Most problems I see from others have to do with the Reports
directory, but their ReportServer directory works.I think 401 is an 'Unauthorised' error. Check your firewall settings, but
pay specific attention to the IIS and .NET authentication as well. Are you
using windows or forms based authentication?
"danb" wrote:
> We are attempting to expose our reports to the internet without much luck.
> The domain name is not set up yet, so we are accessing by IP. There are 2
> virtual folders - Reports and ReportServer are set up with Windows
> authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> prompted, login and then see the list of reports. When I click on a report,
> I get prompted again, but login fails and I get 401. Where should I start
> looking? Most problems I see from others have to do with the Reports
> directory, but their ReportServer directory works.|||Yes, 401 wit h a message about invalid credentials, but as I said, I was able
to log in to the /ReportServer folder successfully and then it prompted me
again for some reason when I clicked on any report.
Check the firewall for what?
Windows authentication is being used on both Reports and ReportServer folders.
Server is Windows 2003 Server.
"CraigyBoop" wrote:
> I think 401 is an 'Unauthorised' error. Check your firewall settings, but
> pay specific attention to the IIS and .NET authentication as well. Are you
> using windows or forms based authentication?
> "danb" wrote:
> > We are attempting to expose our reports to the internet without much luck.
> > The domain name is not set up yet, so we are accessing by IP. There are 2
> > virtual folders - Reports and ReportServer are set up with Windows
> > authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> > prompted, login and then see the list of reports. When I click on a report,
> > I get prompted again, but login fails and I get 401. Where should I start
> > looking? Most problems I see from others have to do with the Reports
> > directory, but their ReportServer directory works.

Monday, March 12, 2012

Reports - IE7?

Are there some major issues with the reports and IE7?
One of our systems which is attempting to access the reports via LAN is
having the following problems. The system is running IE7 Beta 3 on
WinXPPro SP2.
1) When opening report builder the progress window appears showing the
download of the application but the report builder never displays. No
errors, nothing!
2) When clicking on a report the report shows correctly but IE7 seems to be
doing something still, the icon on the tab keep flickering and most
navigation has a minute or two delay. There is also an '!' in the icon on
the status bar but where you can normally click on the icon to view it never
displays.
3) The date select buttons and drop down list from the parameters and export
selection don't work at all.
Regards,
JohnFrom other postings I gather beta2 worked OK and beta3 does not. I discussed
with internal MS person and he told me they have a commitment from the IE
team to fix the problem. There is no workaround. So, MS RS team is aware of
the issue and so is the IE 7 team.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"John J. Hughes II" <no@.invalid.com> wrote in message
news:exnFYOKtGHA.3684@.TK2MSFTNGP05.phx.gbl...
> Are there some major issues with the reports and IE7?
> One of our systems which is attempting to access the reports via LAN is
> having the following problems. The system is running IE7 Beta 3 on
> WinXPPro SP2.
> 1) When opening report builder the progress window appears showing the
> download of the application but the report builder never displays. No
> errors, nothing!
> 2) When clicking on a report the report shows correctly but IE7 seems to
> be doing something still, the icon on the tab keep flickering and most
> navigation has a minute or two delay. There is also an '!' in the icon
> on the status bar but where you can normally click on the icon to view it
> never displays.
> 3) The date select buttons and drop down list from the parameters and
> export selection don't work at all.
> Regards,
> John
>|||Ok, thanks... Saves me trying to track down the problem
Regards,
John
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23oQM%23cKtGHA.4600@.TK2MSFTNGP06.phx.gbl...
> From other postings I gather beta2 worked OK and beta3 does not. I
> discussed with internal MS person and he told me they have a commitment
> from the IE team to fix the problem. There is no workaround. So, MS RS
> team is aware of the issue and so is the IE 7 team.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "John J. Hughes II" <no@.invalid.com> wrote in message
> news:exnFYOKtGHA.3684@.TK2MSFTNGP05.phx.gbl...
>> Are there some major issues with the reports and IE7?
>> One of our systems which is attempting to access the reports via LAN is
>> having the following problems. The system is running IE7 Beta 3 on
>> WinXPPro SP2.
>> 1) When opening report builder the progress window appears showing the
>> download of the application but the report builder never displays. No
>> errors, nothing!
>> 2) When clicking on a report the report shows correctly but IE7 seems to
>> be doing something still, the icon on the tab keep flickering and most
>> navigation has a minute or two delay. There is also an '!' in the icon
>> on the status bar but where you can normally click on the icon to view it
>> never displays.
>> 3) The date select buttons and drop down list from the parameters and
>> export selection don't work at all.
>> Regards,
>> John
>|||I have tried IE7 RC1 and it seems to have the same problem, can anyone
confirm this?
Regards,
John
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23oQM%23cKtGHA.4600@.TK2MSFTNGP06.phx.gbl...
> From other postings I gather beta2 worked OK and beta3 does not. I
> discussed with internal MS person and he told me they have a commitment
> from the IE team to fix the problem. There is no workaround. So, MS RS
> team is aware of the issue and so is the IE 7 team.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "John J. Hughes II" <no@.invalid.com> wrote in message
> news:exnFYOKtGHA.3684@.TK2MSFTNGP05.phx.gbl...
>> Are there some major issues with the reports and IE7?
>> One of our systems which is attempting to access the reports via LAN is
>> having the following problems. The system is running IE7 Beta 3 on
>> WinXPPro SP2.
>> 1) When opening report builder the progress window appears showing the
>> download of the application but the report builder never displays. No
>> errors, nothing!
>> 2) When clicking on a report the report shows correctly but IE7 seems to
>> be doing something still, the icon on the tab keep flickering and most
>> navigation has a minute or two delay. There is also an '!' in the icon
>> on the status bar but where you can normally click on the icon to view it
>> never displays.
>> 3) The date select buttons and drop down list from the parameters and
>> export selection don't work at all.
>> Regards,
>> John
>|||Hi John,
I was using IE 7 Beta 2 with reporting services fine. I then installed Beta
3 and was having the problem you described in your first postingand reported
it via this newsgroup. Can't recall if it was Bruce or not but a Microsoft
MVP contacted Microsoft, confirmed this was known and replied to me that
this would be fixed using essentially the identical words you quoted here.
Late last week I downloaded and installed IE 7 RC1 and was thrilled that the
problem is no longer happening.
If this is happening for you on RC1, there is something else involved.
Jon|||Thanks Jon,
Ok I will look into other issues.
Regards,
John
"Jon Limmer" <jonlimmer@.hotmail.com> wrote in message
news:eyLE43qyGHA.1536@.TK2MSFTNGP02.phx.gbl...
> Hi John,
> I was using IE 7 Beta 2 with reporting services fine. I then installed
> Beta 3 and was having the problem you described in your first postingand
> reported it via this newsgroup. Can't recall if it was Bruce or not but a
> Microsoft MVP contacted Microsoft, confirmed this was known and replied to
> me that this would be fixed using essentially the identical words you
> quoted here.
> Late last week I downloaded and installed IE 7 RC1 and was thrilled that
> the problem is no longer happening.
> If this is happening for you on RC1, there is something else involved.
> Jon
>|||I was running IE Beta 2 with no problems.
Just installed RC1 and the document map - doesn't display the content
anymore :-(|||The issue with Beta 3 was worse than that. Reports just flat out didn't
work. I'll pass this on.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mikey" <mikey@.discussions.microsoft.com> wrote in message
news:14D9B2EB-64F5-40EC-8DD2-960B47EBAAF5@.microsoft.com...
>I was running IE Beta 2 with no problems.
> Just installed RC1 and the document map - doesn't display the content
> anymore :-(
>

Wednesday, March 7, 2012

ReportIoError when performing backup - what can be done?

Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
When attempting a full database backup to a local drive I get the following
error - and have not found any workable documentation.
BackupMedium::ReportIoError: write failure on backup device
'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
found).
Background:
On 2 previous occasions, and the last weekend, the transaction log on the
above database has become full over the weekend.
The main contributor seems to be a script provided as part of a vendor's
software package which reindexes the database.
As there is little spare space on our server, to avoid this problem the
recovery mode has been changed from 'full' to 'bulk logged' before the
re-index is run, and changed back after the event.
I was advised after previously posting to Microsoft's discussion groups to
perform a full database backup after each change of recovery mode. It is
this step that failed with the full log last night.
PREVIOUSLY this problem has been worked around using the following steps:
1. Increased log file size to 3000MB
2. Tried to backup transaction log (failed)
3. Tried to make dbo access only (failed - said that other users logged in)
4. Checked Current activity (no occurance of extra users)
5. Rebooted server.
6. Made Pxxxxxx database dbo access only
7. Ran database shrink (job successful, but logfile still the same size)
8. Ran backup transaction log (successful this time, but logfile still the
same size)
9. Ran full backup ( why not? successful)
10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
only utilising 5% of allocated space.
11. Ran database shrink (job successful, but logfile still the same size)
12. Set log file autogrow to as small as possible (actual + 1)
13. Ran script based on
http://support.microsoft.com/default...b;en-us;256650 (which was
used to shrink a full log on SQL 7)
14. Performed a full database backup
15. Removed dbo access only flag.
Unfortunately, this time, the above process has failed. Any attempts to
backup the transaction log were unsuccessful, and any shrinkfile commands
failed due to the log being full or in use - preventing progress beyond steps
7&8.
A contact refered me to Article
http://support.microsoft.com/default...b;EN-US;272318
* DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile was
in use.
* BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file not
shrunk
*"Take a full backup of your database after you perform backup log with
truncate_only" ie:
BACKUP DATABASE [Pxxxxxx]
TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
WITH INIT ,
NOUNLOAD ,
NAME = N'Pxxxxxx backup',
NOSKIP ,
STATS = 10,
NOFORMAT
- fails with the same error (above) previously encountered when attempting a
log backup
Regards,
Kim.
Hi!
Just a quick help: you can get description of the OS error messages if you
use NET HELPMSG from the command prompt. For your case,
net helpmsg 2
gives
The system cannot find the file specified.
Hpe this will lead you to a resolution!
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the
following
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged
in)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/default...b;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond
steps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/default...b;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile
was
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file
not
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting
a
> log backup
>
> --
> Regards,
> Kim.
|||Dejan,
Thanks for the response. The explanation of the error code didn't leave me
much the wiser...
I increased the log file by another Gb and the backup succeeded.
Given that the data file is only 5.5GB, having a log file with so much space
allocated (over 3Gb) seems overkill, but... at least it works.
I've also now done a successful log file backup and shrunk the log - less
than 1% of the current log file in use.
"Dejan Sarka" wrote:

> Hi!
> Just a quick help: you can get description of the OS error messages if you
> use NET HELPMSG from the command prompt. For your case,
> net helpmsg 2
> gives
> The system cannot find the file specified.
> Hpe this will lead you to a resolution!
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
> news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> following
> in)
> steps
> was
> not
> a
>
>
|||> Thanks for the response. The explanation of the error code didn't leave
me
> much the wiser...
> I increased the log file by another Gb and the backup succeeded.
> Given that the data file is only 5.5GB, having a log file with so much
space
> allocated (over 3Gb) seems overkill, but... at least it works.
> I've also now done a successful log file backup and shrunk the log - less
> than 1% of the current log file in use.
Thank you for sharing your experience, although I have to say the same as
you - do not feel much wiser :-) But not because of your post, it is because
I can't understand what's going on.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
|||KD-Mudgee wrote:
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the following
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged in)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/default...b;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
did you shrink the transaction log after truncate? how much space do you
have on that backup drive?

> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond steps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/default...b;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile was
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file not
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting a
> log backup
>

ReportIoError when performing backup - what can be done?

Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
When attempting a full database backup to a local drive I get the following
error - and have not found any workable documentation.
BackupMedium::ReportIoError: write failure on backup device
'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
found).
Background:
On 2 previous occasions, and the last weekend, the transaction log on the
above database has become full over the weekend.
The main contributor seems to be a script provided as part of a vendor's
software package which reindexes the database.
As there is little spare space on our server, to avoid this problem the
recovery mode has been changed from 'full' to 'bulk logged' before the
re-index is run, and changed back after the event.
I was advised after previously posting to Microsoft's discussion groups to
perform a full database backup after each change of recovery mode. It is
this step that failed with the full log last night.
PREVIOUSLY this problem has been worked around using the following steps:
1. Increased log file size to 3000MB
2. Tried to backup transaction log (failed)
3. Tried to make dbo access only (failed - said that other users logged in)
4. Checked Current activity (no occurance of extra users)
5. Rebooted server.
6. Made Pxxxxxx database dbo access only
7. Ran database shrink (job successful, but logfile still the same size)
8. Ran backup transaction log (successful this time, but logfile still the
same size)
9. Ran full backup ( why not? successful)
10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
only utilising 5% of allocated space.
11. Ran database shrink (job successful, but logfile still the same size)
12. Set log file autogrow to as small as possible (actual + 1)
13. Ran script based on
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650 (which was
used to shrink a full log on SQL 7)
14. Performed a full database backup
15. Removed dbo access only flag.
Unfortunately, this time, the above process has failed. Any attempts to
backup the transaction log were unsuccessful, and any shrinkfile commands
failed due to the log being full or in use - preventing progress beyond steps
7&8.
A contact refered me to Article
http://support.microsoft.com/default.aspx?scid=kb;EN-US;272318
* DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile was
in use.
* BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file not
shrunk
*"Take a full backup of your database after you perform backup log with
truncate_only" ie:
BACKUP DATABASE [Pxxxxxx]
TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
WITH INIT ,
NOUNLOAD ,
NAME = N'Pxxxxxx backup',
NOSKIP ,
STATS = 10,
NOFORMAT
- fails with the same error (above) previously encountered when attempting a
log backup
--
Regards,
Kim.Hi!
Just a quick help: you can get description of the OS error messages if you
use NET HELPMSG from the command prompt. For your case,
net helpmsg 2
gives
The system cannot find the file specified.
Hpe this will lead you to a resolution!
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the
following
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged
in)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/default.aspx?scid=kb;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond
steps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile
was
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file
not
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting
a
> log backup
>
> --
> Regards,
> Kim.|||Dejan,
Thanks for the response. The explanation of the error code didn't leave me
much the wiser...
I increased the log file by another Gb and the backup succeeded.
Given that the data file is only 5.5GB, having a log file with so much space
allocated (over 3Gb) seems overkill, but... at least it works.
I've also now done a successful log file backup and shrunk the log - less
than 1% of the current log file in use.
"Dejan Sarka" wrote:
> Hi!
> Just a quick help: you can get description of the OS error messages if you
> use NET HELPMSG from the command prompt. For your case,
> net helpmsg 2
> gives
> The system cannot find the file specified.
> Hpe this will lead you to a resolution!
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
> news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> > Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> >
> > When attempting a full database backup to a local drive I get the
> following
> > error - and have not found any workable documentation.
> >
> > BackupMedium::ReportIoError: write failure on backup device
> > 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> > found).
> >
> >
> > Background:
> >
> > On 2 previous occasions, and the last weekend, the transaction log on the
> > above database has become full over the weekend.
> >
> > The main contributor seems to be a script provided as part of a vendor's
> > software package which reindexes the database.
> >
> > As there is little spare space on our server, to avoid this problem the
> > recovery mode has been changed from 'full' to 'bulk logged' before the
> > re-index is run, and changed back after the event.
> >
> > I was advised after previously posting to Microsoft's discussion groups to
> > perform a full database backup after each change of recovery mode. It is
> > this step that failed with the full log last night.
> >
> > PREVIOUSLY this problem has been worked around using the following steps:
> > 1. Increased log file size to 3000MB
> > 2. Tried to backup transaction log (failed)
> > 3. Tried to make dbo access only (failed - said that other users logged
> in)
> > 4. Checked Current activity (no occurance of extra users)
> > 5. Rebooted server.
> > 6. Made Pxxxxxx database dbo access only
> >
> > 7. Ran database shrink (job successful, but logfile still the same size)
> > 8. Ran backup transaction log (successful this time, but logfile still the
> > same size)
> > 9. Ran full backup ( why not? successful)
> > 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> > only utilising 5% of allocated space.
> >
> > 11. Ran database shrink (job successful, but logfile still the same size)
> > 12. Set log file autogrow to as small as possible (actual + 1)
> > 13. Ran script based on
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;256650 (which was
> > used to shrink a full log on SQL 7)
> > 14. Performed a full database backup
> > 15. Removed dbo access only flag.
> >
> >
> > Unfortunately, this time, the above process has failed. Any attempts to
> > backup the transaction log were unsuccessful, and any shrinkfile commands
> > failed due to the log being full or in use - preventing progress beyond
> steps
> > 7&8.
> >
> > A contact refered me to Article
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;272318
> >
> >
> > * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile
> was
> > in use.
> > * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file
> not
> > shrunk
> > *"Take a full backup of your database after you perform backup log with
> > truncate_only" ie:
> >
> > BACKUP DATABASE [Pxxxxxx]
> > TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> > WITH INIT ,
> > NOUNLOAD ,
> > NAME = N'Pxxxxxx backup',
> > NOSKIP ,
> > STATS = 10,
> > NOFORMAT
> >
> > - fails with the same error (above) previously encountered when attempting
> a
> > log backup
> >
> >
> > --
> > Regards,
> >
> > Kim.
>
>|||> Thanks for the response. The explanation of the error code didn't leave
me
> much the wiser...
> I increased the log file by another Gb and the backup succeeded.
> Given that the data file is only 5.5GB, having a log file with so much
space
> allocated (over 3Gb) seems overkill, but... at least it works.
> I've also now done a successful log file backup and shrunk the log - less
> than 1% of the current log file in use.
Thank you for sharing your experience, although I have to say the same as
you - do not feel much wiser :-) But not because of your post, it is because
I can't understand what's going on.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||KD-Mudgee wrote:
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the following
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged in)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/default.aspx?scid=kb;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
did you shrink the transaction log after truncate? how much space do you
have on that backup drive?
> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond steps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile was
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file not
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting a
> log backup
>

ReportIoError when performing backup - what can be done?

Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
When attempting a full database backup to a local drive I get the following
error - and have not found any workable documentation.
BackupMedium::ReportIoError: write failure on backup device
'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
found).
Background:
On 2 previous occasions, and the last weekend, the transaction log on the
above database has become full over the weekend.
The main contributor seems to be a script provided as part of a vendor's
software package which reindexes the database.
As there is little spare space on our server, to avoid this problem the
recovery mode has been changed from 'full' to 'bulk logged' before the
re-index is run, and changed back after the event.
I was advised after previously posting to Microsoft's discussion groups to
perform a full database backup after each change of recovery mode. It is
this step that failed with the full log last night.
PREVIOUSLY this problem has been worked around using the following steps:
1. Increased log file size to 3000MB
2. Tried to backup transaction log (failed)
3. Tried to make dbo access only (failed - said that other users logged in)
4. Checked Current activity (no occurance of extra users)
5. Rebooted server.
6. Made Pxxxxxx database dbo access only
7. Ran database shrink (job successful, but logfile still the same size)
8. Ran backup transaction log (successful this time, but logfile still the
same size)
9. Ran full backup ( why not? successful)
10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
only utilising 5% of allocated space.
11. Ran database shrink (job successful, but logfile still the same size)
12. Set log file autogrow to as small as possible (actual + 1)
13. Ran script based on
http://support.microsoft.com/defaul...kb;en-us;256650 (which was
used to shrink a full log on SQL 7)
14. Performed a full database backup
15. Removed dbo access only flag.
Unfortunately, this time, the above process has failed. Any attempts to
backup the transaction log were unsuccessful, and any shrinkfile commands
failed due to the log being full or in use - preventing progress beyond step
s
7&8.
A contact refered me to Article
http://support.microsoft.com/defaul...kb;EN-US;272318
* DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile was
in use.
* BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file not
shrunk
*"Take a full backup of your database after you perform backup log with
truncate_only" ie:
BACKUP DATABASE [Pxxxxxx]
TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
WITH INIT ,
NOUNLOAD ,
NAME = N'Pxxxxxx backup',
NOSKIP ,
STATS = 10,
NOFORMAT
- fails with the same error (above) previously encountered when attempting a
log backup
Regards,
Kim.Hi!
Just a quick help: you can get description of the OS error messages if you
use NET HELPMSG from the command prompt. For your case,
net helpmsg 2
gives
The system cannot find the file specified.
Hpe this will lead you to a resolution!
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the
following
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged
in)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/defaul...kb;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond
steps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/defaul...kb;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile
was
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file
not
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting
a
> log backup
>
> --
> Regards,
> Kim.|||Dejan,
Thanks for the response. The explanation of the error code didn't leave me
much the wiser...
I increased the log file by another Gb and the backup succeeded.
Given that the data file is only 5.5GB, having a log file with so much space
allocated (over 3Gb) seems overkill, but... at least it works.
I've also now done a successful log file backup and shrunk the log - less
than 1% of the current log file in use.
"Dejan Sarka" wrote:

> Hi!
> Just a quick help: you can get description of the OS error messages if you
> use NET HELPMSG from the command prompt. For your case,
> net helpmsg 2
> gives
> The system cannot find the file specified.
> Hpe this will lead you to a resolution!
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "KD-Mudgee" <KDMudgee@.discussions.microsoft.com> wrote in message
> news:3646EB63-2227-4ED6-A0B7-83716826C916@.microsoft.com...
> following
> in)
> steps
> was
> not
> a
>
>|||> Thanks for the response. The explanation of the error code didn't leave
me
> much the wiser...
> I increased the log file by another Gb and the backup succeeded.
> Given that the data file is only 5.5GB, having a log file with so much
space
> allocated (over 3Gb) seems overkill, but... at least it works.
> I've also now done a successful log file backup and shrunk the log - less
> than 1% of the current log file in use.
Thank you for sharing your experience, although I have to say the same as
you - do not feel much wiser :-) But not because of your post, it is because
I can't understand what's going on.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||KD-Mudgee wrote:
> Our site is running SQL Server 2000 sp3 on Windows 2000 sp3
> When attempting a full database backup to a local drive I get the followin
g
> error - and have not found any workable documentation.
> BackupMedium::ReportIoError: write failure on backup device
> 'd:\mssql7\backup\Pxxxxxx_backup.bak'. Operating system error 2(error not
> found).
>
> Background:
> On 2 previous occasions, and the last weekend, the transaction log on the
> above database has become full over the weekend.
> The main contributor seems to be a script provided as part of a vendor's
> software package which reindexes the database.
> As there is little spare space on our server, to avoid this problem the
> recovery mode has been changed from 'full' to 'bulk logged' before the
> re-index is run, and changed back after the event.
> I was advised after previously posting to Microsoft's discussion groups to
> perform a full database backup after each change of recovery mode. It is
> this step that failed with the full log last night.
> PREVIOUSLY this problem has been worked around using the following steps:
> 1. Increased log file size to 3000MB
> 2. Tried to backup transaction log (failed)
> 3. Tried to make dbo access only (failed - said that other users logged in
)
> 4. Checked Current activity (no occurance of extra users)
> 5. Rebooted server.
> 6. Made Pxxxxxx database dbo access only
> 7. Ran database shrink (job successful, but logfile still the same size)
> 8. Ran backup transaction log (successful this time, but logfile still the
> same size)
> 9. Ran full backup ( why not? successful)
> 10. Ran command: DBCC SQLPERF (LOGSPACE) which indicates that logfile is
> only utilising 5% of allocated space.
> 11. Ran database shrink (job successful, but logfile still the same size)
> 12. Set log file autogrow to as small as possible (actual + 1)
> 13. Ran script based on
> http://support.microsoft.com/defaul...kb;en-us;256650 (which was
> used to shrink a full log on SQL 7)
> 14. Performed a full database backup
> 15. Removed dbo access only flag.
>
did you shrink the transaction log after truncate? how much space do you
have on that backup drive?

> Unfortunately, this time, the above process has failed. Any attempts to
> backup the transaction log were unsuccessful, and any shrinkfile commands
> failed due to the log being full or in use - preventing progress beyond st
eps
> 7&8.
> A contact refered me to Article
> http://support.microsoft.com/defaul...kb;EN-US;272318
>
> * DBCC SHRINKFILE(Pxxxxxx_log, 2) - failed saying that the logfile wa
s
> in use.
> * BACKUP LOG Pxxxxxx WITH TRUNCATE_ONLY - ran successfully, but file n
ot
> shrunk
> *"Take a full backup of your database after you perform backup log with
> truncate_only" ie:
> BACKUP DATABASE [Pxxxxxx]
> TO DISK = N'D:\mssql7\backup\Pxxxxxx_backup.bak'
> WITH INIT ,
> NOUNLOAD ,
> NAME = N'Pxxxxxx backup',
> NOSKIP ,
> STATS = 10,
> NOFORMAT
> - fails with the same error (above) previously encountered when attempting
a
> log backup
>