Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Reporting Services / July 2008

Tip: Looking for answers? Try searching our database.

Snapshot doesn't work

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
nicknack - 22 Jul 2008 14:40 GMT
Hello.
I have a report that when I'm going to the reporting services to the
"History" tab I can press "new snapshot" and it works fine (The
snapshot was created).
When I try to go to "properties" and then to "history" to configure it
to schedule a snapshot every 5 minuts - nothing happen and the
snapshots does't appear.

I don't see any error on the server.
Is there a way to see way the snapshot can be created manually but not
with a schedule?

Thanks
Bruce L-C  [MVP] - 22 Jul 2008 14:53 GMT
Do you by any chance use User!UserID?

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

> Hello.
> I have a report that when I'm going to the reporting services to the
[quoted text clipped - 9 lines]
>
> Thanks
nicknack - 23 Jul 2008 07:11 GMT
Hi Bruce

I'm useing the User!UserID but it is used only in a fillter and not as
a parameter and I also used a default value for it!

Is this the problem?
I configure the reporting services "execution account" with my user id
if its help.

Thanks.

On 22 יולי, 15:53, "Bruce L-C  [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:
> Do you by any chance use User!UserID?
>
[quoted text clipped - 15 lines]
>
> > Thanks
Bruce L-C  [MVP] - 23 Jul 2008 15:19 GMT
I thought that using it as a filter would be OK. Not as a parameter (that
will not work).

I had someone in this newsgroup that used User!UserID as a filter for a
subscription. He at first used it as a parameter and the subscription failed
for him. When he switched to using it as a filter he was OK.

I am not sure of the rules as far as snapshots and User!UserID. Try
modifying your report to not user User!UserID and see if the problem goes
away. That would tell you if that is the issue.

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

Hi Bruce

I'm useing the User!UserID but it is used only in a fillter and not as
a parameter and I also used a default value for it!

Is this the problem?
I configure the reporting services "execution account" with my user id
if its help.

Thanks.

On 22 ????, 15:53, "Bruce L-C  [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:
> Do you by any chance use User!UserID?
>
[quoted text clipped - 19 lines]
>
> > Thanks
nicknack - 24 Jul 2008 06:08 GMT
Hi Bruce ,

I also think it because of USERID but I don't know way :(
When I run it manually it run ok and the snapshot is created.
When I schedule a snapshot - nothing happen.
Is there a way to see way nothing happen? is there a log where the RS
write way he didn't made the snapshot?

Because I used it only in a fillter and there too he has a deafult
value, I thought it was ok.

If I could find a log for the problem, It may hel pto understand where
is the problem.

Thanks.

On 23 יולי, 16:19, "Bruce L-C  [MVP]" <bruce_lcNOS...@hotmail.com>
wrote:
> I thought that using it as a filter would be OK. Not as a parameter (that
> will not work).
[quoted text clipped - 48 lines]
>
> > > Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.