Showing posts with label existing. Show all posts
Showing posts with label existing. Show all posts

Wednesday, March 28, 2012

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql

Sunday, February 19, 2012

Integrating SSRS with existing .NET 2.0 website issues

I am actively trying to prototype / evaluate SSRS as our reporting solution.
Makes sense, we're completely MS-based, with a SQL 2005 db server and an IIS
6 / Win2003 web server, and custom .NET 2.0 web application.
So, I'm struggling to figure out why it appears to be so difficult to
integrate SSRS. In our .NET web app, of course, we are using forms-based
authentication and SSL. We are also using the membership provider of 2.0
framework.
As so it happens, we are also using a few 3rd party custom classes which
are, of course, installed, in the BIN directory of our .NET web app.
So, now, I've installed SSRS on the same web server hosting our web app.
I've used the SSRS configuration manager admin tool to change the location
of the virtual directories from the default website to our custom web app.
The immediate problem I'm noticing is that I'm unable to get the Report
Manager web interface to work. When I attempt to navigate to our website
and the Reports virdir (http:\\www.[ourwebsitename].com\Reports), I get a
.NET error (listed below).
From what I can tell, the error is complaining it can't find / load one of
our custom 3rd party objects... which is installed in our website's BIN
directory. But, if I'm reading this right, it seems like the Reports
virtual dir has its own BIN directory, and seems to be picking up its own
application root.
This HAS to be a common scenario... how do I solve this?
Error Message:
<-->
Server Error in '/Reports' Application.
----
Could not load file or assembly 'Infragistics2.WebUI.Misc.v6.2,
Version=6.2.20062.1045, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or
one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: Could not load file or
assembly 'Infragistics2.WebUI.Misc.v6.2, Version=6.2.20062.1045,
Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its
dependencies. The system cannot find the file specified.
<-->Hello Noreen,
I would like to know whether you put the Report manager and Report Server
under your custom web application.
That means you have your customer application as the parent of the Report
manager.
Since Report manager and Report Server are also .NET web application, they
have their own BIN folder and web.config file. So, we do not suggest you to
put the report server under your customer web application.
My suggestion is:
1. Create a new web site in IIS and put your Reporting Services under that
web site.
2. Or you could put the custom application as a sub-site for the default
web site and put the reporting services directly under the default web site.
3. You could also condsider the Report Viewer control in your web
application so that you could refer the report in your web application.
Hope the information will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for the reply...
So, again, let me try to zero in on what is the best option here. We have a
custom web site, all ASP.NET 2.0; it is a protected website in that we
require users to login which is all handled using forms-based authentication
and the membership framework of .NET.
So, lets say our nifty .NET custom-developed website was
www.mycustomweb.com
It sounds like our best option is to create a custom web site, then, just
for SSRS, such as
"reports.mycustomweb.com"
But now that's a separate website (by definition!). I'm not aware of how to
make forms-based authentication work across both sites. Remember, the user
has been authenticated on www.mycustomweb.com... and only authenticated
users should get reports...
There must be a Microsoft use-case scenario for this... it has to be all too
common. Can you provide me w/ any references or links to documentation on
how to take care of this situation?
Thanks again,
-- Margo|||Hello Margo,
Thanks for the update.
Reporting Services supported Form Authentication but you need to do some
code work to enable it.
The Reporting Sevices need the Windows authentication so you must
impersonate a windows user in your code.
Here are some article maybe helpful:
Using Forms Authentication in Reporting Services
http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.as
p?frame=true#ufairs_topic3
Authentication in Reporting Services
http://msdn2.microsoft.com/de-de/library/ms152899.aspx
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Integrating Reports into existing ASP.NET site/app...

We have been creating reports using SSRS but would like our users to request
reports through a custom interface NOT the standard SSRS interface. So as
far as I know there are 3 ways of presenting SSRS reports to users:
1) Report Manager
2) Reports through URL
3) SSRS Web Services
1 and 2 are simple, but require that the user experience SSRS look and feel,
including all navigation whereas the Web Services can be used to allow the
user to interact with reports that will have the same look and feel as the
site for which they are being integrated.
Is this a fair assessment? What in your opinion is the best way to integrate
SSRS reports into a site so the user will get to pick report params via web
controls custom to the site but then view the report with the zooming,
paging and exporting
that you get free with Report Manager?
**Note I have looked at and got to run the
Microsoft.Samples.ReportingServices.ReportViewer, and maybe this is the best
way. But can this be used when presenting the user with an alternative way
of providing parameters?
Thanks all in advance.I am using ReportViewer component in my current asp.net web site. You can
find this component in x:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\Samples\Applications\ReportViewer. There is
c# and vb.net code available. You need to compile it first. And this link is
also helped me much at the begining;
http://www.odetocode.com/Articles/128.aspx (dont forget to read part two)
Hope this helps,
Regards.
"Terry Mulvany" <terry.mulvany@.rouseservices.com> wrote in message
news:#G#BlW72EHA.3380@.TK2MSFTNGP09.phx.gbl...
> We have been creating reports using SSRS but would like our users to
request
> reports through a custom interface NOT the standard SSRS interface. So as
> far as I know there are 3 ways of presenting SSRS reports to users:
> 1) Report Manager
> 2) Reports through URL
> 3) SSRS Web Services
> 1 and 2 are simple, but require that the user experience SSRS look and
feel,
> including all navigation whereas the Web Services can be used to allow the
> user to interact with reports that will have the same look and feel as the
> site for which they are being integrated.
> Is this a fair assessment? What in your opinion is the best way to
integrate
> SSRS reports into a site so the user will get to pick report params via
web
> controls custom to the site but then view the report with the zooming,
> paging and exporting
> that you get free with Report Manager?
> **Note I have looked at and got to run the
> Microsoft.Samples.ReportingServices.ReportViewer, and maybe this is the
best
> way. But can this be used when presenting the user with an alternative
way
> of providing parameters?
> Thanks all in advance.
>
>