Showing posts with label service. Show all posts
Showing posts with label service. Show all posts

Wednesday, March 28, 2012

Running a Report deployed on Reporting Server from C#

I have a report deployed on reporting serice. I am using reporting web service.

How can we call the report, assign parameters and execute it on a webpage

Are you using the full-blown version of Visual Studio 2005? If so, use a report viewer.

I'm not sure what a "reporting web service" is.

|||ReportExecution2005.asmx|||

Is that a link? If so it isn't clickable.

|||

http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsexecutionservice2005.aspx

I was refereing to the Reporting Services Web Service

Its ReportExecutionService

|||

Ok. Either I'm very mistaken or you are quite confused. That is the service which allows reports to render and generate.

I don't think there is any claim in this document that is made that would indicate that you can use this service directly to view reports from a webpage.

What I was getting at is you most likely want to create a .net web application and use the report viewer within Visual Studio 2005.

|||

Yeah i was gonna do that approach, get the bytes from webserivces render and using response to write to the page

Do u know how we can use the reportviwer to use the bytes returned from the webserivce

|||

Yes. In a nutshell, you do the following:

1. Create a C# .Net web application.

2. Drag and drop a report viewer to the application.

3. Set the report viewer properties properly to point to the report.

|||

Here's code I used from my application to generate a report, and get the byte stream. You'll note code in there that is used by HTML reports to point to the location of the images returned from the report service (all of which need to be saved to disk in my case). However, you can probably do all of this via stream directly to the output stream as well. Ignore my application-specific code:

Code Snippet

// load the report meta data and execution data

ReportExecutionService res = new ReportExecutionService();

res.Credentials = System.Net.CredentialCache.DefaultCredentials;

res.Url = application.ReportServer + "ReportExecution2005.asmx";

ReportingService2005 rs = new ReportingService2005();

rs.Credentials = System.Net.CredentialCache.DefaultCredentials;

ReportService2005.DataSourceCredentials[] credentials = null;

ReportService2005.ReportParameter[] availableParameters = rs.GetReportParameters(reportPath, null, false, null, credentials);

string outputID = IdGenerator.GetRandomStringId(20, null, null, true, true);

string outputFileName = outputID + "." + ext;

bool gecko = false;

if (request != null && request.UserAgent != null && request.UserAgent.ToLower().Contains("firefox"))

{

gecko = true;

}

string deviceInfo = "/" + site.RewriteUrl(application.VirtualPathRoot + "/Content/Resource.aspx?type=tmp") + "&filename=" + outputID + "_" + (gecko ? "Gecko" : "") + "";

deviceInfo = deviceInfo.Replace("&s=" + site.Key, "&s=" + site.Key);

string historyID = null;

string encoding = null;

string mimeType = null;

string extension = null;

ReportExecution2005.Warning[] warnings = null;

string[] streamIDs = null;

ExecutionInfo execInfo = new ExecutionInfo();

ExecutionHeader execHeader = new ExecutionHeader();

res.ExecutionHeaderValue = execHeader;

execInfo = res.LoadReport(reportPath, historyID);

string sessionId = res.ExecutionHeaderValue.ExecutionID;

// add all execution parameters

PrepareReportServerExecutionParameters(res, reportParameterCollection, format, parameters, availableParameters, application, site);

// execute the report to a file

byte[] result = res.Render(format, deviceInfo, out extension, out encoding, out mimeType, out warnings, out streamIDs);

FileStream stream = null;

try

{

stream = File.Create(application.TempFolder + outputFileName, result.Length);

stream.Write(result, 0, result.Length);

}

finally

{

if (stream != null)

{

stream.Close();

}

}

if (streamIDs != null && streamIDs.Length > 0)

{

for (int i = 0; i < streamIDs.Length; i++)

{

string encodingImage;

string mimeTypeImage;

System.IO.FileStream fs = null;

try

{

byte[] image = res.RenderStream("HTML4.0", streamIDs[i], null, out encodingImage, out mimeTypeImage);

fs = System.IO.File.OpenWrite(application.TempFolder + outputID + "_" + streamIDs[i]);

fs.Write(image, 0, Convert.ToInt32(image.Length));

}

catch (Exception e)

{

Log.Error(site, "Error rendering image stream for report (" + reportParameterCollection.ReportToken + "). " + e.Message + " " + e.StackTrace);

}

finally

{

if (fs != null)

{

fs.Close();

}

}

}

}

The "PrepareReportServerExecutionParameters()" method adds parameters to the report as follows:

Code Snippet

ReportExecution2005.ParameterValue parameter = new ReportExecution2005.ParameterValue();

parameter.Name = name;

parameter.Value = value;

reportServerParameterValues.Add(parameter);

The "reportServerParameterValues" collection is eventually funnelled into this call:

Code Snippet

res.SetExecutionParameters(reportParameters, "en-us");

I hope that all helps!

Michael

Running a Report deployed on Reporting Server from C#

I have a report deployed on reporting serice. I am using reporting web service.

How can we call the report, assign parameters and execute it on a webpage

Are you using the full-blown version of Visual Studio 2005? If so, use a report viewer.

I'm not sure what a "reporting web service" is.

|||ReportExecution2005.asmx|||

Is that a link? If so it isn't clickable.

|||

http://msdn2.microsoft.com/en-us/library/microsoft.wssux.reportingserviceswebservice.rsexecutionservice2005.aspx

I was refereing to the Reporting Services Web Service

Its ReportExecutionService

|||

Ok. Either I'm very mistaken or you are quite confused. That is the service which allows reports to render and generate.

I don't think there is any claim in this document that is made that would indicate that you can use this service directly to view reports from a webpage.

What I was getting at is you most likely want to create a .net web application and use the report viewer within Visual Studio 2005.

|||

Yeah i was gonna do that approach, get the bytes from webserivces render and using response to write to the page

Do u know how we can use the reportviwer to use the bytes returned from the webserivce

|||

Yes. In a nutshell, you do the following:

1. Create a C# .Net web application.

2. Drag and drop a report viewer to the application.

3. Set the report viewer properties properly to point to the report.

|||

Here's code I used from my application to generate a report, and get the byte stream. You'll note code in there that is used by HTML reports to point to the location of the images returned from the report service (all of which need to be saved to disk in my case). However, you can probably do all of this via stream directly to the output stream as well. Ignore my application-specific code:

Code Snippet

// load the report meta data and execution data

ReportExecutionService res = new ReportExecutionService();

res.Credentials = System.Net.CredentialCache.DefaultCredentials;

res.Url = application.ReportServer + "ReportExecution2005.asmx";

ReportingService2005 rs = new ReportingService2005();

rs.Credentials = System.Net.CredentialCache.DefaultCredentials;

ReportService2005.DataSourceCredentials[] credentials = null;

ReportService2005.ReportParameter[] availableParameters = rs.GetReportParameters(reportPath, null, false, null, credentials);

string outputID = IdGenerator.GetRandomStringId(20, null, null, true, true);

string outputFileName = outputID + "." + ext;

bool gecko = false;

if (request != null && request.UserAgent != null && request.UserAgent.ToLower().Contains("firefox"))

{

gecko = true;

}

string deviceInfo = "/" + site.RewriteUrl(application.VirtualPathRoot + "/Content/Resource.aspx?type=tmp") + "&filename=" + outputID + "_" + (gecko ? "Gecko" : "") + "";

deviceInfo = deviceInfo.Replace("&s=" + site.Key, "&amp;s=" + site.Key);

string historyID = null;

string encoding = null;

string mimeType = null;

string extension = null;

ReportExecution2005.Warning[] warnings = null;

string[] streamIDs = null;

ExecutionInfo execInfo = new ExecutionInfo();

ExecutionHeader execHeader = new ExecutionHeader();

res.ExecutionHeaderValue = execHeader;

execInfo = res.LoadReport(reportPath, historyID);

string sessionId = res.ExecutionHeaderValue.ExecutionID;

// add all execution parameters

PrepareReportServerExecutionParameters(res, reportParameterCollection, format, parameters, availableParameters, application, site);

// execute the report to a file

byte[] result = res.Render(format, deviceInfo, out extension, out encoding, out mimeType, out warnings, out streamIDs);

FileStream stream = null;

try

{

stream = File.Create(application.TempFolder + outputFileName, result.Length);

stream.Write(result, 0, result.Length);

}

finally

{

if (stream != null)

{

stream.Close();

}

}

if (streamIDs != null && streamIDs.Length > 0)

{

for (int i = 0; i < streamIDs.Length; i++)

{

string encodingImage;

string mimeTypeImage;

System.IO.FileStream fs = null;

try

{

byte[] image = res.RenderStream("HTML4.0", streamIDs[i], null, out encodingImage, out mimeTypeImage);

fs = System.IO.File.OpenWrite(application.TempFolder + outputID + "_" + streamIDs[i]);

fs.Write(image, 0, Convert.ToInt32(image.Length));

}

catch (Exception e)

{

Log.Error(site, "Error rendering image stream for report (" + reportParameterCollection.ReportToken + "). " + e.Message + " " + e.StackTrace);

}

finally

{

if (fs != null)

{

fs.Close();

}

}

}

}

The "PrepareReportServerExecutionParameters()" method adds parameters to the report as follows:

Code Snippet

ReportExecution2005.ParameterValue parameter = new ReportExecution2005.ParameterValue();

parameter.Name = name;

parameter.Value = value;

reportServerParameterValues.Add(parameter);

The "reportServerParameterValues" collection is eventually funnelled into this call:

Code Snippet

res.SetExecutionParameters(reportParameters, "en-us");

I hope that all helps!

Michael

Wednesday, March 21, 2012

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
Ellis
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>
|||Do you have a test environment where you could test the application as a SS 2K installation but running in 7.0 compatibility mode? I'd try it with a full blown upgrade but, if you run into problems, try again in the old 7.0 compatibility.
Sincerely,
Anthony Thomas

"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message news:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...

> Dear all,
>
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using

SQL7

> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using

SQL7

> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>

Run SQL Server 7.0 in Windows 2003

Dear all,
Lately, we bought a new server to replace existing old one. After
installation of SQL7, we followed to install the service pack 4 into it.
During the installation, we found SQL7 didn't support in 2003. And we
continued the process until it finished. Is there any problem on using SQL7
in windows server 2003? Since we have some application supported in SQL7
only, we have to keep using SQL7. Anyone know there's any impact using SQL7
in windows 2003? Please help
Best Rdgs
EllisIs there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So if
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> Lately, we bought a new server to replace existing old one. After
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
> Best Rdgs
> Ellis
>|||Do you have a test environment where you could test the application as a SS
2K installation but running in 7.0 compatibility mode? I'd try it with a fu
ll blown upgrade but, if you run into problems, try again in the old 7.0 com
patibility.
Sincerely,
Anthony Thomas
--
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message new
s:OeIJSk20EHA.1204@.TK2MSFTNGP10.phx.gbl...
Is there a technical reason your applications can't use SQL Server 2000?
SQL Server 7.0 will run, it just won't be a supported configuration. So i
f
you run into a problem with *ANY* software on that box, and try to call MS
product support, they'll tell you good luck and have a nice day...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eI0hUG20EHA.1296@.TK2MSFTNGP10.phx.gbl...
> Dear all,
>
> Lately, we bought a new server to replace existing old one. Afte
r
> installation of SQL7, we followed to install the service pack 4 into it.
> During the installation, we found SQL7 didn't support in 2003. And we
> continued the process until it finished. Is there any problem on using
SQL7
> in windows server 2003? Since we have some application supported in SQL7
> only, we have to keep using SQL7. Anyone know there's any impact using
SQL7
> in windows 2003? Please help
>
> Best Rdgs
> Ellis
>
>

Tuesday, March 20, 2012

run sp1 where??

i have 3 machines running report service components:
1 - a sql server
2 - a web server
3 - a development machine with vsnet2003
do i run sp1 on all 3?
please help
dushan bilbijaInstall it everywhere you installed Reporting Services.
I have IIS (and Reporting Services) installed on my SQL Server, so the only
location I had to install the SP was on the combination database/web server
and on my machine to update the client piece (that runs within VS.NET 2003).
--
Keith
"Dushan Bilbija" <dbilbija@.msn.com> wrote in message
news:e%23rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> i have 3 machines running report service components:
> 1 - a sql server
> 2 - a web server
> 3 - a development machine with vsnet2003
> do i run sp1 on all 3?
> please help
> dushan bilbija
>|||On 2 and 3.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dushan Bilbija" <dbilbija@.msn.com> wrote in message
news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> i have 3 machines running report service components:
> 1 - a sql server
> 2 - a web server
> 3 - a development machine with vsnet2003
> do i run sp1 on all 3?
> please help
> dushan bilbija
>|||Tudor, doesn't SP1 also update the server as well?
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> On 2 and 3.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > i have 3 machines running report service components:
> >
> > 1 - a sql server
> > 2 - a web server
> > 3 - a development machine with vsnet2003
> >
> > do i run sp1 on all 3?
> >
> > please help
> >
> > dushan bilbija
> >
> >
>|||I did a diff on my development SQL Server box that is running both the
reporting service and database and my production (pre SP1) ReportServer db
and there are large differences between the two. That makes me believe that
I will need to run the SP on the production database server as well as the
production Reporting Service, unless running it on the production Reporting
Service will pass the database updates automatically to its database server.
Worst thing that happens is I run the SP on the production Reporting
Service, do my diff, notice the changes haven't propogated as expected, run
the SP on the SQL Server db.
Thx, Joel
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Tudor, doesn't SP1 also update the server as well?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > On 2 and 3.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > i have 3 machines running report service components:
> > >
> > > 1 - a sql server
> > > 2 - a web server
> > > 3 - a development machine with vsnet2003
> > >
> > > do i run sp1 on all 3?
> > >
> > > please help
> > >
> > > dushan bilbija
> > >
> > >
> >
> >
>|||You don't need to run SP1 setup on the SQL Server box - if that's separate
from the report server box.
When you run SP1 setup on the RS box it will update stored procs and tables
on the SQL Server box.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Tudor, doesn't SP1 also update the server as well?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > On 2 and 3.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > i have 3 machines running report service components:
> > >
> > > 1 - a sql server
> > > 2 - a web server
> > > 3 - a development machine with vsnet2003
> > >
> > > do i run sp1 on all 3?
> > >
> > > please help
> > >
> > > dushan bilbija
> > >
> > >
> >
> >
>|||I don't think that there are any database related changes within Reporting
Services SP1.
--
Keith
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> Iâ've upgrade in a similar scenario (a 2 node NLB running Reporting
Services and a separate server running SQL Server). Reporting Services is
showing the appropriate version number (8.00.878.00) so all seems well on
the NLB.
> The only thing that makes me slightly nervous about the upgrade is the
fact that I didnâ't see any kind of â'upgrading database...â' dialog box, and I
have seen this dialog box where I have upgraded Reporting Services servers
that are running SQL Server and Reporting Services on the same server.
> Should I just forget about this nervousness and assume that the database
has successfully upgraded â' Is there any way to verify that the upgrade has
taken place on the SQL Server?
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > You don't need to run SP1 setup on the SQL Server box - if that's
separate
> > from the report server box.
> > When you run SP1 setup on the RS box it will update stored procs and
tables
> > on the SQL Server box.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > Tudor, doesn't SP1 also update the server as well?
> > >
> > > --
> > > ____________________________________
> > > William (Bill) Vaughn
> > > Author, Mentor, Consultant
> > > Microsoft MVP
> > > www.betav.com
> > > Please reply only to the newsgroup so that others can benefit.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > __________________________________
> > >
> > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > On 2 and 3.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > >
> > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > i have 3 machines running report service components:
> > > > >
> > > > > 1 - a sql server
> > > > > 2 - a web server
> > > > > 3 - a development machine with vsnet2003
> > > > >
> > > > > do i run sp1 on all 3?
> > > > >
> > > > > please help
> > > > >
> > > > > dushan bilbija
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >|||The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> I've upgrade in a similar scenario (a 2 node NLB running Reporting
Services and a separate server running SQL Server). Reporting Services is
showing the appropriate version number (8.00.878.00) so all seems well on
the NLB.
> The only thing that makes me slightly nervous about the upgrade is the
fact that I didn't see any kind of 'upgrading database...' dialog box, and I
have seen this dialog box where I have upgraded Reporting Services servers
that are running SQL Server and Reporting Services on the same server.
> Should I just forget about this nervousness and assume that the database
has successfully upgraded - Is there any way to verify that the upgrade has
taken place on the SQL Server?
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > You don't need to run SP1 setup on the SQL Server box - if that's
separate
> > from the report server box.
> > When you run SP1 setup on the RS box it will update stored procs and
tables
> > on the SQL Server box.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > Tudor, doesn't SP1 also update the server as well?
> > >
> > > --
> > > ____________________________________
> > > William (Bill) Vaughn
> > > Author, Mentor, Consultant
> > > Microsoft MVP
> > > www.betav.com
> > > Please reply only to the newsgroup so that others can benefit.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > __________________________________
> > >
> > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > On 2 and 3.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > >
> > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > i have 3 machines running report service components:
> > > > >
> > > > > 1 - a sql server
> > > > > 2 - a web server
> > > > > 3 - a development machine with vsnet2003
> > > > >
> > > > > do i run sp1 on all 3?
> > > > >
> > > > > please help
> > > > >
> > > > > dushan bilbija
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >|||There are definetly database changes. My diff showed 1 table change and 13
stored procedure changes. It's just as Tudor said though, the RS Service
takes care of the updates.
-Joel
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:Oweg%239eXEHA.1152@.TK2MSFTNGP09.phx.gbl...
> I don't think that there are any database related changes within Reporting
> Services SP1.
> --
> Keith
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> Services and a separate server running SQL Server). Reporting Services is
> showing the appropriate version number (8.00.878.00) so all seems well on
> the NLB.
> >
> > The only thing that makes me slightly nervous about the upgrade is the
> fact that I didn't see any kind of 'upgrading database...' dialog box, and
I
> have seen this dialog box where I have upgraded Reporting Services servers
> that are running SQL Server and Reporting Services on the same server.
> >
> > Should I just forget about this nervousness and assume that the database
> has successfully upgraded - Is there any way to verify that the upgrade
has
> taken place on the SQL Server?
> >
> > Thanks,
> > Mark
> >
> >
> > "Tudor Trufinescu (MSFT)" wrote:
> >
> > > You don't need to run SP1 setup on the SQL Server box - if that's
> separate
> > > from the report server box.
> > > When you run SP1 setup on the RS box it will update stored procs and
> tables
> > > on the SQL Server box.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > Tudor, doesn't SP1 also update the server as well?
> > > >
> > > > --
> > > > ____________________________________
> > > > William (Bill) Vaughn
> > > > Author, Mentor, Consultant
> > > > Microsoft MVP
> > > > www.betav.com
> > > > Please reply only to the newsgroup so that others can benefit.
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > __________________________________
> > > >
> > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > On 2 and 3.
> > > > >
> > > > > --
> > > > > Tudor Trufinescu
> > > > > Dev Lead
> > > > > Sql Server Reporting Services
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > >
> > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > i have 3 machines running report service components:
> > > > > >
> > > > > > 1 - a sql server
> > > > > > 2 - a web server
> > > > > > 3 - a development machine with vsnet2003
> > > > > >
> > > > > > do i run sp1 on all 3?
> > > > > >
> > > > > > please help
> > > > > >
> > > > > > dushan bilbija
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
>|||Thanks Tudor
Sounds like we are all agreed that the steps for running SP1 in a Web Farm outlined in the SP1 readme should be ignored?
â'The order in which you apply SP1 is important. You must first apply SP1 to the server that hosts the report server database (this updates the database format to the SP1 version). Once you update the database, you can update the report server nodes in any order.â'
Cleary if I have implemented my Web Farm following the recommendations in Reporting Services BOL , Step 1 (run SP1 on the database server) will never work.
Thanks,
Mark
"Tudor Trufinescu (MSFT)" wrote:
> The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> Services and a separate server running SQL Server). Reporting Services is
> showing the appropriate version number (8.00.878.00) so all seems well on
> the NLB.
> >
> > The only thing that makes me slightly nervous about the upgrade is the
> fact that I didn't see any kind of 'upgrading database...' dialog box, and I
> have seen this dialog box where I have upgraded Reporting Services servers
> that are running SQL Server and Reporting Services on the same server.
> >
> > Should I just forget about this nervousness and assume that the database
> has successfully upgraded - Is there any way to verify that the upgrade has
> taken place on the SQL Server?
> >
> > Thanks,
> > Mark
> >
> >
> > "Tudor Trufinescu (MSFT)" wrote:
> >
> > > You don't need to run SP1 setup on the SQL Server box - if that's
> separate
> > > from the report server box.
> > > When you run SP1 setup on the RS box it will update stored procs and
> tables
> > > on the SQL Server box.
> > >
> > > --
> > > Tudor Trufinescu
> > > Dev Lead
> > > Sql Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > Tudor, doesn't SP1 also update the server as well?
> > > >
> > > > --
> > > > ____________________________________
> > > > William (Bill) Vaughn
> > > > Author, Mentor, Consultant
> > > > Microsoft MVP
> > > > www.betav.com
> > > > Please reply only to the newsgroup so that others can benefit.
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > __________________________________
> > > >
> > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > On 2 and 3.
> > > > >
> > > > > --
> > > > > Tudor Trufinescu
> > > > > Dev Lead
> > > > > Sql Server Reporting Services
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > > rights.
> > > > >
> > > > >
> > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > i have 3 machines running report service components:
> > > > > >
> > > > > > 1 - a sql server
> > > > > > 2 - a web server
> > > > > > 3 - a development machine with vsnet2003
> > > > > >
> > > > > > do i run sp1 on all 3?
> > > > > >
> > > > > > please help
> > > > > >
> > > > > > dushan bilbija
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
>
>|||Yes, the wording is wrong here, I will pass this to our doc team.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:74CA554A-9BCD-46CF-B99C-AC8B8445CF55@.microsoft.com...
> Thanks Tudor
> Sounds like we are all agreed that the steps for running SP1 in a Web Farm
outlined in the SP1 readme should be ignored?
> "The order in which you apply SP1 is important. You must first apply SP1
to the server that hosts the report server database (this updates the
database format to the SP1 version). Once you update the database, you can
update the report server nodes in any order."
> Cleary if I have implemented my Web Farm following the recommendations in
Reporting Services BOL , Step 1 (run SP1 on the database server) will never
work.
> Thanks,
> Mark
>
> "Tudor Trufinescu (MSFT)" wrote:
> > The SP1 bits would only work on the SP1 schema, so your upgrade is OK.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> > news:9E97C141-6BFA-424F-A6C2-A5F6524FC824@.microsoft.com...
> > > I've upgrade in a similar scenario (a 2 node NLB running Reporting
> > Services and a separate server running SQL Server). Reporting Services
is
> > showing the appropriate version number (8.00.878.00) so all seems well
on
> > the NLB.
> > >
> > > The only thing that makes me slightly nervous about the upgrade is the
> > fact that I didn't see any kind of 'upgrading database...' dialog box,
and I
> > have seen this dialog box where I have upgraded Reporting Services
servers
> > that are running SQL Server and Reporting Services on the same server.
> > >
> > > Should I just forget about this nervousness and assume that the
database
> > has successfully upgraded - Is there any way to verify that the upgrade
has
> > taken place on the SQL Server?
> > >
> > > Thanks,
> > > Mark
> > >
> > >
> > > "Tudor Trufinescu (MSFT)" wrote:
> > >
> > > > You don't need to run SP1 setup on the SQL Server box - if that's
> > separate
> > > > from the report server box.
> > > > When you run SP1 setup on the RS box it will update stored procs and
> > tables
> > > > on the SQL Server box.
> > > >
> > > > --
> > > > Tudor Trufinescu
> > > > Dev Lead
> > > > Sql Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in
message
> > > > news:uKoXakWXEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > > > > Tudor, doesn't SP1 also update the server as well?
> > > > >
> > > > > --
> > > > > ____________________________________
> > > > > William (Bill) Vaughn
> > > > > Author, Mentor, Consultant
> > > > > Microsoft MVP
> > > > > www.betav.com
> > > > > Please reply only to the newsgroup so that others can benefit.
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > __________________________________
> > > > >
> > > > > "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> wrote in message
> > > > > news:uKCfRmTXEHA.384@.TK2MSFTNGP10.phx.gbl...
> > > > > > On 2 and 3.
> > > > > >
> > > > > > --
> > > > > > Tudor Trufinescu
> > > > > > Dev Lead
> > > > > > Sql Server Reporting Services
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > > rights.
> > > > > >
> > > > > >
> > > > > > "Dushan Bilbija" <dbilbija@.msn.com> wrote in message
> > > > > > news:e#rFxdTXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> > > > > > > i have 3 machines running report service components:
> > > > > > >
> > > > > > > 1 - a sql server
> > > > > > > 2 - a web server
> > > > > > > 3 - a development machine with vsnet2003
> > > > > > >
> > > > > > > do i run sp1 on all 3?
> > > > > > >
> > > > > > > please help
> > > > > > >
> > > > > > > dushan bilbija
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >

Monday, March 12, 2012

run IIS error?

When i go to My computer-Manage-IIS(restart).
I have folowing error message;
The service has not been started.
I did reinstall IIS.
What should i do to run IIS?
Thanks.On Jul 5, 5:40 pm, GGill <G...@.discussions.microsoft.com> wrote:
> When i go to My computer-Manage-IIS(restart).
> I have folowing error message;
> The service has not been started.
> I did reinstall IIS.
> What should i do to run IIS?
> Thanks.
This article is a bit old; but, it might be of use.
http://groups.google.com/group/microsoft.public.inetserver.misc/browse_thread/thread/34d8669353f6e8d1/d7598968da3a7112?lnk=st&q=service+has+not+been+started+IIS&rnum=11#d7598968da3a7112
Regards,
Enrique Martinez
Sr. Software Consultant