Wednesday, March 28, 2012
Making sure that SQL Agent is running
and restart. In these cases, the SQL Agent does not auto
re-start, and overnight processing has not been completed.
Is there:
a) A way to make sure that the SQL Agent ALWAYS starts
when the SQL Service is started. I know I can do this if
the server is re-booted, but if you just stop and re-start
the SQL Service, the SQL Agent doesn't re-start.
b) From a stored procedure, or perhaps VB, inquire on the
running status of the SQL Agent (we have a monitor tool
that could be expended to report if the agent isn't
running) How does the SQL Enterprise Manager determin if
the SQL Agent is running ?
Thanks,
Joe.You can write a proc which uses xp_cmdshell and executed NET START and then park the proc as an auto
start proc (sp_procoption).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Joe Farr" <joefarr@.hotmail.com> wrote in message news:091801c36e0d$179a1530$a401280a@.phx.gbl...
> On several occasions, the SQL Service has been shut down
> and restart. In these cases, the SQL Agent does not auto
> re-start, and overnight processing has not been completed.
> Is there:
> a) A way to make sure that the SQL Agent ALWAYS starts
> when the SQL Service is started. I know I can do this if
> the server is re-booted, but if you just stop and re-start
> the SQL Service, the SQL Agent doesn't re-start.
> b) From a stored procedure, or perhaps VB, inquire on the
> running status of the SQL Agent (we have a monitor tool
> that could be expended to report if the agent isn't
> running) How does the SQL Enterprise Manager determin if
> the SQL Agent is running ?
> Thanks,
> Joe.
>|||That will do fine - thanks Tibor.
>--Original Message--
>You can write a proc which uses xp_cmdshell and executed
NET START and then park the proc as an auto
>start proc (sp_procoption).
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Joe Farr" <joefarr@.hotmail.com> wrote in message
news:091801c36e0d$179a1530$a401280a@.phx.gbl...
>> On several occasions, the SQL Service has been shut down
>> and restart. In these cases, the SQL Agent does not auto
>> re-start, and overnight processing has not been
completed.
>> Is there:
>> a) A way to make sure that the SQL Agent ALWAYS starts
>> when the SQL Service is started. I know I can do this if
>> the server is re-booted, but if you just stop and re-
start
>> the SQL Service, the SQL Agent doesn't re-start.
>> b) From a stored procedure, or perhaps VB, inquire on
the
>> running status of the SQL Agent (we have a monitor tool
>> that could be expended to report if the agent isn't
>> running) How does the SQL Enterprise Manager determin if
>> the SQL Agent is running ?
>> Thanks,
>> Joe.
>
>.
>|||For a robust production-grade setup, you may want to
configure your monitoring tool, which should be
independent of SQL Server, to restart the SQLAgent
service. Most enterprise-class monitoring tools such as
NetIQ and Patrol suppor such a configuration.
Linchi
>--Original Message--
>On several occasions, the SQL Service has been shut down
>and restart. In these cases, the SQL Agent does not auto
>re-start, and overnight processing has not been completed.
>Is there:
>a) A way to make sure that the SQL Agent ALWAYS starts
>when the SQL Service is started. I know I can do this if
>the server is re-booted, but if you just stop and re-
start
>the SQL Service, the SQL Agent doesn't re-start.
>b) From a stored procedure, or perhaps VB, inquire on the
>running status of the SQL Agent (we have a monitor tool
>that could be expended to report if the agent isn't
>running) How does the SQL Enterprise Manager determin if
>the SQL Agent is running ?
>Thanks,
>Joe.
>.
>
Monday, March 26, 2012
Making report add in work
Good day
I have been trying to install some type of reporting service . I have found a add in for web developer 2005 express . I drag the nessesay onto my form from the tool box and data table , but when I test the application all I get is xml , like below. Have I left something out. sorry I forgot to add that I also get this error on the default page-
<?xml version="1.0" encoding="utf-8"?>
-<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
-<DataSources>
-<DataSource Name="ConnectionString">
+<ConnectionProperties>
<ConnectString/>
<DataProvider>SQL</DataProvider>
</ConnectionProperties>
<rd:DataSourceID>baa3d63e-0dc9-43cf-9477-0040139b2ea1</rd:DataSourceID>
</DataSource>
</DataSources>
<BottomMargin>2.5cm</BottomMargin>
<RightMargin>2.5cm</RightMargin>
Hi;
Ok from the error message you are getting ie. "An error has occurred during report processing.
Friday, March 9, 2012
Major Problem!...Multiple user connection problem in reporting service 2000 with SOAP
Hi Everyone,
I am having a big problem here.
I am using Reporting Service 2000 and Visual Studio 2005. I have developed a custom web control which communicates with reporting web service and displays report. I pass username, password and domain information as network credential for communicating with report server (report server is remote). This is a web application in which users can see reports on the web page which uses my custom web control.
Everything works fine when there is single user. But when another user logs onto website and tries to access same or different report it seems like connection of the first user gets lost. And everything crashes for first user and for second user it works fine.
In fact if second user is accessing the same report then first user can see second user's report information which is no at all acceptable. I am sure that there should be some way so that multiple users can communicate with reporting server programmatically at the same time. Microsoft wouldn't make reporting web service so that only one user can access report at a time, would they?
Can anyone help me with this problem? Any help will be greatly appreciated.
Sounds like your users are being identified as the same person which would suggest annonymous access is being used or your web control is passing the same credentials for both users. I'm not sure how you've coded it or whether you are doing any caching or storing session state somewhere.
You have to narrow down what is at fault here. I would suggest the following:
Set your report server and report manager virtual directories to integrated or basic authentication and have 2 separate users access report manager at the same time|||
Thanks Adam for quick reply.
I don't have anonymous access enabled. I am using integrated windows authentication. Earlier i was trying to authenticate all users with one administartor credentials to communicate with Reporting web service. But then i changed my code so that it takes individual user's credentials. But this didn't make any difference.
I read in one reporting service book that Report server overwrites SessionID member after each call to the Render method. Therefore, two subsequent report requests will share same sessions only if they ask for the same report (assuming that the parameter set is same)
For example, let's say you run report A, then report B, and then report A again. When report B is rendered, its session identifier will overwrite the previous session identifier, which means that you will lose report A's session identifier. When report A is run again, even if the parameter set is the same, its execution will create a new report session and IsNewExecution will return true.
So i think this overwriting of SessionID by report server is causing the problem. But i don't know yet how to program so that it maintains proper SessionID for each user and hence doesn't crash for any user.
If anyone has any idea for solving this problem then please let me know. Thanks in advance.
|||Figured out. It was bug in my code. Accidentlly i had declared Parameter property as static in my code and because of that one user's report was using other user's property and which was making program crash. Thanks for reply though.Major Multiple connection problem RS2000 with SOAP
Hi Everyone,
I am having a big problem here.
I am using Reporting Service 2000 and Visual Studio 2005. I have developed a custom web control which communicates with reporting web service and displays report. I pass username, password and domain information as network credential for communicating with report server (report server is remote). This is a web application in which users can see reports on the web page which uses my custom web control.
Everything works fine when there is single user. But when another user logs onto website and tries to access same or different report it seems like connection of the first user gets lost. And everything crashes for first user and for second user it works fine.
In fact if second user is accessing the same report then first user can see second user's report information which is no at all acceptable. I am sure that should be some way so that multiple users can communicate with reporting server programmatically at the same time. Microsoft wouldn't make reporting web service so that only one user can access report at a time, would they?
Can anyone help me with this problem? ANyhelp will be greatly appreciated.
I don't have anonymous access enabled. I am using integrated windows authentication. Earlier i was trying to authenticate all users with one administartor credentials to communicate with Reporting web service. But then i changed my code so that it takes individual user's credentials. But this didn't make any difference.
I read in one reporting service book that Report server overwrites SessionID member after each call to the Render method. Therefore, two subsequent report requests will share same sessions only if they ask for the same report (assuming that the parameter set is same)
For example, let's say you run report A, then report B, and then report A again. When report B is rendered, its session identifier will overwrite the previous session identifier, which means that you will lose report A's session identifier. When report A is run again, even if the parameter set is the same, its execution will create a new report session and IsNewExecution will return true.
So i think this overwriting of SessionID by report server is causing the problem. But i don't know yet how to program so that it maintains proper SessionID for each user and hence doesn't crash for any user.
If anyone has any idea for solving this problem then please let me know. Thanks in advance.