PDF Report not reflecting changes after update

I've working on a report at a client and I'm having an issue with a report
not reflecting multiple updated. The basic procedure that is followed is:
1. The client adds an event to the timeline.
2. The client runs the timeline report and the new event shows up.
3. The client adds a new event to the timeline.
4. The second, and any subsequent events do not show up.
I've checked the stored procedure that the report calls and it returns the
correct data every time (reflects the events as added). I've also checked
the execution properties in the report to be sure that the report isn't set
to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
and I'm using Visual Studio 2003 SP1.
Any help would be really appreciated.It took me awhile to find the answer when I had the same problem.
Use;
rs:ClearSession=true in the url assuming you are using the url method.
directs the report server to remove a report from session. All report
instances associated with an authenticated user are removed from
session. (A report instance is defined as the same report run multiple
times with different report parameter values.)
Neil
John Swaringen wrote:
> I've working on a report at a client and I'm having an issue with a report
> not reflecting multiple updated. The basic procedure that is followed is:
> 1. The client adds an event to the timeline.
> 2. The client runs the timeline report and the new event shows up.
> 3. The client adds a new event to the timeline.
> 4. The second, and any subsequent events do not show up.
> I've checked the stored procedure that the report calls and it returns the
> correct data every time (reflects the events as added). I've also checked
> the execution properties in the report to be sure that the report isn't set
> to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
> and I'm using Visual Studio 2003 SP1.
> Any help would be really appreciated.|||Neil,
That worked great. It took me a while to figure out that I had to add it
via the ReportViewer.SetParameter() function. But once I did that everything
is cooking!
Thanks for the help!
"neilgould@.gmail.com" wrote:
> It took me awhile to find the answer when I had the same problem.
> Use;
> rs:ClearSession=true in the url assuming you are using the url method.
> directs the report server to remove a report from session. All report
> instances associated with an authenticated user are removed from
> session. (A report instance is defined as the same report run multiple
> times with different report parameter values.)
> Neil
>
> John Swaringen wrote:
> > I've working on a report at a client and I'm having an issue with a report
> > not reflecting multiple updated. The basic procedure that is followed is:
> >
> > 1. The client adds an event to the timeline.
> > 2. The client runs the timeline report and the new event shows up.
> > 3. The client adds a new event to the timeline.
> > 4. The second, and any subsequent events do not show up.
> >
> > I've checked the stored procedure that the report calls and it returns the
> > correct data every time (reflects the events as added). I've also checked
> > the execution properties in the report to be sure that the report isn't set
> > to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
> > and I'm using Visual Studio 2003 SP1.
> >
> > Any help would be really appreciated.
>

Pay Attention Please...

Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***
First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***
sql

Pay Attention Please...

Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***

Patching for W2k3 SP1 server w/SQL Server 2005

Is the correct procedure for SUS patches to a server running SQL Server 2005, to set the client to download only and then manually shutdown SQL Server, apply patches, reboot, and restart SQL Server?

Do SQL Server 2005 patches download through SUS or is it manual SP only, except for hotfixes?

Thanks, Tom

I don't have much experience with SUS, but the hotfix patches will take care of the services for you. SP2, which has publicly released quite yet, shows a list of processes in use to allow you to shut them down before patching. This will eliminate the reboot need.

Thanks,
Sam Lester (MSFT)

Password security

Have SQL 7.0 running on a Windows 2000 server. Users
access the database on a front end client that utilizes
SQL authentication. I see no password restriction
properties anywhere. I need to set some restrictions,
such as password expiration in 90 days, unique password
requirements, and minimum password lengths. Where do I
set up these restrictions? I can't find anything.Those options are not availble for SQL logins in SQL 7 or 2000. Odds are
we'll have it for the next major release.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

password expiry with HTTPS merge replication

Hi
We are using anonymous HTTPS merge replication.

The windows password used for the client subscriber expired on the publisher.

I reset it on the publisher - but SQL still seems to think that it is not expired - I get the following message in the event log of the publisher running SQL Server 2005

Login failed for user 'XYZ'. Reason: The password of the account has expired. [CLIENT: <local machine>]

Any ideas ?

thanks
Bruce

Two things to try:

1. Reset IIS and attempt to sync again

2. Since you are saying you use anon auth, I believe merge agent is not passing any credentials, just ensure that there is no other auth enabled on IIS.

Also I would suggest against anon authentication and instead use Basic authentication. And maybe you are using your domain\account in the anon auth instead of machine account? That would be more insecure. Strongly suggest you use basic authentication.

Password complexity in SQL

We have a SQL 2000 server and a client app that accesses it. We utilize SQL
authentication for the users who have already logged into the Windows domain
with a separate userid and password.
We are currently going through a certification and accredidation test and
one of the things we are getting dinged on is that we do not require complex
passwords with the SQL password. I see nowhere in SQL server to setup
mandatory password complexities, ie: minimum 8 characters, at least 1
number, 1 capital letter, etc.
Is there somewhere in SQL 2000 that a password policy for the SQL password
can be setup?Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
functionality yourself. In SQL Server 2005, SQL passwords will abide by the
Windows OS machine/domain password policy with Windows Server 2003 and
above. In either version, its preferred to use only Windows logins which
have had password complexity policies for some time. Do you really need to
support SQL logins?
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:8F93457A-538A-4FD5-8551-79A9404AB777@.microsoft.com...
> We have a SQL 2000 server and a client app that accesses it. We utilize
> SQL
> authentication for the users who have already logged into the Windows
> domain
> with a separate userid and password.
> We are currently going through a certification and accredidation test and
> one of the things we are getting dinged on is that we do not require
> complex
> passwords with the SQL password. I see nowhere in SQL server to setup
> mandatory password complexities, ie: minimum 8 characters, at least 1
> number, 1 capital letter, etc.
> Is there somewhere in SQL 2000 that a password policy for the SQL password
> can be setup?|||Well that's what I'm trying to tell these guys. We already meet the
password requirements as a user cannot even get access to the client app
without first logging into the domain with a required complex password. If
I
change all the users to Windows authentication, when they access the client
app, will it just automatically open or will they have to reenter their
Domain id and password?
"Bob Beauchemin" wrote:

> Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
> functionality yourself. In SQL Server 2005, SQL passwords will abide by th
e
> Windows OS machine/domain password policy with Windows Server 2003 and
> above. In either version, its preferred to use only Windows logins which
> have had password complexity policies for some time. Do you really need to
> support SQL logins?
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb|||If you use Windows authentication, their existing credentials are used, they
don't need to reenter. You'd need to change the connection strings in the
client apps to make this happen. There are some issues with delegation of
credentials (NTLM credentials are good for 1 inter-machine "hop", Kerberos
credentials can do multi-machine only if you have delegation enabled on a
server level) so you'd want to ensure that your application architecture can
accomdate this, especially if you have an intranet application. There's a
section in the SQL Server Books Online with details.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:3A6FD24F-14C1-4C15-B559-CD1489849867@.microsoft.com...
> Well that's what I'm trying to tell these guys. We already meet the
> password requirements as a user cannot even get access to the client app
> without first logging into the domain with a required complex password.
> If I
> change all the users to Windows authentication, when they access the
> client
> app, will it just automatically open or will they have to reenter their
> Domain id and password?
> "Bob Beauchemin" wrote:
>
>