Problems using SQL: sp2

Showing posts with label sp2. Show all posts

Wednesday, March 28, 2012

Problems with SQLh2 and reporting services 2000

Problems with SQLH2

Hi friends!
I have installed SQLH2 reporting and collector services and all of them work
fine. I configured IIS WIth Reporting services with SP2 and uploaded the
reports pages, the connection to the database seems to be well, but when i
try to see some data (not happens with all reports) a recieve errors like
this:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
OR:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_TraceProperty'.
What'is wrong?
Can anyone help me?
Thanks in advance.
Martin
Martin
The errors you see mean your reports connect to the wrong database.
Check your datasource and make sure your reports are using correct
datasource.
You can download 'Additional doc.cab' from
http://www.microsoft.com/downloads/d...DisplayLang=en
You can find 'ComprehensiveSQLH2InstallDoc.doc' in the cab. It has a big
section on configuring reports.
"Tinchos" wrote:

> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_TraceProperty'.
>
|||Hi,
I have same problem.
'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.sql
script.
'd_DbObjectType', 'd_UserAcces' also.
Most of reports from ReportsV2 are missing some object or procedure.
Scripts and programs are downloaded today.
Thanks,
Don
"Tinchos" wrote:

> Hi friends!
> I have installed SQLH2 reporting and collector services and all of them work
> fine. I configured IIS WIth Reporting services with SP2 and uploaded the
> reports pages, the connection to the database seems to be well, but when i
> try to see some data (not happens with all reports) a recieve errors like
> this:
>
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_TraceProperty'.
>
> What'is wrong?
> Can anyone help me?
>
> Thanks in advance.
> Martin
>
|||Sorry I missed that the first time
Reports package (ReportV2.cab) contains 'New Dictionaries.sql' script, which
creates objects you mention.
"Don" wrote:

> I have same problem.
> 'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.sql
> script.
> 'd_DbObjectType', 'd_UserAcces' also.
> Most of reports from ReportsV2 are missing some object or procedure.
> Scripts and programs are downloaded today.

Problems with SQLH2

Hi friends!
I have installed SQLH2 reporting and collector services and all of them work
fine. I configured IIS WIth Reporting services with SP2 and uploaded the
reports pages, the connection to the database seems to be well, but when i
try to see some data (not happens with all reports) a recieve errors like
this:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
OR:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_TraceProperty'.
What'is wrong?
Can anyone help me?
Thanks in advance.
MartinMartin
The errors you see mean your reports connect to the wrong database.
Check your datasource and make sure your reports are using correct
datasource.
You can download 'Additional doc.cab' from
2347b8b5f89&DisplayLang=en" target="_blank">http://www.microsoft.com/downloads/...&DisplayLang=en
You can find 'ComprehensiveSQLH2InstallDoc.doc' in the cab. It has a big
section on configuring reports.
"Tinchos" wrote:

> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Ge
t
> Online Help
> Invalid object name 'd_TraceProperty'.
>|||Hi,
I have same problem.
'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.sql
script.
'd_DbObjectType', 'd_UserAcces' also.
Most of reports from ReportsV2 are missing some object or procedure.
Scripts and programs are downloaded today.
Thanks,
Don
"Tinchos" wrote:

> Hi friends!
> I have installed SQLH2 reporting and collector services and all of them wo
rk
> fine. I configured IIS WIth Reporting services with SP2 and uploaded the
> reports pages, the connection to the database seems to be well, but when i
> try to see some data (not happens with all reports) a recieve errors like
> this:
>
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Ge
t
> Online Help
> Invalid object name 'd_TraceProperty'.
>
> What'is wrong?
> Can anyone help me?
>
> Thanks in advance.
> Martin
>|||Sorry I missed that the first time
Reports package (ReportV2.cab) contains 'New Dictionaries.sql' script, which
creates objects you mention.
"Don" wrote:

> I have same problem.
> 'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.s
ql
> script.
> 'd_DbObjectType', 'd_UserAcces' also.
> Most of reports from ReportsV2 are missing some object or procedure.
> Scripts and programs are downloaded today.

Problems with SQLH2

Hi friends!
I have installed SQLH2 reporting and collector services and all of them work
fine. I configured IIS WIth Reporting services with SP2 and uploaded the
reports pages, the connection to the database seems to be well, but when i
try to see some data (not happens with all reports) a recieve errors like
this:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
OR:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
Online Help
Invalid object name 'd_TraceProperty'.
What'is wrong?
Can anyone help me?
Thanks in advance.
MartinMartin
The errors you see mean your reports connect to the wrong database.
Check your datasource and make sure your reports are using correct
datasource.
You can download 'Additional doc.cab' from
http://www.microsoft.com/downloads/details.aspx?FamilyID=eedd10d6-75f7-4763-86de-d2347b8b5f89&DisplayLang=en
You can find 'ComprehensiveSQLH2InstallDoc.doc' in the cab. It has a big
section on configuring reports.
"Tinchos" wrote:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_TraceProperty'.
>|||Hi,
I have same problem.
'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.sql
script.
'd_DbObjectType', 'd_UserAcces' also.
Most of reports from ReportsV2 are missing some object or procedure.
Scripts and programs are downloaded today.
Thanks,
Don
"Tinchos" wrote:
> Hi friends!
> I have installed SQLH2 reporting and collector services and all of them work
> fine. I configured IIS WIth Reporting services with SP2 and uploaded the
> reports pages, the connection to the database seems to be well, but when i
> try to see some data (not happens with all reports) a recieve errors like
> this:
>
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'CS'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_DomainRole'. Invalid object name 'd_DomainRole'.
> OR:
> An error has occurred during report processing. (rsProcessingAborted) Get
> Online Help
> Query execution failed for data set 'Traces'. (rsErrorExecutingCommand) Get
> Online Help
> Invalid object name 'd_TraceProperty'.
>
> What'is wrong?
> Can anyone help me?
>
> Thanks in advance.
> Martin
>|||Sorry I missed that the first time
Reports package (ReportV2.cab) contains 'New Dictionaries.sql' script, which
creates objects you mention.
"Don" wrote:
> I have same problem.
> 'd_DomainRole' is missing in SQLH2Repository database, and in SQLH2setup.sql
> script.
> 'd_DbObjectType', 'd_UserAcces' also.
> Most of reports from ReportsV2 are missing some object or procedure.
> Scripts and programs are downloaded today.

Monday, March 26, 2012

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, whic
h is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that shou
ld mean you can connect
to the default but not named. You seem to have the other way around. One mor
e thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>sql

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
Lourival
Are both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegr oups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>
|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor
|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>
|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival
|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Cant connect on 2000

Any idea? Have i to reinstall 2000?

Tks,
Lourival(lourivalsjr@.gmail.com) writes:
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?

Exactly which service-pack level of SQL 2000 do you have? You can view
this on the first line of
C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG
(if this is the instance directory for SQL 2000.)

I believe you need at least SP3 (8.00.760 to run in parallel with SQL 2005.)

Another thing to try is to open the Server and Client Network Utilities of
SQL 2000, and make sure that both use TCP/IP. For local connections,
shared memory is the default, but if it for some reason does not work, you
can try TCP/IP.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Wednesday, March 21, 2012

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Hello all,
I'll get to the problem, which I have a tough time finding out the
root cause.
1) I have SQL Server 2000 Installed, with the following patch/SP
version:
Version: 8.00.760
2) My database is running on a server with Windows Server 2003 SP2.
The Problem:
All of the automated scheduled backups used to work all perfectly
well. We have an IC backup that we've implemented and it hasn't ever
caused us issues (since it is our standard)...BUT...when our
security team decided to update the Service Pack to SP2, we noticed
that the scheduled backup job would cease to run...YET...it shows
that the backup has been taken on the Jobs Activity Monitor (Even in
the History of that job), but once we look at it, the job only fired
and completed in 1 second, when it takes on average (1-2 mins).
But here's something even more wierd...it takes a backup whenever it
feels like...notably every 2-3 days...and everything is perfect. Then
you get 3-4 days of no backups. We've been watching this odd behaivour
for the past 1 month or so.
Is there a patch I am missing for SQL Server 2000? Or is the Windows
Server 2003 SP2, causing me to not properly take my backups since it
is blocking or has stopped a particular step.
It sounds strange. Have you looked into ERROR.LOG ? Any entries?
"Mohd Al Junaibi" <mohamed.aljunaibi@.gmail.com> wrote in message
news:d9f861f4-3667-49cc-8eae-a51b75aff9db@.s19g2000prg.googlegroups.com...
> Hello all,
> I'll get to the problem, which I have a tough time finding out the
> root cause.
> 1) I have SQL Server 2000 Installed, with the following patch/SP
> version:
> Version: 8.00.760
> 2) My database is running on a server with Windows Server 2003 SP2.
> The Problem:
> All of the automated scheduled backups used to work all perfectly
> well. We have an IC backup that we've implemented and it hasn't ever
> caused us issues (since it is our standard)...BUT...when our
> security team decided to update the Service Pack to SP2, we noticed
> that the scheduled backup job would cease to run...YET...it shows
> that the backup has been taken on the Jobs Activity Monitor (Even in
> the History of that job), but once we look at it, the job only fired
> and completed in 1 second, when it takes on average (1-2 mins).
> But here's something even more wierd...it takes a backup whenever it
> feels like...notably every 2-3 days...and everything is perfect. Then
> you get 3-4 days of no backups. We've been watching this odd behaivour
> for the past 1 month or so.
> Is there a patch I am missing for SQL Server 2000? Or is the Windows
> Server 2003 SP2, causing me to not properly take my backups since it
> is blocking or has stopped a particular step.
|||I do get entries in the ERROR.LOG file.
But they are only there once the backup is successfully done. The
backups are to happen on a daily basis...but you'll notice in the
ERROR.LOG that there are gaps of 2,3 and sometimes 4 days in between.
Again, this is strange, as in the Jobs Activity Monitor, it says that
the job was successfully run, yet in reality it didn't as it fired and
completed the job within 1 second...which is big sign that OS is
stoping something. But I'm speculating.
Here's the error logs (the database I'm talking about is:
"MyDatabase") I've edited just to make it as informative as possible:
2007-10-31 11:08:13.03 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-10-31 11:08:13.03 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-10-31 11:08:13.03 server All rights reserved.
2007-10-31 11:08:13.03 server Server Process ID is 1892.
2007-10-31 11:08:13.03 server Logging SQL Server messages in file
'd:\MSSQL\log\ERRORLOG'.
2007-10-31 11:08:13.06 server SQL Server is starting at priority
class 'normal'(4 CPUs
detected).
2007-10-31 11:08:13.71 server SQL Server configured for thread mode
processing.
2007-10-31 11:08:13.78 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000]
Lock Owner Blocks.
2007-10-31 11:08:14.09 server Attempting to initialize Distributed
Transaction
Coordinator.
2007-10-31 11:08:17.34 spid3 Starting up database 'master'.
2007-10-31 11:08:22.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2007-10-31 11:08:22.40 spid5 Starting up database 'model'.
2007-10-31 11:08:22.43 spid3 Server name is 'XYZ'.
2007-10-31 11:08:22.62 spid8 Starting up database 'msdb'.
2007-10-31 11:08:22.64 spid12 Starting up database 'MyDatabase'.
2007-10-31 11:08:23.25 spid5 Clearing tempdb database.
2007-10-31 11:08:26.45 server SQL server listening on 10.40.50.210:
1433.
2007-10-31 11:08:26.45 server SQL server listening on 127.0.0.1:
1433.
2007-10-31 11:08:26.51 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2007-10-31 11:08:26.51 server SQL Server is ready for client
connections
2007-10-31 11:08:27.70 spid5 Starting up database 'tempdb'.
2007-10-31 11:08:28.17 spid5 Analysis of database 'tempdb' (2) is
100% complete
(approximately 0 more seconds)
2007-10-31 11:08:28.64 spid3 Recovery complete.
2007-10-31 11:08:28.64 spid3 SQL global counter collection task is
created.
2007-10-31 11:08:32.39 spid51 Using 'xpsqlbot.dll' version
'2000.80.194' to execute
extended stored procedure 'xp_qv'.
2007-11-01 00:10:01.07 spid53 Using 'xplog70.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_cmdshell'.
2007-11-01 00:10:03.07 spid53 Using 'xpstar.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_instance_regread'.
2007-11-01 08:06:08.26 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31369, first LSN:
38008:338:1, last LSN:
38008:404:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
errors and repaired 0 errors.
2007-11-08 00:10:28.80 spid55 Starting up database 'MyDatabase'.
2007-11-08 00:10:47.85 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31513, first LSN:
38022:1404:1, last LSN:
38022:1408:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-10 00:10:00.80 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:00.91 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:02.22 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1798:1, last
LSN: 155:1800:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-10 00:10:02.49 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-10 00:10:02.57 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:04.30 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 980:417:1, last
LSN: 980:420:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-10 00:10:27.83 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.86 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.93 spid55 Starting up database 'MyDatabase'.
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-19 00:10:26.45 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:29.02 spid57 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.05 spid57 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.12 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:48.69 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31881, first LSN:
38051:74:1, last LSN:
38051:78:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-21 00:10:01.23 spid56 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:01.35 spid56 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:02.71 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1920:1, last
LSN: 155:1922:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-21 00:10:02.98 spid56 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-21 00:10:03.05 spid56 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:04.96 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 981:198:1, last
LSN: 981:201:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-21 00:10:26.87 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:29.51 spid56 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.55 spid56 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.63 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:49.37 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32033, first LSN:
38073:707:1, last LSN:
38073:711:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-24 00:10:00.47 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:00.60 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:02.00 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1969:1, last
LSN: 155:1971:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-24 00:10:02.28 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-24 00:10:02.36 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:04.17 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1843, first LSN: 981:274:1, last
LSN: 981:277:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-24 00:10:25.86 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:28.50 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.53 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.61 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:48.19 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32161, first LSN:
38101:76:1, last LSN:
38101:80:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
|||I've just realised that the main issue is that in one of backup
scripts that runs (and it is automated)...we have used:
isql command to run the back, and this would at times work, and also
not work.
by using the osql command instead, everything worked out fine.
Example:
Instead of having your statement:
isql -Usa -P -SSERVER
You have:
osql -Usa -P -SSERVER
That worked for me. The statement for the backup was in "isql" and I
converted it to "osql" and the rest remained untouched, and everything
started working again.
sql

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Hello all,
I'll get to the problem, which I have a tough time finding out the
root cause.
1) I have SQL Server 2000 Installed, with the following patch/SP
version:
Version: 8.00.760
2) My database is running on a server with Windows Server 2003 SP2.
The Problem:
All of the automated scheduled backups used to work all perfectly
well. We have an IC backup that we've implemented and it hasn't ever
caused us issues (since it is our standard)...BUT...when our
security team decided to update the Service Pack to SP2, we noticed
that the scheduled backup job would cease to run...YET...it shows
that the backup has been taken on the Jobs Activity Monitor (Even in
the History of that job), but once we look at it, the job only fired
and completed in 1 second, when it takes on average (1-2 mins).
But here's something even more wierd...it takes a backup whenever it
feels like...notably every 2-3 days...and everything is perfect. Then
you get 3-4 days of no backups. We've been watching this odd behaivour
for the past 1 month or so.
Is there a patch I am missing for SQL Server 2000? Or is the Windows
Server 2003 SP2, causing me to not properly take my backups since it
is blocking or has stopped a particular step.It sounds strange. Have you looked into ERROR.LOG ? Any entries?
"Mohd Al Junaibi" <mohamed.aljunaibi@.gmail.com> wrote in message
news:d9f861f4-3667-49cc-8eae-a51b75aff9db@.s19g2000prg.googlegroups.com...
> Hello all,
> I'll get to the problem, which I have a tough time finding out the
> root cause.
> 1) I have SQL Server 2000 Installed, with the following patch/SP
> version:
> Version: 8.00.760
> 2) My database is running on a server with Windows Server 2003 SP2.
> The Problem:
> All of the automated scheduled backups used to work all perfectly
> well. We have an IC backup that we've implemented and it hasn't ever
> caused us issues (since it is our standard)...BUT...when our
> security team decided to update the Service Pack to SP2, we noticed
> that the scheduled backup job would cease to run...YET...it shows
> that the backup has been taken on the Jobs Activity Monitor (Even in
> the History of that job), but once we look at it, the job only fired
> and completed in 1 second, when it takes on average (1-2 mins).
> But here's something even more wierd...it takes a backup whenever it
> feels like...notably every 2-3 days...and everything is perfect. Then
> you get 3-4 days of no backups. We've been watching this odd behaivour
> for the past 1 month or so.
> Is there a patch I am missing for SQL Server 2000? Or is the Windows
> Server 2003 SP2, causing me to not properly take my backups since it
> is blocking or has stopped a particular step.|||I do get entries in the ERROR.LOG file.
But they are only there once the backup is successfully done. The
backups are to happen on a daily basis...but you'll notice in the
ERROR.LOG that there are gaps of 2,3 and sometimes 4 days in between.
Again, this is strange, as in the Jobs Activity Monitor, it says that
the job was successfully run, yet in reality it didn't as it fired and
completed the job within 1 second...which is big sign that OS is
stoping something. But I'm speculating.
Here's the error logs (the database I'm talking about is:
"MyDatabase") I've edited just to make it as informative as possible:
2007-10-31 11:08:13.03 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-10-31 11:08:13.03 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-10-31 11:08:13.03 server All rights reserved.
2007-10-31 11:08:13.03 server Server Process ID is 1892.
2007-10-31 11:08:13.03 server Logging SQL Server messages in file
'd:\MSSQL\log\ERRORLOG'.
2007-10-31 11:08:13.06 server SQL Server is starting at priority
class 'normal'(4 CPUs
detected).
2007-10-31 11:08:13.71 server SQL Server configured for thread mode
processing.
2007-10-31 11:08:13.78 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000]
Lock Owner Blocks.
2007-10-31 11:08:14.09 server Attempting to initialize Distributed
Transaction
Coordinator.
2007-10-31 11:08:17.34 spid3 Starting up database 'master'.
2007-10-31 11:08:22.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2007-10-31 11:08:22.40 spid5 Starting up database 'model'.
2007-10-31 11:08:22.43 spid3 Server name is 'XYZ'.
2007-10-31 11:08:22.62 spid8 Starting up database 'msdb'.
2007-10-31 11:08:22.64 spid12 Starting up database 'MyDatabase'.
2007-10-31 11:08:23.25 spid5 Clearing tempdb database.
2007-10-31 11:08:26.45 server SQL server listening on 10.40.50.210:
1433.
2007-10-31 11:08:26.45 server SQL server listening on 127.0.0.1:
1433.
2007-10-31 11:08:26.51 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2007-10-31 11:08:26.51 server SQL Server is ready for client
connections
2007-10-31 11:08:27.70 spid5 Starting up database 'tempdb'.
2007-10-31 11:08:28.17 spid5 Analysis of database 'tempdb' (2) is
100% complete
(approximately 0 more seconds)
2007-10-31 11:08:28.64 spid3 Recovery complete.
2007-10-31 11:08:28.64 spid3 SQL global counter collection task is
created.
2007-10-31 11:08:32.39 spid51 Using 'xpsqlbot.dll' version
'2000.80.194' to execute
extended stored procedure 'xp_qv'.
2007-11-01 00:10:01.07 spid53 Using 'xplog70.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_cmdshell'.
2007-11-01 00:10:03.07 spid53 Using 'xpstar.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_instance_regread'.
2007-11-01 08:06:08.26 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31369, first LSN:
38008:338:1, last LSN:
38008:404:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
errors and repaired 0 errors.
2007-11-08 00:10:28.80 spid55 Starting up database 'MyDatabase'.
2007-11-08 00:10:47.85 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31513, first LSN:
38022:1404:1, last LSN:
38022:1408:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-10 00:10:00.80 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:00.91 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:02.22 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1798:1, last
LSN: 155:1800:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-10 00:10:02.49 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-10 00:10:02.57 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:04.30 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 980:417:1, last
LSN: 980:420:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-10 00:10:27.83 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.86 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.93 spid55 Starting up database 'MyDatabase'.
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-19 00:10:26.45 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:29.02 spid57 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.05 spid57 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.12 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:48.69 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31881, first LSN:
38051:74:1, last LSN:
38051:78:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-21 00:10:01.23 spid56 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:01.35 spid56 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:02.71 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1920:1, last
LSN: 155:1922:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-21 00:10:02.98 spid56 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-21 00:10:03.05 spid56 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:04.96 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 981:198:1, last
LSN: 981:201:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-21 00:10:26.87 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:29.51 spid56 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.55 spid56 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.63 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:49.37 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32033, first LSN:
38073:707:1, last LSN:
38073:711:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-24 00:10:00.47 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:00.60 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:02.00 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1969:1, last
LSN: 155:1971:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-24 00:10:02.28 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-24 00:10:02.36 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:04.17 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1843, first LSN: 981:274:1, last
LSN: 981:277:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-24 00:10:25.86 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:28.50 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.53 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.61 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:48.19 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32161, first LSN:
38101:76:1, last LSN:
38101:80:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).|||I've just realised that the main issue is that in one of backup
scripts that runs (and it is automated)...we have used:
isql command to run the back, and this would at times work, and also
not work.
by using the osql command instead, everything worked out fine.
Example:
Instead of having your statement:
isql -Usa -P -SSERVER
You have:
osql -Usa -P -SSERVER
That worked for me. The statement for the backup was in "isql" and I
converted it to "osql" and the rest remained untouched, and everything
started working again.

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Hello all,
I'll get to the problem, which I have a tough time finding out the
root cause.
1) I have SQL Server 2000 Installed, with the following patch/SP
version:
Version: 8.00.760
2) My database is running on a server with Windows Server 2003 SP2.
The Problem:
All of the automated scheduled backups used to work all perfectly
well. We have an IC backup that we've implemented and it hasn't ever
caused us issues (since it is our standard)...BUT...when our
security team decided to update the Service Pack to SP2, we noticed
that the scheduled backup job would cease to run...YET...it shows
that the backup has been taken on the Jobs Activity Monitor (Even in
the History of that job), but once we look at it, the job only fired
and completed in 1 second, when it takes on average (1-2 mins).
But here's something even more wierd...it takes a backup whenever it
feels like...notably every 2-3 days...and everything is perfect. Then
you get 3-4 days of no backups. We've been watching this odd behaivour
for the past 1 month or so.
Is there a patch I am missing for SQL Server 2000? Or is the Windows
Server 2003 SP2, causing me to not properly take my backups since it
is blocking or has stopped a particular step.It sounds strange. Have you looked into ERROR.LOG ? Any entries?
"Mohd Al Junaibi" <mohamed.aljunaibi@.gmail.com> wrote in message
news:d9f861f4-3667-49cc-8eae-a51b75aff9db@.s19g2000prg.googlegroups.com...
> Hello all,
> I'll get to the problem, which I have a tough time finding out the
> root cause.
> 1) I have SQL Server 2000 Installed, with the following patch/SP
> version:
> Version: 8.00.760
> 2) My database is running on a server with Windows Server 2003 SP2.
> The Problem:
> All of the automated scheduled backups used to work all perfectly
> well. We have an IC backup that we've implemented and it hasn't ever
> caused us issues (since it is our standard)...BUT...when our
> security team decided to update the Service Pack to SP2, we noticed
> that the scheduled backup job would cease to run...YET...it shows
> that the backup has been taken on the Jobs Activity Monitor (Even in
> the History of that job), but once we look at it, the job only fired
> and completed in 1 second, when it takes on average (1-2 mins).
> But here's something even more wierd...it takes a backup whenever it
> feels like...notably every 2-3 days...and everything is perfect. Then
> you get 3-4 days of no backups. We've been watching this odd behaivour
> for the past 1 month or so.
> Is there a patch I am missing for SQL Server 2000? Or is the Windows
> Server 2003 SP2, causing me to not properly take my backups since it
> is blocking or has stopped a particular step.|||I do get entries in the ERROR.LOG file.
But they are only there once the backup is successfully done. The
backups are to happen on a daily basis...but you'll notice in the
ERROR.LOG that there are gaps of 2,3 and sometimes 4 days in between.
Again, this is strange, as in the Jobs Activity Monitor, it says that
the job was successfully run, yet in reality it didn't as it fired and
completed the job within 1 second...which is big sign that OS is
stoping something. But I'm speculating.
Here's the error logs (the database I'm talking about is:
"MyDatabase") I've edited just to make it as informative as possible:
2007-10-31 11:08:13.03 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-10-31 11:08:13.03 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-10-31 11:08:13.03 server All rights reserved.
2007-10-31 11:08:13.03 server Server Process ID is 1892.
2007-10-31 11:08:13.03 server Logging SQL Server messages in file
'd:\MSSQL\log\ERRORLOG'.
2007-10-31 11:08:13.06 server SQL Server is starting at priority
class 'normal'(4 CPUs
detected).
2007-10-31 11:08:13.71 server SQL Server configured for thread mode
processing.
2007-10-31 11:08:13.78 server Using dynamic lock allocation. [2500]
Lock Blocks, [5000]
Lock Owner Blocks.
2007-10-31 11:08:14.09 server Attempting to initialize Distributed
Transaction
Coordinator.
2007-10-31 11:08:17.34 spid3 Starting up database 'master'.
2007-10-31 11:08:22.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2007-10-31 11:08:22.40 spid5 Starting up database 'model'.
2007-10-31 11:08:22.43 spid3 Server name is 'XYZ'.
2007-10-31 11:08:22.62 spid8 Starting up database 'msdb'.
2007-10-31 11:08:22.64 spid12 Starting up database 'MyDatabase'.
2007-10-31 11:08:23.25 spid5 Clearing tempdb database.
2007-10-31 11:08:26.45 server SQL server listening on 10.40.50.210:
1433.
2007-10-31 11:08:26.45 server SQL server listening on 127.0.0.1:
1433.
2007-10-31 11:08:26.51 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2007-10-31 11:08:26.51 server SQL Server is ready for client
connections
2007-10-31 11:08:27.70 spid5 Starting up database 'tempdb'.
2007-10-31 11:08:28.17 spid5 Analysis of database 'tempdb' (2) is
100% complete
(approximately 0 more seconds)
2007-10-31 11:08:28.64 spid3 Recovery complete.
2007-10-31 11:08:28.64 spid3 SQL global counter collection task is
created.
2007-10-31 11:08:32.39 spid51 Using 'xpsqlbot.dll' version
'2000.80.194' to execute
extended stored procedure 'xp_qv'.
2007-11-01 00:10:01.07 spid53 Using 'xplog70.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_cmdshell'.
2007-11-01 00:10:03.07 spid53 Using 'xpstar.dll' version
'2000.80.760' to execute
extended stored procedure 'xp_instance_regread'.
2007-11-01 08:06:08.26 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31369, first LSN:
38008:338:1, last LSN:
38008:404:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
errors and repaired 0 errors.
2007-11-08 00:10:28.80 spid55 Starting up database 'MyDatabase'.
2007-11-08 00:10:47.85 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31513, first LSN:
38022:1404:1, last LSN:
38022:1408:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-10 00:10:00.80 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:00.91 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:02.22 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1798:1, last
LSN: 155:1800:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-10 00:10:02.49 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-10 00:10:02.57 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-10 00:10:04.30 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 980:417:1, last
LSN: 980:420:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-10 00:10:27.83 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.86 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-10 00:10:27.93 spid55 Starting up database 'MyDatabase'.
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-19 00:10:26.45 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:29.02 spid57 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.05 spid57 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-19 00:10:29.12 spid57 Starting up database 'MyDatabase'.
2007-11-19 00:10:48.69 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 31881, first LSN:
38051:74:1, last LSN:
38051:78:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-21 00:10:01.23 spid56 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:01.35 spid56 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:02.71 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1920:1, last
LSN: 155:1922:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-21 00:10:02.98 spid56 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-21 00:10:03.05 spid56 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-21 00:10:04.96 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1835, first LSN: 981:198:1, last
LSN: 981:201:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-21 00:10:26.87 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:29.51 spid56 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.55 spid56 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-21 00:10:29.63 spid56 Starting up database 'MyDatabase'.
2007-11-21 00:10:49.37 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32033, first LSN:
38073:707:1, last LSN:
38073:711:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).
2007-11-24 00:10:00.47 spid55 DBCC CHECKDB (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:00.60 spid55 DBCC CHECKALLOC (master) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:02.00 backup Database backed up: Database: master,
creation date(time):
2007/10/31(11:08:17), pages dumped: 1867, first LSN: 155:1969:1, last
LSN: 155:1971:1,
number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'master_Backup'}).
2007-11-24 00:10:02.28 spid55 DBCC CHECKDB (msdb) executed by
sqladm found 0 errors and
repaired 0 errors.
2007-11-24 00:10:02.36 spid55 DBCC CHECKALLOC (msdb) executed by
sqladm found 0 errors
and repaired 0 errors.
2007-11-24 00:10:04.17 backup Database backed up: Database: msdb,
creation date(time):
2000/08/06(01:40:56), pages dumped: 1843, first LSN: 981:274:1, last
LSN: 981:277:1, number
of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'msdb_Backup'}).
2007-11-24 00:10:25.86 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:28.50 spid55 DBCC CHECKDB (MyDatabase) executed by
sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.53 spid55 DBCC CHECKALLOC (MyDatabase) executed
by sqladm found 0
errors and repaired 0 errors.
2007-11-24 00:10:28.61 spid55 Starting up database 'MyDatabase'.
2007-11-24 00:10:48.19 backup Database backed up: Database:
MyDatabase, creation
date(time): 2006/08/16(23:08:27), pages dumped: 32161, first LSN:
38101:76:1, last LSN:
38101:80:1, number of dump devices: 1, device information: (FILE=1,
TYPE=DISK:
{'MyDatabase_Backup'}).|||I've just realised that the main issue is that in one of backup
scripts that runs (and it is automated)...we have used:
isql command to run the back, and this would at times work, and also
not work.
by using the osql command instead, everything worked out fine.
Example:
Instead of having your statement:
isql -Usa -P -SSERVER
You have:
osql -Usa -P -SSERVER
That worked for me. The statement for the backup was in "isql" and I
converted it to "osql" and the rest remained untouched, and everything
started working again.

Wednesday, March 7, 2012

Problems with Dataset, Table Filters SSRS 2000 SP2

Hello all..
I've put this question out before, but I still haven't figured out a
solution..
When I apply this filter at the dataset or table level to get rid of
commission code 100 it blanks out the report
Expression: =Cstr(Fields!CommissionCode.Value)
Operator: = Value: '100'
I did discover that when I run this under the data tab to look at the raw
data, the filter works! But the report still comes up blank when I preview
it..
Help!!
Thanks.Its pretty apparent to me that due to the lack of response on this issue
that dataset and table filters aren't well supported on this version of
SSRS.. I will take another approach. I hope this post will save someone else
some time in the future.. Thanks
"jereviscious" <here@.there.com> wrote in message
news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
> Hello all..
> I've put this question out before, but I still haven't figured out a
> solution..
> When I apply this filter at the dataset or table level to get rid of
> commission code 100 it blanks out the report
> Expression: =Cstr(Fields!CommissionCode.Value)
> Operator: => Value: '100'
> I did discover that when I run this under the data tab to look at the raw
> data, the filter works! But the report still comes up blank when I preview
> it..
> Help!!
> Thanks.
>
>|||Wrong assumption.
People answer on a volunteer basis. You post might or might not be seen.
Take my case. I don't use filters because I think they are mostly a bad idea
to do. Filters are used after the data is brought over to the report. I use
query parameters. Query parameters do the same thing but it applies the
filter at the database, not at the report.
However, just because I don't use it does not means that filters don't work.
I have not seen any indications that they don't work. If you didn't get a
response you could try posting again. Or try the web forums. The web forums
have a lot more eyeballs.
If you have MSDN you might check out managed newsgroups. Managed newsgroups
are done by registering a fake email address with microsoft. That email
address gets monitored in the newsgroup and you are guaranteed a response
from a MS employee within two business days.
One last thing, have you tried query parameters? That really is the way to
go in most cases.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jereviscious" <here@.there.com> wrote in message
news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
> Its pretty apparent to me that due to the lack of response on this issue
> that dataset and table filters aren't well supported on this version of
> SSRS.. I will take another approach. I hope this post will save someone
> else some time in the future.. Thanks
> "jereviscious" <here@.there.com> wrote in message
> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the raw
>> data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>|||Bruce, thanks for your thoughtful response .
I'm not making any assumption here. I have anectdotal evidence, and in my
OPINION, which I have a right to, this filtering mechanism is NOT well
supported/implemented.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
> Wrong assumption.
> People answer on a volunteer basis. You post might or might not be seen.
> Take my case. I don't use filters because I think they are mostly a bad
> idea to do. Filters are used after the data is brought over to the report.
> I use query parameters. Query parameters do the same thing but it applies
> the filter at the database, not at the report.
> However, just because I don't use it does not means that filters don't
> work. I have not seen any indications that they don't work. If you didn't
> get a response you could try posting again. Or try the web forums. The web
> forums have a lot more eyeballs.
> If you have MSDN you might check out managed newsgroups. Managed
> newsgroups are done by registering a fake email address with microsoft.
> That email address gets monitored in the newsgroup and you are guaranteed
> a response from a MS employee within two business days.
> One last thing, have you tried query parameters? That really is the way to
> go in most cases.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this issue
>> that dataset and table filters aren't well supported on this version of
>> SSRS.. I will take another approach. I hope this post will save someone
>> else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>|||Yes you are right to your opinion, I'm not saying you aren't. However, if
you mean supported as in does the product support (work with) filters then I
have never seen anything with any posts where filters did not function. If
you mean supported because of response in this newsgroup, this newsgroup is
dying. Most of the action is in the web forums. Pretty much 0 MS people come
here, except for managed newsgroup postings. MS is putting all its focus on
the web forum. I prefer newsgroups but I am thinking of heading over to the
web forums.
So, if you want to use filters (which I suggest you do only as a last
resort) you should try both searching and posting at the web forums.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jereviscious" <here@.there.com> wrote in message
news:%23cIgSwHcHHA.4004@.TK2MSFTNGP06.phx.gbl...
> Bruce, thanks for your thoughtful response .
> I'm not making any assumption here. I have anectdotal evidence, and in my
> OPINION, which I have a right to, this filtering mechanism is NOT well
> supported/implemented.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea to do. Filters are used after the data is brought over to the
>> report. I use query parameters. Query parameters do the same thing but it
>> applies the filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work. I have not seen any indications that they don't work. If you didn't
>> get a response you could try posting again. Or try the web forums. The
>> web forums have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups are done by registering a fake email address with microsoft.
>> That email address gets monitored in the newsgroup and you are guaranteed
>> a response from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this issue
>> that dataset and table filters aren't well supported on this version of
>> SSRS.. I will take another approach. I hope this post will save someone
>> else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>>
>|||I'm wasn't criticizing the forum. It took me 6-7 hours to come up with the
correct syntax for this expression
=Cstr(Fields!CommissionCode.Value) = '100'
Simply refuses to work. I tried probably 30 different permutations
attempting to work with the string value. I finally tried this expression,
and it worked
=Cint(Fields!CommissionCode.Value) = =100
Which works fine unless you have a commission code = 032, which fortunately
for this report, doesn't affect anything, but it easily could have.
This should have taken 2 minutes. This was not a last resort problem, but it
WAS a much cleaner solution (far less code) than the alternative.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ONB%23kzHcHHA.4312@.TK2MSFTNGP05.phx.gbl...
> Yes you are right to your opinion, I'm not saying you aren't. However, if
> you mean supported as in does the product support (work with) filters then
> I have never seen anything with any posts where filters did not function.
> If you mean supported because of response in this newsgroup, this
> newsgroup is dying. Most of the action is in the web forums. Pretty much 0
> MS people come here, except for managed newsgroup postings. MS is putting
> all its focus on the web forum. I prefer newsgroups but I am thinking of
> heading over to the web forums.
> So, if you want to use filters (which I suggest you do only as a last
> resort) you should try both searching and posting at the web forums.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:%23cIgSwHcHHA.4004@.TK2MSFTNGP06.phx.gbl...
>> Bruce, thanks for your thoughtful response .
>> I'm not making any assumption here. I have anectdotal evidence, and in my
>> OPINION, which I have a right to, this filtering mechanism is NOT well
>> supported/implemented.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea to do. Filters are used after the data is brought over to the
>> report. I use query parameters. Query parameters do the same thing but
>> it applies the filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work. I have not seen any indications that they don't work. If you
>> didn't get a response you could try posting again. Or try the web
>> forums. The web forums have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups are done by registering a fake email address with microsoft.
>> That email address gets monitored in the newsgroup and you are
>> guaranteed a response from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this
>> issue that dataset and table filters aren't well supported on this
>> version of SSRS.. I will take another approach. I hope this post will
>> save someone else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>>
>>
>|||I have missed your earlier post. As far as your assumptions, I am with Bruce.
Infact its not like they are not supported, people have not come across, like
this, that's why no one replied or like me, have missed the post.
Anyways, so giving in query parameters is good, answering your post.
It s something to do with your data type and your single and double quote.
ie you are converting to string and giving single quote in the expression
window.
How to find out is sometime you need to give the wrong input to find out the
way to give the right input. Try diff. options give integer as input, give it
in double quotes or give a blank input. see what happens.
Let me know whether it works.
Amarnath, MCTS.
"Bruce L-C [MVP]" wrote:
> Wrong assumption.
> People answer on a volunteer basis. You post might or might not be seen.
> Take my case. I don't use filters because I think they are mostly a bad idea
> to do. Filters are used after the data is brought over to the report. I use
> query parameters. Query parameters do the same thing but it applies the
> filter at the database, not at the report.
> However, just because I don't use it does not means that filters don't work.
> I have not seen any indications that they don't work. If you didn't get a
> response you could try posting again. Or try the web forums. The web forums
> have a lot more eyeballs.
> If you have MSDN you might check out managed newsgroups. Managed newsgroups
> are done by registering a fake email address with microsoft. That email
> address gets monitored in the newsgroup and you are guaranteed a response
> from a MS employee within two business days.
> One last thing, have you tried query parameters? That really is the way to
> go in most cases.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
> > Its pretty apparent to me that due to the lack of response on this issue
> > that dataset and table filters aren't well supported on this version of
> > SSRS.. I will take another approach. I hope this post will save someone
> > else some time in the future.. Thanks
> > "jereviscious" <here@.there.com> wrote in message
> > news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
> >> Hello all..
> >>
> >> I've put this question out before, but I still haven't figured out a
> >> solution..
> >>
> >> When I apply this filter at the dataset or table level to get rid of
> >> commission code 100 it blanks out the report
> >>
> >> Expression: =Cstr(Fields!CommissionCode.Value)
> >> Operator: => >> Value: '100'
> >>
> >> I did discover that when I run this under the data tab to look at the raw
> >> data, the filter works! But the report still comes up blank when I
> >> preview it..
> >>
> >> Help!!
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >
> >
>
>|||I have answered this question ad infinitum. I have not made any assumptions
thank-you
"Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
news:7236F647-63FA-47A3-A90E-79D1A77A5C17@.microsoft.com...
>I have missed your earlier post. As far as your assumptions, I am with
>Bruce.
> Infact its not like they are not supported, people have not come across,
> like
> this, that's why no one replied or like me, have missed the post.
> Anyways, so giving in query parameters is good, answering your post.
> It s something to do with your data type and your single and double quote.
> ie you are converting to string and giving single quote in the expression
> window.
> How to find out is sometime you need to give the wrong input to find out
> the
> way to give the right input. Try diff. options give integer as input, give
> it
> in double quotes or give a blank input. see what happens.
> Let me know whether it works.
> Amarnath, MCTS.
>
> "Bruce L-C [MVP]" wrote:
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea
>> to do. Filters are used after the data is brought over to the report. I
>> use
>> query parameters. Query parameters do the same thing but it applies the
>> filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work.
>> I have not seen any indications that they don't work. If you didn't get a
>> response you could try posting again. Or try the web forums. The web
>> forums
>> have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups
>> are done by registering a fake email address with microsoft. That email
>> address gets monitored in the newsgroup and you are guaranteed a response
>> from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to
>> go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> > Its pretty apparent to me that due to the lack of response on this
>> > issue
>> > that dataset and table filters aren't well supported on this version of
>> > SSRS.. I will take another approach. I hope this post will save someone
>> > else some time in the future.. Thanks
>> > "jereviscious" <here@.there.com> wrote in message
>> > news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> >> Hello all..
>> >>
>> >> I've put this question out before, but I still haven't figured out a
>> >> solution..
>> >>
>> >> When I apply this filter at the dataset or table level to get rid of
>> >> commission code 100 it blanks out the report
>> >>
>> >> Expression: =Cstr(Fields!CommissionCode.Value)
>> >> Operator: =>> >> Value: '100'
>> >>
>> >> I did discover that when I run this under the data tab to look at the
>> >> raw
>> >> data, the filter works! But the report still comes up blank when I
>> >> preview it..
>> >>
>> >> Help!!
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>

Problems with creating SQL server accounts with SQL express edition

I installed Visual Web Developer on my laptop running on Windows XP Professional (SP2). With this SQL server express edition too got installed. Then I installed SQL server management studio express to manage the databases

I used "windows authentication" to login the SQL server for the first time. Then I found sa password is already there. I was never given the opportunity to set this sa password during the installation. I tired to change it to my own password but I found that it's not accepting any changes.

Then I tired to create a SQL server account and try to login. I was not allowed. Then through MSDN I got to know that Express Edition does not support mixed mode authentication by default but I have to select that during the installation. But the problem is I was never given the opportunity to select this authentication mode during the install ion.

I tired changing the registry values ( set LoginMode to '2") as instructed in the MSDN to allowe mixed mode. Even after that still I'm not allowed to create sql server accounts with my own passwords. I'm allowed to create accounts but it doesn't allow me to set the password; every time I check it had replace the password I set to some unknown password which I cannot see due to masking.

Can anyone offer me some advice to understand what's happening?

aththidiyavidana:
I'm allowed to create accounts but it doesn't allow me to set the password; every time I check it had replace the password I set to some unknown password which I cannot see due to masking.

Sounds Strange Surprise Make sure you've restarted the SQL Express instance after you modify the Authentication Mode.

Did you mean the password of new created account will be replaced by an unkown string?

How do you know (Did you get an error when try to login SQL Server with the account and password you just create, or you just find the length of the password seems to be changed)?

If yes, what's error message? Something like "Login failed for user 'test'. The user is not associated with a trusted SQL Server connection" or looks like "Login failed for user 'test'. (Microsoft SQL Server, Error: 18456"?

|||

Thanks for the reply.

I have found out the reason for not getting a chance to set 'sa' password during the installation; By default it avoids the advanced configuration options. We have to uncheck the option to get the extra dialog boxes to select authentication modes. I was able to reinstall SQL Serve express with this option uncheck and managed set my own sa password.

But I still don't know why I was not allowed to change the sa password set by the installation program during my first attempt. Each time I tired to reset this password it gave me the impression that changes are accepted because no error messages were thrown. But when I accessed the properties again after the changes I realized that 'sa' password I submit had not been accepted

I don't think this is an error or a bug. I think this is how it works…it won't let me access the server using SQL server accounts or set/reset my own SQL server account passwords if "mixed mode" is not selected during the installation

Thanks again for the reply

Problems With Client Connections

I will try to keep this as concise as possible. I am trying to set up a new
SQL Server 2005 Express server.
The OS is Windows XP Pro SP2. SQL Express is SP2.
I am able to connect to the instance locally through shared memory. I am
also able to connect to the instance locally with TCP by selecting browsing
and the network tab.
I have been able to connect through ODBC from one client desktop through MS
Access.
I am unable to establish a connection from any other client. They are all
on the same subnet. I have tried updating the driver to SQL Native Client
but still cannot connect. I receive the very long error message that
essentially states that it doesn't exist or I do not have permission to it.
I hope that this will be enough information for someone to make some
suggestions.
Thanks in advance for reading this post.
Bill
Perhaps these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"William Downey" <wdowney@.mclean.harvard.edu> wrote in message
news:%23emSqz9FHHA.4588@.TK2MSFTNGP05.phx.gbl...
>I will try to keep this as concise as possible. I am trying to set up a
>new SQL Server 2005 Express server.
> The OS is Windows XP Pro SP2. SQL Express is SP2.
> I am able to connect to the instance locally through shared memory. I am
> also able to connect to the instance locally with TCP by selecting
> browsing and the network tab.
> I have been able to connect through ODBC from one client desktop through
> MS Access.
> I am unable to establish a connection from any other client. They are all
> on the same subnet. I have tried updating the driver to SQL Native Client
> but still cannot connect. I receive the very long error message that
> essentially states that it doesn't exist or I do not have permission to
> it.
> I hope that this will be enough information for someone to make some
> suggestions.
> Thanks in advance for reading this post.
> Bill
>
|||Thanks for the article links.
Unfortunately, it seems I have tried nearly everything I can think of to get
clients to access the instance.
I did notice a previous thread that mentioned a similar issue.
The troubleshooting path I am headed down now is one of network-related
issues.
I wonder if anyone has had similar connectivity issues and had to tweak lan
settings?
Bill Downey
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%237eThA%23FHHA.4652@.TK2MSFTNGP04.phx.gbl...
> Perhaps these articles will help:
> Configuration -Configure SQL Server 2005 to allow remote connections
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
> Configuration -Connect to SQL Express from "downlevel clients"
> http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "William Downey" <wdowney@.mclean.harvard.edu> wrote in message
> news:%23emSqz9FHHA.4588@.TK2MSFTNGP05.phx.gbl...
>
|||You need to enable SQL Browser service (automatic), else the clients do
not know which dynamic TCP-port the should connect to. SQL Browser (UDP
1434) helps with this.
Default instance uses TCP 1433, which works without SQL Browser, but
all instances need SQL Browser.
In the SQL Area configuration guide, I think it should ask if you want
to start SQL Browser when you enable TCP-connections on an instance
other than default instance.
Best regards
Niklas Engfelt
William Downey skrev:
[vbcol=seagreen]
> Thanks for the article links.
> Unfortunately, it seems I have tried nearly everything I can think of to get
> clients to access the instance.
> I did notice a previous thread that mentioned a similar issue.
> The troubleshooting path I am headed down now is one of network-related
> issues.
> I wonder if anyone has had similar connectivity issues and had to tweak lan
> settings?
> Bill Downey
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%237eThA%23FHHA.4652@.TK2MSFTNGP04.phx.gbl...
|||I dont know if it is the same situation but I am having a problem with native
clients also... Essentiallly I CAN NOT INSTALLED SQL Express 2005 because I
keep getting an error almost at the end of the installation that read like
this: "[Microsoft][SQL Native Client]SSL Provider: The certificate's CN name
does not match the passed value" I have no idea what to do. I am practically
new to this. I just wanted to install SQL to follow up with the Visual Studio
C# lessons I am taking. I am stuck in chapter 8 because I need to install SQL
in order to follow up with the lessons and I can not do it... HELP!!!! Can
someone out there tell me what I need to do to install this package? (SQL
Express 2005). I would appreciate if beside posting something that person
would email me at waltersantiago@.msn.com. I just found this group while
looking for answers to my problem and I am afraid I may not get to see the
responses, if any, to my plight... Again... I just want to be able to install
the product. The above mentioned error stop me every time... I cleaned up and
uninstalled both automatically (with the program the SQL people provide) and
manually (by following their instructions) everything they asked to be
uninstalled before trying an installation. I still get the error... What is
CN? and where is lookling for the certificate? Do I need to delete or create
a especial certificate in order to install this product? If yes then how?
Anyway any help would be greatly appreciated. I would like to keep my journey
into becoming a Visual Studio C# programmer. THanks
"William Downey" wrote:

> I will try to keep this as concise as possible. I am trying to set up a new
> SQL Server 2005 Express server.
> The OS is Windows XP Pro SP2. SQL Express is SP2.
> I am able to connect to the instance locally through shared memory. I am
> also able to connect to the instance locally with TCP by selecting browsing
> and the network tab.
> I have been able to connect through ODBC from one client desktop through MS
> Access.
> I am unable to establish a connection from any other client. They are all
> on the same subnet. I have tried updating the driver to SQL Native Client
> but still cannot connect. I receive the very long error message that
> essentially states that it doesn't exist or I do not have permission to it.
> I hope that this will be enough information for someone to make some
> suggestions.
> Thanks in advance for reading this post.
> Bill
>
>
|||I've been having similar issues with regards to connectiong to SQL Server
Express Edition. I've installed it at several locatoins with little to no
problems. But, at a current client site things are not working as they have
at other client sites, which has really frustrated me.
I've made a post in SQL Server Access ADP regarding my problem, but have
decided to search a little more for a solution. My SQL Express has SQL
Browser Started. Initally, my Access application was not able to list my
databases for my server, but after Starting my SQL Browser my application now
lists the databases on my Server, but does not allow my client to connect to
the database. This same client application is installed on the server and
loads just fine, so I kinow my logon credentials are all correct.
Your comments regarding Port 1433. Is this a port that is commonly blocked
by firewalls? If so, could this be causeing a problem with me connecting? I
have little knowledge of TCP/IP and Ports, so I do not know where to work on
this items.
I understand SQL Server and Development against it but am finding connecting
to it to be very frustrating as I'm at the point I have no clue as to what
trouble-shooting to do. Most posts I've ready make it sound like it should be
simple, but I'm still missing something.
So, In my situation, my application can "see" the Server as it lists all of
my current databases, but when I attempt to log on using SQL Authentication
it fails. I'm using Mixes Mode (Win/SQL). And, the SQL Login works fine on my
Server. What has me puzzled is that my application sees all my databases but
will no accept logon credentials that work on my Server at my Client PC.
I'm very frustated. Any suggestions on how I can do further troubleshooting.
This just seems way more complicated that Microsoft claimed when I switched
from Access to SQL Server.
Thanks, Greg
"engfelt@.gmail.com" wrote:

> You need to enable SQL Browser service (automatic), else the clients do
> not know which dynamic TCP-port the should connect to. SQL Browser (UDP
> 1434) helps with this.
> Default instance uses TCP 1433, which works without SQL Browser, but
> all instances need SQL Browser.
> In the SQL Area configuration guide, I think it should ask if you want
> to start SQL Browser when you enable TCP-connections on an instance
> other than default instance.
> Best regards
> Niklas Engfelt
>
> William Downey skrev:
>
>

Wednesday, March 28, 2012

Problems with SQLh2 and reporting services 2000

Problems with SQLH2

Problems with SQLH2

Problems with SQLH2

Monday, March 26, 2012

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Problems with SQL 2000 and 2005 on same machine - Cant connect on 2000

Wednesday, March 21, 2012

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Problems with my Scheduled Backup Jobs on Windows Server 2003 SP2

Wednesday, March 7, 2012

Problems with Dataset, Table Filters SSRS 2000 SP2

Problems with creating SQL server accounts with SQL express edition

Problems With Client Connections

Problems using SQL

Blog Archive

About Me