Migrated Historical Snapshot

We have recently migrated (into a test environment) our RS2000 DB per the
microsoft migration instructions into RS2005.
When a history snapshot record is requested (Via ReportManager), we get an
internal RS Exception...
w3wp!library!1!11/13/2006-11:35:39:: i INFO: Call to
GetPermissions:<Roger!REPORTPATH>
w3wp!library!1!11/13/2006-11:35:39:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., Error compressing;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
w3wp!library!1!11/13/2006-11:35:40:: i INFO: Exception dumped to: C:\Program
Files\Microsoft SQL Server\MSSQL.5\Reporting Services\LogFiles flags=
ReferencedMemory, AllThreads, SendToWatson
w3wp!chunks!1!11/13/2006-11:35:40:: e ERROR: ###
SnapshotConverter(cb8c0d49-39e1-4775-ae6f-f73ac0fc68c4, True),
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
at Microsoft.ReportingServices.Diagnostics.CompressUt il.checkErr(Int32 err)
at Microsoft.ReportingServices.Diagnostics.CompressUt il.UnCompress(Byte[]
input, Int32 outputBufferLength, Byte[]& output)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.UncompressNative(Byte[]
compressedBuffer, Int32 uncompressedBufferLength, Byte[]& uncompressedBuffer)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.Uncompress(Byte[]
compressedBuffer, Int32 uncompressedBufferLength, Byte[]& uncompressedBuffer)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.ReadAndUncompressBuffer()
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.FillBuffer()
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream..ctor(Stream
store, Int16 version)
at
Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.CreateReadStream(Guid
snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
chunkType, Boolean rawStreamRequested, ConnectionManager connectionManager,
String& mimeType)
at
Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.GetCompressedReadStream(Guid
snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
chunkType, ConnectionManager connectionManager, String& mimeType)
at
Microsoft.ReportingServices.Library.SnapshotConver ter.ConvertFromV1(ReportSnapshot snapshot, Boolean isSnapshotProcessing)
Has anyone sucessfully migrated history from RS2000 to RS2005?
- Roger
Could you post this in the reporting services newsgroup? I think it belongs
there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tx Whytboy" <TxWhytboy@.discussions.microsoft.com> wrote in message
news:18002B03-FAED-4825-A6E7-ED56B8668B77@.microsoft.com...
> We have recently migrated (into a test environment) our RS2000 DB per the
> microsoft migration instructions into RS2005.
> When a history snapshot record is requested (Via ReportManager), we get an
> internal RS Exception...
> w3wp!library!1!11/13/2006-11:35:39:: i INFO: Call to
> GetPermissions:<Roger!REPORTPATH>
> w3wp!library!1!11/13/2006-11:35:39:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details., Error compressing;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details.
> w3wp!library!1!11/13/2006-11:35:40:: i INFO: Exception dumped to:
> C:\Program
> Files\Microsoft SQL Server\MSSQL.5\Reporting Services\LogFiles flags=
> ReferencedMemory, AllThreads, SendToWatson
> w3wp!chunks!1!11/13/2006-11:35:40:: e ERROR: ###
> SnapshotConverter(cb8c0d49-39e1-4775-ae6f-f73ac0fc68c4, True),
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details.
> at Microsoft.ReportingServices.Diagnostics.CompressUt il.checkErr(Int32
> err)
> at
> Microsoft.ReportingServices.Diagnostics.CompressUt il.UnCompress(Byte[]
> input, Int32 outputBufferLength, Byte[]& output)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.UncompressNative(Byte[]
> compressedBuffer, Int32 uncompressedBufferLength, Byte[]&
> uncompressedBuffer)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.Uncompress(Byte[]
> compressedBuffer, Int32 uncompressedBufferLength, Byte[]&
> uncompressedBuffer)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.ReadAndUncompressBuffer()
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.FillBuffer()
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream..ctor(Stream
> store, Int16 version)
> at
> Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.CreateReadStream(Guid
> snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
> chunkType, Boolean rawStreamRequested, ConnectionManager
> connectionManager,
> String& mimeType)
> at
> Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.GetCompressedReadStream(Guid
> snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
> chunkType, ConnectionManager connectionManager, String& mimeType)
> at
> Microsoft.ReportingServices.Library.SnapshotConver ter.ConvertFromV1(ReportSnapshot
> snapshot, Boolean isSnapshotProcessing)
>
> Has anyone sucessfully migrated history from RS2000 to RS2005?
> - Roger
|||Yeah.. Missed it by one.. and I didnt realize that...
Sorry!
"Hilary Cotter" wrote:

> Could you post this in the reporting services newsgroup? I think it belongs
> there.
> --
> Hilary Cotter
sql

migrate report history to another server

All,
I'm looking into the ability to move a report and it's history from one
reporting server to another. Moving the reporting is no problem, but I am
not having any luck in finding a way to move the associated historical
reports. I have used RSScripter to move reports, but the history does not
migrate. I was hoping to migrate the report history programmatically, but
I'm not seeing anything that suggests it is possible short of moving the
entire Reporting Services database. Has anyone moved historical reports
between Reporting Service servers?
Thanks,
RobertRMac,
There is a way to do this, I have done it. It involves creating some DTS
Packages though. Here are the steps that I did and it worked great:
First thing you need to do is go into the Catalog Table in the ReportServer
database and find the report that you are working with (the one that has all
of the history). This report will have an 'ItemID'. You will need this
ItemID to use in queries in the DTS packages.
Once you have the ItemID you can run a query against the History Table to
find all of the SnapShotDataID's, like this:
select * from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}'
Create a DTS Package, using this query, to export the history items from the
old server to the new one. Your history records will now be in the new
server History table.
Next, create another DTS Package, using a query similar to this one:
select * from dbo.SnapShotData
where snapshotdataid in
(select snapshotdataid from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
With this DTS package you are going to export out all of the SnapShotData
Table information from the old server to the new one.
Next DTS package will use a query similar to this one:
select * from dbo.ChunkData
where snapshotdataid in
(select snapshotdataid from dbo.history
where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
The ChunkData table is the table that actually contains the image files (or
snapshots) of the reports. Once you have the History table, SnapShotData
table and ChunkData table information moved over. You will need to run an
update query on the new server like this:
update dbo.History
set reportid = '(your new itemid from the new server catalog table)'
where reportid = '(your old itemid from the old server}'
You will need the new itemid for this previous query. Once you have
deployed the report to the new server, just go out to the Catalog table and
find the new item id. Use that in the update query above.
It sounds a lot harder than it really is. But, I have done it and this does
work.
"RMac" wrote:
> All,
> I'm looking into the ability to move a report and it's history from one
> reporting server to another. Moving the reporting is no problem, but I am
> not having any luck in finding a way to move the associated historical
> reports. I have used RSScripter to move reports, but the history does not
> migrate. I was hoping to migrate the report history programmatically, but
> I'm not seeing anything that suggests it is possible short of moving the
> entire Reporting Services database. Has anyone moved historical reports
> between Reporting Service servers?
> Thanks,
> Robert|||SandiB, this works like a champ. Thanks much!
"SandiB" wrote:
> RMac,
> There is a way to do this, I have done it. It involves creating some DTS
> Packages though. Here are the steps that I did and it worked great:
> First thing you need to do is go into the Catalog Table in the ReportServer
> database and find the report that you are working with (the one that has all
> of the history). This report will have an 'ItemID'. You will need this
> ItemID to use in queries in the DTS packages.
> Once you have the ItemID you can run a query against the History Table to
> find all of the SnapShotDataID's, like this:
> select * from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}'
> Create a DTS Package, using this query, to export the history items from the
> old server to the new one. Your history records will now be in the new
> server History table.
> Next, create another DTS Package, using a query similar to this one:
> select * from dbo.SnapShotData
> where snapshotdataid in
> (select snapshotdataid from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
> With this DTS package you are going to export out all of the SnapShotData
> Table information from the old server to the new one.
> Next DTS package will use a query similar to this one:
> select * from dbo.ChunkData
> where snapshotdataid in
> (select snapshotdataid from dbo.history
> where reportid = '{B22FBC16-5E61-4B40-903E-0E04E689DE60}')
> The ChunkData table is the table that actually contains the image files (or
> snapshots) of the reports. Once you have the History table, SnapShotData
> table and ChunkData table information moved over. You will need to run an
> update query on the new server like this:
> update dbo.History
> set reportid = '(your new itemid from the new server catalog table)'
> where reportid = '(your old itemid from the old server}'
> You will need the new itemid for this previous query. Once you have
> deployed the report to the new server, just go out to the Catalog table and
> find the new item id. Use that in the update query above.
> It sounds a lot harder than it really is. But, I have done it and this does
> work.
>
> "RMac" wrote:
> > All,
> > I'm looking into the ability to move a report and it's history from one
> > reporting server to another. Moving the reporting is no problem, but I am
> > not having any luck in finding a way to move the associated historical
> > reports. I have used RSScripter to move reports, but the history does not
> > migrate. I was hoping to migrate the report history programmatically, but
> > I'm not seeing anything that suggests it is possible short of moving the
> > entire Reporting Services database. Has anyone moved historical reports
> > between Reporting Service servers?
> > Thanks,
> > Robert

Microsoft SQL Server Health and History Tool

Anyone have any experience or comments using Microsoft SQL Server Health and
History Tool?
Hi,
The Microsoft SQL Server Health and History Tool (SQLH2) allows you to
collect information from instances of SQL Server, store this information,
and run reports against the data in order to determine how SQL Server is
being used.
http://www.microsoft..com/downloads/details.aspx?FamilyID=eedd10d6-75f7-4763
-86de-d2347b8b5f89&DisplayLang=en
Run the SQLH2 collector to help us collect feature usage information on SQL
2005(and SQL 2000) deployments. Then when the reports come out you (and
your customers) can easily view the collections.
Please understand, this question appears to be consulting in nature.
Although this newsgroup is here to provide break/fix resolution, we are
happy to provide general information and suggestions on it here and you may
receive suggestions from other partners on this topic both here and in the
public newsgroup for this product.
If you need further information, we would also like to introduce you to the
CUSTOMER SERVICE AND SUPPORT (CSS) Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/gp/advisoryservice
Outside of the US/Canada:
http://support.microsoft.com/common/international.aspx
Thanks for understanding.
Best regards,
Vincent Xu
Microsoft Online Partner Support
================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====
--[vbcol=seagreen]
and[vbcol=seagreen]

Microsoft SQL Server Health and History Tool

Hi All
I am reciving the following error when running the
Microsoft SQL Server Health and History Tool:
22/09/2004 1:48:56 PM INFO: version: 8.00.760
22/09/2004 1:48:56 PM Status: RUN
22/09/2004 1:48:56 PM Status: Initializing
collector: WMI
22/09/2004 1:48:56 PM Status: Running WMI collector
22/09/2004 1:48:56 PM Status: Opening Unit 1
(OS/CS)
22/09/2004 1:48:56 PM Status: Collecting
Win32_OperatingSystem
22/09/2004 1:48:56 PM Status: Collecting
Win32_ComputerSystem
22/09/2004 1:48:56 PM Status: Collecting
Win32_Processor
22/09/2004 1:48:58 PM ERROR: Line 1: Incorrect
syntax near 'c09'.
22/09/2004 1:48:58 PM Status: Closing Unit 1
22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
(run_id,srv_id,BootDevice,BuildNumber,BuildType,Ca ption,Co
deSet,CountryCode,CSDVersion,CSName,CurrentTimeZon e,Debug,
Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles, FreeVirt
ualMemory,InstallDate,LastBootUpTime,LocalDateTime ,Locale,
MaxProcessMemorySize,NumberOfProcesses,NumberOfUse rs,OSLan
guage,OSProductSuite,PAEEnabled,ServicePackMajorVe rsion,Se
rvicePackMinorVersion,SizeStoredInPagingFiles,Syst emDevice
,SystemDirectory,TotalVirtualMemorySize,TotalVisib leMemory
Size,Version,WindowsDirectory) Values (3,
1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
Free', 'Microsoft Windows XP
Professional', '1252', '61', 'Service Pack 1', 'test01',
600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
3112032, 522220, '5.1.2600', 'C:\WINDOWS')
22/09/2004 1:48:58 PM WARNING: WMI Collector
encountered critical error. Abandoning Collector.
22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
(run_id,srv_id,BootDevice,BuildNumber,BuildType,Ca ption,Co
deSet,CountryCode,CSDVersion,CSName,CurrentTimeZon e,Debug,
Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles, FreeVirt
ualMemory,InstallDate,LastBootUpTime,LocalDateTime ,Locale,
MaxProcessMemorySize,NumberOfProcesses,NumberOfUse rs,OSLan
guage,OSProductSuite,PAEEnabled,ServicePackMajorVe rsion,Se
rvicePackMinorVersion,SizeStoredInPagingFiles,Syst emDevice
,SystemDirectory,TotalVirtualMemorySize,TotalVisib leMemory
Size,Version,WindowsDirectory) Values (3,
1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
Free', 'Microsoft Windows XP
Professional', '1252', '61', 'Service Pack 1', 'test01',
600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
3112032, 522220, '5.1.2600', 'C:\WINDOWS')
22/09/2004 1:48:58 PM ERROR: test01: Collection
failed; Error:104; Provider Error: 170
22/09/2004 1:48:58 PM ERROR: Critical Repository
Failure
22/09/2004 1:48:58 PM SQLH2 is shutting down
22/09/2004 1:48:58 PM Closing Log
Has anyone come acrosss this error and can advise.
Thanks
Yes, i also have problems too.
And i think there is a problem with our collation settings. (Which is
Turkish_CI_AS).
Also reports are not working because of that i think. Hate this localization
problems.
I will try on English Locale server and see if it works..
"anonymous@.discussions.microsoft.com" wrote:

> Hi All
> I am reciving the following error when running the
> Microsoft SQL Server Health and History Tool:
> 22/09/2004 1:48:56 PM INFO: version: 8.00.760
> 22/09/2004 1:48:56 PM Status: RUN
> 22/09/2004 1:48:56 PM Status: Initializing
> collector: WMI
> 22/09/2004 1:48:56 PM Status: Running WMI collector
> 22/09/2004 1:48:56 PM Status: Opening Unit 1
> (OS/CS)
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_OperatingSystem
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_ComputerSystem
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_Processor
> 22/09/2004 1:48:58 PM ERROR: Line 1: Incorrect
> syntax near 'c09'.
> 22/09/2004 1:48:58 PM Status: Closing Unit 1
> 22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
> (run_id,srv_id,BootDevice,BuildNumber,BuildType,Ca ption,Co
> deSet,CountryCode,CSDVersion,CSName,CurrentTimeZon e,Debug,
> Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles, FreeVirt
> ualMemory,InstallDate,LastBootUpTime,LocalDateTime ,Locale,
> MaxProcessMemorySize,NumberOfProcesses,NumberOfUse rs,OSLan
> guage,OSProductSuite,PAEEnabled,ServicePackMajorVe rsion,Se
> rvicePackMinorVersion,SizeStoredInPagingFiles,Syst emDevice
> ,SystemDirectory,TotalVirtualMemorySize,TotalVisib leMemory
> Size,Version,WindowsDirectory) Values (3,
> 1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
> Free', 'Microsoft Windows XP
> Professional', '1252', '61', 'Service Pack 1', 'test01',
> 600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
> 08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
> 0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
> 2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
> 3112032, 522220, '5.1.2600', 'C:\WINDOWS')
> 22/09/2004 1:48:58 PM WARNING: WMI Collector
> encountered critical error. Abandoning Collector.
> 22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
> (run_id,srv_id,BootDevice,BuildNumber,BuildType,Ca ption,Co
> deSet,CountryCode,CSDVersion,CSName,CurrentTimeZon e,Debug,
> Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles, FreeVirt
> ualMemory,InstallDate,LastBootUpTime,LocalDateTime ,Locale,
> MaxProcessMemorySize,NumberOfProcesses,NumberOfUse rs,OSLan
> guage,OSProductSuite,PAEEnabled,ServicePackMajorVe rsion,Se
> rvicePackMinorVersion,SizeStoredInPagingFiles,Syst emDevice
> ,SystemDirectory,TotalVirtualMemorySize,TotalVisib leMemory
> Size,Version,WindowsDirectory) Values (3,
> 1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
> Free', 'Microsoft Windows XP
> Professional', '1252', '61', 'Service Pack 1', 'test01',
> 600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
> 08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
> 0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
> 2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
> 3112032, 522220, '5.1.2600', 'C:\WINDOWS')
> 22/09/2004 1:48:58 PM ERROR: test01: Collection
> failed; Error:104; Provider Error: 170
> 22/09/2004 1:48:58 PM ERROR: Critical Repository
> Failure
> 22/09/2004 1:48:58 PM SQLH2 is shutting down
> 22/09/2004 1:48:58 PM Closing Log
>
> Has anyone come acrosss this error and can advise.
> Thanks
>

Microsoft SQL Server Health and History Tool

Hi All
I am reciving the following error when running the
Microsoft SQL Server Health and History Tool:
22/09/2004 1:48:56 PM INFO: version: 8.00.760
22/09/2004 1:48:56 PM Status: RUN
22/09/2004 1:48:56 PM Status: Initializing
collector: WMI
22/09/2004 1:48:56 PM Status: Running WMI collector
22/09/2004 1:48:56 PM Status: Opening Unit 1
(OS/CS)
22/09/2004 1:48:56 PM Status: Collecting
Win32_OperatingSystem
22/09/2004 1:48:56 PM Status: Collecting
Win32_ComputerSystem
22/09/2004 1:48:56 PM Status: Collecting
Win32_Processor
22/09/2004 1:48:58 PM ERROR: Line 1: Incorrect
syntax near 'c09'.
22/09/2004 1:48:58 PM Status: Closing Unit 1
22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
(run_id,srv_id,BootDevice,BuildNumber,BuildType,Caption,Co
deSet,CountryCode,CSDVersion,CSName,CurrentTimeZone,Debug,
Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles,FreeVirt
ualMemory,InstallDate,LastBootUpTime,LocalDateTime,Locale,
MaxProcessMemorySize,NumberOfProcesses,NumberOfUsers,OSLan
guage,OSProductSuite,PAEEnabled,ServicePackMajorVersion,Se
rvicePackMinorVersion,SizeStoredInPagingFiles,SystemDevice
,SystemDirectory,TotalVirtualMemorySize,TotalVisibleMemory
Size,Version,WindowsDirectory) Values (3,
1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
Free', 'Microsoft Windows XP
Professional', '1252', '61', 'Service Pack 1', 'test01',
600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
3112032, 522220, '5.1.2600', 'C:\WINDOWS')
22/09/2004 1:48:58 PM WARNING: WMI Collector
encountered critical error. Abandoning Collector.
22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
(run_id,srv_id,BootDevice,BuildNumber,BuildType,Caption,Co
deSet,CountryCode,CSDVersion,CSName,CurrentTimeZone,Debug,
Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles,FreeVirt
ualMemory,InstallDate,LastBootUpTime,LocalDateTime,Locale,
MaxProcessMemorySize,NumberOfProcesses,NumberOfUsers,OSLan
guage,OSProductSuite,PAEEnabled,ServicePackMajorVersion,Se
rvicePackMinorVersion,SizeStoredInPagingFiles,SystemDevice
,SystemDirectory,TotalVirtualMemorySize,TotalVisibleMemory
Size,Version,WindowsDirectory) Values (3,
1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
Free', 'Microsoft Windows XP
Professional', '1252', '61', 'Service Pack 1', 'test01',
600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
3112032, 522220, '5.1.2600', 'C:\WINDOWS')
22/09/2004 1:48:58 PM ERROR: test01: Collection
failed; Error:104; Provider Error: 170
22/09/2004 1:48:58 PM ERROR: Critical Repository
Failure
22/09/2004 1:48:58 PM SQLH2 is shutting down
22/09/2004 1:48:58 PM Closing Log
Has anyone come acrosss this error and can advise.
ThanksYes, i also have problems too.
And i think there is a problem with our collation settings. (Which is
Turkish_CI_AS).
Also reports are not working because of that i think. Hate this localization
problems.
I will try on English Locale server and see if it works..
"anonymous@.discussions.microsoft.com" wrote:
> Hi All
> I am reciving the following error when running the
> Microsoft SQL Server Health and History Tool:
> 22/09/2004 1:48:56 PM INFO: version: 8.00.760
> 22/09/2004 1:48:56 PM Status: RUN
> 22/09/2004 1:48:56 PM Status: Initializing
> collector: WMI
> 22/09/2004 1:48:56 PM Status: Running WMI collector
> 22/09/2004 1:48:56 PM Status: Opening Unit 1
> (OS/CS)
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_OperatingSystem
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_ComputerSystem
> 22/09/2004 1:48:56 PM Status: Collecting
> Win32_Processor
> 22/09/2004 1:48:58 PM ERROR: Line 1: Incorrect
> syntax near 'c09'.
> 22/09/2004 1:48:58 PM Status: Closing Unit 1
> 22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
> (run_id,srv_id,BootDevice,BuildNumber,BuildType,Caption,Co
> deSet,CountryCode,CSDVersion,CSName,CurrentTimeZone,Debug,
> Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles,FreeVirt
> ualMemory,InstallDate,LastBootUpTime,LocalDateTime,Locale,
> MaxProcessMemorySize,NumberOfProcesses,NumberOfUsers,OSLan
> guage,OSProductSuite,PAEEnabled,ServicePackMajorVersion,Se
> rvicePackMinorVersion,SizeStoredInPagingFiles,SystemDevice
> ,SystemDirectory,TotalVirtualMemorySize,TotalVisibleMemory
> Size,Version,WindowsDirectory) Values (3,
> 1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
> Free', 'Microsoft Windows XP
> Professional', '1252', '61', 'Service Pack 1', 'test01',
> 600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
> 08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
> 0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
> 2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
> 3112032, 522220, '5.1.2600', 'C:\WINDOWS')
> 22/09/2004 1:48:58 PM WARNING: WMI Collector
> encountered critical error. Abandoning Collector.
> 22/09/2004 1:48:58 PM ERROR: Insert dbo.c_wmi_OS
> (run_id,srv_id,BootDevice,BuildNumber,BuildType,Caption,Co
> deSet,CountryCode,CSDVersion,CSName,CurrentTimeZone,Debug,
> Distrib,FreePhysicalMemory,FreeSpaceInPagingFiles,FreeVirt
> ualMemory,InstallDate,LastBootUpTime,LocalDateTime,Locale,
> MaxProcessMemorySize,NumberOfProcesses,NumberOfUsers,OSLan
> guage,OSProductSuite,PAEEnabled,ServicePackMajorVersion,Se
> rvicePackMinorVersion,SizeStoredInPagingFiles,SystemDevice
> ,SystemDirectory,TotalVirtualMemorySize,TotalVisibleMemory
> Size,Version,WindowsDirectory) Values (3,
> 1, '\Device\HarddiskVolume2', '2600', 'Multiprocessor
> Free', 'Microsoft Windows XP
> Professional', '1252', '61', 'Service Pack 1', 'test01',
> 600, 0, 0, 102104, 2102060, 2204164, '01/09/2004
> 08:35:38', '09/21/2004 04:34:18', '09/22/2004 13:48:56',
> 0c09, 2097024, 55, 5, 1033, -1, 0, 1, 0,
> 2589812, '\Device\HarddiskVolume2', 'C:\WINDOWS\System32',
> 3112032, 522220, '5.1.2600', 'C:\WINDOWS')
> 22/09/2004 1:48:58 PM ERROR: test01: Collection
> failed; Error:104; Provider Error: 170
> 22/09/2004 1:48:58 PM ERROR: Critical Repository
> Failure
> 22/09/2004 1:48:58 PM SQLH2 is shutting down
> 22/09/2004 1:48:58 PM Closing Log
>
> Has anyone come acrosss this error and can advise.
> Thanks
>

Microsoft SQL Server Health and History Tool

Anyone have any experience or comments using Microsoft SQL Server Health and
History Tool?Hi,
The Microsoft SQL Server Health and History Tool (SQLH2) allows you to
collect information from instances of SQL Server, store this information,
and run reports against the data in order to determine how SQL Server is
being used.
http://www.microsoft..com/downloads/details.aspx?FamilyID=eedd10d6-75f7-4763
-86de-d2347b8b5f89&DisplayLang=en
Run the SQLH2 collector to help us collect feature usage information on SQL
2005(and SQL 2000) deployments. Then when the reports come out you (and
your customers) can easily view the collections.
Please understand, this question appears to be consulting in nature.
Although this newsgroup is here to provide break/fix resolution, we are
happy to provide general information and suggestions on it here and you may
receive suggestions from other partners on this topic both here and in the
public newsgroup for this product.
If you need further information, we would also like to introduce you to the
CUSTOMER SERVICE AND SUPPORT (CSS) Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/gp/advisoryservice
Outside of the US/Canada:
http://support.microsoft.com/common/international.aspx
Thanks for understanding.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Reply-To: "TM" <tmcclenn@.community.nospam>
>>From: "TM" <tmcclenn@.community.nospam>
>>Subject: Microsoft SQL Server Health and History Tool
>>Date: Mon, 6 Nov 2006 10:45:23 -0500
>>Lines: 5
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <#B$rSqbAHHA.1224@.TK2MSFTNGP04.phx.gbl>
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: ip70-161-7-200.hr.hr.cox.net 70.161.7.200
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:450417
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>Anyone have any experience or comments using Microsoft SQL Server Health
and
>>History Tool?
>>
>>

Microsoft SQL Server Health and History Tool

Anyone have any experience or comments using Microsoft SQL Server Health and
History Tool?Hi,
The Microsoft SQL Server Health and History Tool (SQLH2) allows you to
collect information from instances of SQL Server, store this information,
and run reports against the data in order to determine how SQL Server is
being used.
http://www.microsoft..com/downloads...d10d6-75f7-4763
-86de-d2347b8b5f89&DisplayLang=en
Run the SQLH2 collector to help us collect feature usage information on SQL
2005(and SQL 2000) deployments. Then when the reports come out you (and
your customers) can easily view the collections.
Please understand, this question appears to be consulting in nature.
Although this newsgroup is here to provide break/fix resolution, we are
happy to provide general information and suggestions on it here and you may
receive suggestions from other partners on this topic both here and in the
public newsgroup for this product.
If you need further information, we would also like to introduce you to the
CUSTOMER SERVICE AND SUPPORT (CSS) Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/gp/advisoryservice
Outside of the US/Canada:
http://support.microsoft.com/common/international.aspx
Thanks for understanding.
Best regards,
Vincent Xu
Microsoft Online Partner Support
========================================
==============
Get Secure! - www.microsoft.com/security
========================================
==============
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties,and confers no rights.
========================================
==============
--[vbcol=seagreen]
and[vbcol=seagreen]