Mysterious DB Owner Changed

We are running a SQL 2000 server on Windows 2003 server. Somehow the db
owner changed on some of the databases. It's interesting that it changed to
the first login account listed on the server, not sure if that means anythin
g
or not. Has anyone seen the db owner mysteriously change and if so what
caused this?"Brenda" <Brenda@.discussions.microsoft.com> wrote in message
news:CAC1D3F3-225C-42AD-A992-0594561F997B@.microsoft.com...
> We are running a SQL 2000 server on Windows 2003 server. Somehow the db
> owner changed on some of the databases. It's interesting that it changed
> to
> the first login account listed on the server, not sure if that means
> anything
> or not. Has anyone seen the db owner mysteriously change and if so what
> caused this?
Did someone detach, then re-attach the databases in question using EM (as
opposed to manually executing sp_attach_db)? The attach UI allows you to
select the owner from sorted a combobox; which effectively makes the first
user the default owner. (sp_attach_db sets the owner to the current user.)
I'd think the old owner could be inferred from the orphaned dbo alias when
the db is attached, and that best-case behavior would be for previously
established ownership to be retained... but maybe not quite so simple.
In any case, sp_changedbowner is the easiest remedy.
-Mark|||Mark,
No the db's in question haven't been re-attached...I already changed the
owner, but I was just concerned that the owner changed mysteriously...Just
trying to see if anyone else has seen this happen...
Thanks!
"Mark J. McGinty" wrote:

> "Brenda" <Brenda@.discussions.microsoft.com> wrote in message
> news:CAC1D3F3-225C-42AD-A992-0594561F997B@.microsoft.com...
> Did someone detach, then re-attach the databases in question using EM (as
> opposed to manually executing sp_attach_db)? The attach UI allows you to
> select the owner from sorted a combobox; which effectively makes the first
> user the default owner. (sp_attach_db sets the owner to the current user.
)
> I'd think the old owner could be inferred from the orphaned dbo alias when
> the db is attached, and that best-case behavior would be for previously
> established ownership to be retained... but maybe not quite so simple.
> In any case, sp_changedbowner is the easiest remedy.
> -Mark
>
>|||I've never seen an unexplained database ownership change. Mark mentioned to
usual reasons. Another possibility is that a utility script was run that
changed the owners, such as one intended to correct invalid database owners
.
Hope this helps.
Dan Guzman
SQL Server MVP
"Brenda" <Brenda@.discussions.microsoft.com> wrote in message
news:CAC1D3F3-225C-42AD-A992-0594561F997B@.microsoft.com...
> We are running a SQL 2000 server on Windows 2003 server. Somehow the db
> owner changed on some of the databases. It's interesting that it changed
> to
> the first login account listed on the server, not sure if that means
> anything
> or not. Has anyone seen the db owner mysteriously change and if so what
> caused this?

My Report Manager Broke "The underlying connection was closed"

Our company recently re-located the servers and somehow in the process of
disconnecting -> reconnecting the Report Server the Report Manager now cannot
be run. All we get is the error:
"The underlying connection was closed: Unable to connect to the remote
server."
Interestingly, this affects ONLY the Report Manager, the Report Service is
running OK and all reports run fine via our web application and in Visual
Studio IDE etc...
Any clues?Hi!
We had a similar problem and resolved it by correcting the Applications
Extensions Mapping for the ReportServer virtual directory. Information about
configuring Reporting Services' virtual directories is available here:
http://support.microsoft.com/Default.aspx?kbid=867872
Good luck,
Bob
"neokortex" wrote:
> Our company recently re-located the servers and somehow in the process of
> disconnecting -> reconnecting the Report Server the Report Manager now cannot
> be run. All we get is the error:
> "The underlying connection was closed: Unable to connect to the remote
> server."
> Interestingly, this affects ONLY the Report Manager, the Report Service is
> running OK and all reports run fine via our web application and in Visual
> Studio IDE etc...
> Any clues?|||thanks for the tip,
but Im not quite sure this will help me. I checked the extensions for our
ReportServer virtual directory and they are already mapped exactly as
specified in the Support article. Also, ReportServer is working fine in so
far as reports can still be run through it.
It is only the Report Manager Web UI that is flaking out.
"bobhug" wrote:
> Hi!
> We had a similar problem and resolved it by correcting the Applications
> Extensions Mapping for the ReportServer virtual directory. Information about
> configuring Reporting Services' virtual directories is available here:
> http://support.microsoft.com/Default.aspx?kbid=867872
> Good luck,
> Bob
> "neokortex" wrote:
> > Our company recently re-located the servers and somehow in the process of
> > disconnecting -> reconnecting the Report Server the Report Manager now cannot
> > be run. All we get is the error:
> >
> > "The underlying connection was closed: Unable to connect to the remote
> > server."
> >
> > Interestingly, this affects ONLY the Report Manager, the Report Service is
> > running OK and all reports run fine via our web application and in Visual
> > Studio IDE etc...
> >
> > Any clues?|||I am having the exact same problem. ReportServer is working fine, but report
manager web interface gives The underlying connection was closed. was there a
resolution to this problem?
"neokortex" wrote:
> thanks for the tip,
> but Im not quite sure this will help me. I checked the extensions for our
> ReportServer virtual directory and they are already mapped exactly as
> specified in the Support article. Also, ReportServer is working fine in so
> far as reports can still be run through it.
> It is only the Report Manager Web UI that is flaking out.
> "bobhug" wrote:
> > Hi!
> > We had a similar problem and resolved it by correcting the Applications
> > Extensions Mapping for the ReportServer virtual directory. Information about
> > configuring Reporting Services' virtual directories is available here:
> > http://support.microsoft.com/Default.aspx?kbid=867872
> >
> > Good luck,
> > Bob
> >
> > "neokortex" wrote:
> >
> > > Our company recently re-located the servers and somehow in the process of
> > > disconnecting -> reconnecting the Report Server the Report Manager now cannot
> > > be run. All we get is the error:
> > >
> > > "The underlying connection was closed: Unable to connect to the remote
> > > server."
> > >
> > > Interestingly, this affects ONLY the Report Manager, the Report Service is
> > > running OK and all reports run fine via our web application and in Visual
> > > Studio IDE etc...
> > >
> > > Any clues?|||No resolution yet. Since that was a test server and we were/are in the
process of migrating to a production server, it is not a emergency for us. I
do know this is a general web service error, not necessarily specfic to RS.
However if you find the answer please respond. I am curious.
"Paul" wrote:
> I am having the exact same problem. ReportServer is working fine, but report
> manager web interface gives The underlying connection was closed. was there a
> resolution to this problem?
> "neokortex" wrote:
> > thanks for the tip,
> >
> > but Im not quite sure this will help me. I checked the extensions for our
> > ReportServer virtual directory and they are already mapped exactly as
> > specified in the Support article. Also, ReportServer is working fine in so
> > far as reports can still be run through it.
> >
> > It is only the Report Manager Web UI that is flaking out.
> >
> > "bobhug" wrote:
> >
> > > Hi!
> > > We had a similar problem and resolved it by correcting the Applications
> > > Extensions Mapping for the ReportServer virtual directory. Information about
> > > configuring Reporting Services' virtual directories is available here:
> > > http://support.microsoft.com/Default.aspx?kbid=867872
> > >
> > > Good luck,
> > > Bob
> > >
> > > "neokortex" wrote:
> > >
> > > > Our company recently re-located the servers and somehow in the process of
> > > > disconnecting -> reconnecting the Report Server the Report Manager now cannot
> > > > be run. All we get is the error:
> > > >
> > > > "The underlying connection was closed: Unable to connect to the remote
> > > > server."
> > > >
> > > > Interestingly, this affects ONLY the Report Manager, the Report Service is
> > > > running OK and all reports run fine via our web application and in Visual
> > > > Studio IDE etc...
> > > >
> > > > Any clues?|||Hi ,
I figured out the solution to this problem. Follwoing 3 things should be
made sure of:
1. Never reinstall reporting services without first uninstalling it
completely... i.e first remove the registry entiries manually then only
reporting services uninstallation is complete.
2. In the RSWebApplication.Config file in Reports Manager , the
ReportServerURL key should have a value as https:/IP(of the report manager
virtual directory)/ReportServer . If in other Report Server and Report
manager .Config files, you find localhost... replace it with the IP of the
virtual directory where reports manager and report server are installed.
3. When you deploy the report, in the configuration properties for the
project .. in the deployment path, again specify the IP instaed of
localhost...
If all these 3 things are taken care of.. then this error will not occur...
When i fixed all these, it worked for me.
pmud
"neokortex" wrote:
> No resolution yet. Since that was a test server and we were/are in the
> process of migrating to a production server, it is not a emergency for us. I
> do know this is a general web service error, not necessarily specfic to RS.
> However if you find the answer please respond. I am curious.
> "Paul" wrote:
> > I am having the exact same problem. ReportServer is working fine, but report
> > manager web interface gives The underlying connection was closed. was there a
> > resolution to this problem?
> >
> > "neokortex" wrote:
> >
> > > thanks for the tip,
> > >
> > > but Im not quite sure this will help me. I checked the extensions for our
> > > ReportServer virtual directory and they are already mapped exactly as
> > > specified in the Support article. Also, ReportServer is working fine in so
> > > far as reports can still be run through it.
> > >
> > > It is only the Report Manager Web UI that is flaking out.
> > >
> > > "bobhug" wrote:
> > >
> > > > Hi!
> > > > We had a similar problem and resolved it by correcting the Applications
> > > > Extensions Mapping for the ReportServer virtual directory. Information about
> > > > configuring Reporting Services' virtual directories is available here:
> > > > http://support.microsoft.com/Default.aspx?kbid=867872
> > > >
> > > > Good luck,
> > > > Bob
> > > >
> > > > "neokortex" wrote:
> > > >
> > > > > Our company recently re-located the servers and somehow in the process of
> > > > > disconnecting -> reconnecting the Report Server the Report Manager now cannot
> > > > > be run. All we get is the error:
> > > > >
> > > > > "The underlying connection was closed: Unable to connect to the remote
> > > > > server."
> > > > >
> > > > > Interestingly, this affects ONLY the Report Manager, the Report Service is
> > > > > running OK and all reports run fine via our web application and in Visual
> > > > > Studio IDE etc...
> > > > >
> > > > > Any clues?