Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Friday, March 23, 2012
Frontpage & MS SQL Connection Error-Please Help
Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated
This error means that the account is unknown on the SQL Server machine.
For example, suppose I create a user named User1 on computer Machine1.
Then I try to log into SQL Server on Machine2 using User1 from Machine1.
This is not possible because Machine2 has no idea about User1.
However, there is one trick you can employ to make this work, an old NTLM
trick that is used here.
If you create same user name on 2 machines with same exact password, then it
is possible for these accounts to work in this fashion (User1 from Machine1
to log into Machine2 as User1).
So in your case you need to create SQLUser on both machines with exact same
password and in theory it should work.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbmhoqAck6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated
This error means that the account is unknown on the SQL Server machine.
For example, suppose I create a user named User1 on computer Machine1.
Then I try to log into SQL Server on Machine2 using User1 from Machine1.
This is not possible because Machine2 has no idea about User1.
However, there is one trick you can employ to make this work, an old NTLM
trick that is used here.
If you create same user name on 2 machines with same exact password, then it
is possible for these accounts to work in this fashion (User1 from Machine1
to log into Machine2 as User1).
So in your case you need to create SQLUser on both machines with exact same
password and in theory it should work.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbmhoqAck6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
Frontpage & MS SQL Connection Error-Please Help
Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
Frontpage & MS SQL Connection Error-Please Help
Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
--
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
--
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
Frontpage & MS SQL Connection Error-Please Help
Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated
If you are not on a domain your best bet is probably to use SQL
Authentication. You will pass a user name and password from the web page to
SQL Server.
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
|||I meant to mention in my previous post that you can look up connection
string examples on www.connectionstrings.com
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
sql
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"
I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.
On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..
Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.
Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.
Any help will be very much appriciated
If you are not on a domain your best bet is probably to use SQL
Authentication. You will pass a user name and password from the web page to
SQL Server.
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
|||I meant to mention in my previous post that you can look up connection
string examples on www.connectionstrings.com
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-3g@.giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
> Any help will be very much appriciated
sql
Monday, March 12, 2012
Frequent generated log files takes up the whole system drive (C:\)
This happend twice on two different servers. A 33MB reporting service log was
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
......
Thanks,
MichaelCheck out this hotfix:
http://support.microsoft.com/kb/885286/
This problem should be fixed in SP2.
--
Adrian M.
MCP
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
> was
> generated every 3 minutes until it took up the entire C:\ drive. The log
> file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
> C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael|||Hi Michael,
Yes, as Adrian M said this is a known issue for us now. A supported hotfix
is now available from Microsoft, but it is only intended to correct the
problem that is described in this article. Only apply it to systems that
are experiencing this specific problem. This hotfix may receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next Microsoft SQL Server 2000 Reporting
Services service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note that if will be a *free* incident if you only asking for the hotfix
from PSS :)
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||As a quick fix, you can delete old logs using a scheduled job. Check
http://solidqualitylearning.com/blogs/dejan/archive/2004/12/19/225.aspx.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
was
> generated every 3 minutes until it took up the entire C:\ drive. The log
file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
......
Thanks,
MichaelCheck out this hotfix:
http://support.microsoft.com/kb/885286/
This problem should be fixed in SP2.
--
Adrian M.
MCP
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
> was
> generated every 3 minutes until it took up the entire C:\ drive. The log
> file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
> C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael|||Hi Michael,
Yes, as Adrian M said this is a known issue for us now. A supported hotfix
is now available from Microsoft, but it is only intended to correct the
problem that is described in this article. Only apply it to systems that
are experiencing this specific problem. This hotfix may receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next Microsoft SQL Server 2000 Reporting
Services service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note that if will be a *free* incident if you only asking for the hotfix
from PSS :)
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||As a quick fix, you can delete old logs using a scheduled job. Check
http://solidqualitylearning.com/blogs/dejan/archive/2004/12/19/225.aspx.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Michael" <missisummer@.community.nospam> wrote in message
news:C1FE7688-A420-49E1-A17C-0FC736DECC7D@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
was
> generated every 3 minutes until it took up the entire C:\ drive. The log
file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael
Frequent generated log file takes up the entire system drive
This happend twice on two different servers. A 33MB reporting service log was
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
.......
Thanks,
Michael
This is a known bug fixed in the imminent SP2 for Reporting Services.
http://support.microsoft.com/kb/885286/
You can get a hotfix, details are in the KB article. What've I've tended to
do is just set up a scheduled task to check the size of the logs folder and
if it gets over a certain size start deleting old logs.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Michael" <missisummer@.community.nospam> wrote in message
news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
> was
> generated every 3 minutes until it took up the entire C:\ drive. The log
> file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
> C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael
|||Jasper,
My DBA is looking for this. Would you be able to send me the code for this
scheduled task. I'd apprciate it.
Bill..
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:%238P0SFuNFHA.604@.TK2MSFTNGP10.phx.gbl...
> This is a known bug fixed in the imminent SP2 for Reporting Services.
> http://support.microsoft.com/kb/885286/
> You can get a hotfix, details are in the KB article. What've I've tended
> to do is just set up a scheduled task to check the size of the logs folder
> and if it gets over a certain size start deleting old logs.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Michael" <missisummer@.community.nospam> wrote in message
> news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
>
|||> Jasper,
> My DBA is looking for this. Would you be able to send me the code for
this
> scheduled task. I'd apprciate it.
> Bill..
You can use something I create couple of months ago for diferent purposes,
but can apply to this problem as well:
http://solidqualitylearning.com/blog...2/19/225.aspx.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
.......
Thanks,
Michael
This is a known bug fixed in the imminent SP2 for Reporting Services.
http://support.microsoft.com/kb/885286/
You can get a hotfix, details are in the KB article. What've I've tended to
do is just set up a scheduled task to check the size of the logs folder and
if it gets over a certain size start deleting old logs.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Michael" <missisummer@.community.nospam> wrote in message
news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
> This happend twice on two different servers. A 33MB reporting service log
> was
> generated every 3 minutes until it took up the entire C:\ drive. The log
> file
> has a header then repeat some message as in the following exerpt for 30+
> thousand times. Then it starts another log file endlessly until the whole
> C:\
> drive is used.
> It has caused the interruptions of programs hosted on the server. After
> delete the logs the reporting service is back to normal. But we need to
> prevent this from happening again.
> <Header>
> <Product>Microsoft SQL Server Reporting Services Version
> 8.00.743.00</Product>
> <Locale>en-US</Locale>
> <TimeZone>Eastern Standard Time</TimeZone>
> <Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
> <SystemName>WSReport</SystemName>
> <OSName>Microsoft Windows NT 5.2.3790.0</OSName>
> <OSVersion>5.2.3790.0</OSVersion>
> </Header>
> ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
> Cleaned
> 0 broken snapshots, 0 chunks
> ......
> Thanks,
> Michael
|||Jasper,
My DBA is looking for this. Would you be able to send me the code for this
scheduled task. I'd apprciate it.
Bill..
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:%238P0SFuNFHA.604@.TK2MSFTNGP10.phx.gbl...
> This is a known bug fixed in the imminent SP2 for Reporting Services.
> http://support.microsoft.com/kb/885286/
> You can get a hotfix, details are in the KB article. What've I've tended
> to do is just set up a scheduled task to check the size of the logs folder
> and if it gets over a certain size start deleting old logs.
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Michael" <missisummer@.community.nospam> wrote in message
> news:6A7FD5FA-AA33-4B15-8472-D204B6D8B75A@.microsoft.com...
>
|||> Jasper,
> My DBA is looking for this. Would you be able to send me the code for
this
> scheduled task. I'd apprciate it.
> Bill..
You can use something I create couple of months ago for diferent purposes,
but can apply to this problem as well:
http://solidqualitylearning.com/blog...2/19/225.aspx.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
Freqent generated log files took up the entire system drive
This happend twice on two different servers. A 33MB reporting service log was
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
.......
Thanks,
Michael
Hi Michael,
I found you have another two posts with the same topic in
microsoft.public.sqlserver.reportingsvcs and
microsoft.public.sqlserver.tools, both has response from MVP and community
members. To keep the integrity of newsgroup and benefit others. I will
follwo up the questions in microsoft.public.sqlserver.reportingsvcs
instead of these two.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
generated every 3 minutes until it took up the entire C:\ drive. The log file
has a header then repeat some message as in the following exerpt for 30+
thousand times. Then it starts another log file endlessly until the whole C:\
drive is used.
It has caused the interruptions of programs hosted on the server. After
delete the logs the reporting service is back to normal. But we need to
prevent this from happening again.
<Header>
<Product>Microsoft SQL Server Reporting Services Version
8.00.743.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\LogFiles\ReportServerService__03_29_2005_ 18_55_53.log</Path>
<SystemName>WSReport</SystemName>
<OSName>Microsoft Windows NT 5.2.3790.0</OSName>
<OSVersion>5.2.3790.0</OSVersion>
</Header>
ReportingServicesService!runningjobs!118c!3/29/2005-18:55:53:: i INFO:
Execution Log Entry Expiration timer enabled: Cycle: 25446 seconds
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiring old execution log entries
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO:
Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a30!3/29/2005-18:55:53:: i INFO: Cleaned
0 broken snapshots, 0 chunks
.......
Thanks,
Michael
Hi Michael,
I found you have another two posts with the same topic in
microsoft.public.sqlserver.reportingsvcs and
microsoft.public.sqlserver.tools, both has response from MVP and community
members. To keep the integrity of newsgroup and benefit others. I will
follwo up the questions in microsoft.public.sqlserver.reportingsvcs
instead of these two.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, February 26, 2012
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on
"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on
"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
--
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> > We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> > database from one to the other. The free text search runs on the original
> > server and produces results but on the new server it runs but produces a
> > nil
> > return.
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> >
> > Can anyone offer any help?
> >
> > --
> > Confused but battling on
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
--
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text search
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> > We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> > database from one to the other. The free text search runs on the original
> > server and produces results but on the new server it runs but produces a
> > nil
> > return.
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> >
> > Can anyone offer any help?
> >
> > --
> > Confused but battling on
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
Free Text Search
We have two SQL Server 2000 servers with SP4 loaded. We have copied a
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text searc
h
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>
database from one to the other. The free text search runs on the original
server and produces results but on the new server it runs but produces a nil
return.
Can anyone offer any help?
Confused but battling on"Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> We have two SQL Server 2000 servers with SP4 loaded. We have copied a
> database from one to the other. The free text search runs on the original
> server and produces results but on the new server it runs but produces a
> nil
> return.
Free text?
I assume you mean FULL TEXT?
Did you copy the Full-text indices to the same place?
Did you enable full-text on the new database?
How was the data moved?
> Can anyone offer any help?
> --
> Confused but battling on
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Sorry I did mean full text search. We have tried to re create the indices
and the search but it still returns a nil result. The full text search
service is running.
How do you enable full text search on a database?
The database was moved by backing up to a device, then copying the device to
the new location and restoring it (changing the file locations etc).
Eeverything else in the database works fine; it is just this full text searc
h
--
Confused but battling on
"Greg D. Moore (Strider)" wrote:
> "Madame Artois" <MadameArtois@.discussions.microsoft.com> wrote in message
> news:C3B84E7A-4085-4089-85B8-820174CC303E@.microsoft.com...
> Sorry I did mean Full Text Search.
The full text searches had been copied to the same place and I'm not sure
what you mean about enabling full test searches on the database.
The full text search service is running
> Free text?
> I assume you mean FULL TEXT?
> Did you copy the Full-text indices to the same place?
> Did you enable full-text on the new database?
> How was the data moved?
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>
Subscribe to:
Posts (Atom)