Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!
>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

multi databases or partitions

Hi all

i have 3 million customer stored in a billing system.

currently i dived them to 40 database running sql2000.

i plan to migrate to sql 2005.

Is it better to let all customer in one partioned table based on city.?

or divide them one database for city.

taking into account there is 15 million transaction per month.

i want to get best performance and maintainance for backup.

thanks

Hi,

I would go for the partioned table. It is easier to remain within 1 database. I think there is more overhead in going to multiple databases anyway. With the partioned tables in 2005, you can span your data on multiple disks.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||

Hi Geert Verhoeven

Thank you for reply.

I use one storage Raid-5 for database storage composed of of 8 disk*73GB . In that case ,can that fullfill "span data on multiple disks".

Is there overhead for table partition compared to multi databases.

Just i want to know the side effect before starting merging data in one database using partitioned tables.

thanks

|||

Hi,

Indeed since you are using Raid, the spanning multiple disks is not an argument. Partioned tables can be processed by different processors but that is the same for multiple databases.

I still think that multiple databases give you more overhead then remaining in one database but it is hard to tell. Either way, I don't think that partitioned tables will be slower than multiple databases. Partitioned tables are easier to manage then multiple databases.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||

Since you have 40 different databases, I assume you want to be able to backup a portion (i.e. database in this case) and also that your data for one city does not interact with data in another city. With table partitioning, you can get the same convenience. you can partition by the city. You can possibly put each partition in its own file group there by mapped to diiferentg disk, you can backup/restore at filegroup granularity. Since partitioned table is managed as one logical unit, you won't need to worry about making schema changes in 40 databases, for example if you want to create an index.

multi databases or partitions

Hi all

i have 3 million customer stored in a billing system.

currently i dived them to 40 database running sql2000.

i plan to migrate to sql 2005.

Is it better to let all customer in one partioned table based on city.?

or divide them one database for city.

taking into account there is 15 million transaction per month.

i want to get best performance and maintainance for backup.

thanks

Hi,

I would go for the partioned table. It is easier to remain within 1 database. I think there is more overhead in going to multiple databases anyway. With the partioned tables in 2005, you can span your data on multiple disks.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||

Hi Geert Verhoeven

Thank you for reply.

I use one storage Raid-5 for database storage composed of of 8 disk*73GB . In that case ,can that fullfill "span data on multiple disks".

Is there overhead for table partition compared to multi databases.

Just i want to know the side effect before starting merging data in one database using partitioned tables.

thanks

|||

Hi,

Indeed since you are using Raid, the spanning multiple disks is not an argument. Partioned tables can be processed by different processors but that is the same for multiple databases.

I still think that multiple databases give you more overhead then remaining in one database but it is hard to tell. Either way, I don't think that partitioned tables will be slower than multiple databases. Partitioned tables are easier to manage then multiple databases.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||

Since you have 40 different databases, I assume you want to be able to backup a portion (i.e. database in this case) and also that your data for one city does not interact with data in another city. With table partitioning, you can get the same convenience. you can partition by the city. You can possibly put each partition in its own file group there by mapped to diiferentg disk, you can backup/restore at filegroup granularity. Since partitioned table is managed as one logical unit, you won't need to worry about making schema changes in 40 databases, for example if you want to create an index.

sql

msx-tsx restore...

hi
SQLServer 2000 sp3 having master-target relationship. I want to change the
master server to another system.how can i replace this master server without
affecting target relations? any help , appreciated.
BOL says:
Each target server reports to only one master server. You must defect a
target server from one master before you can enlist it into a different one.
"kpxus" <kpxus@.discussions.microsoft.com> wrote in message
news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
> hi
> SQLServer 2000 sp3 having master-target relationship. I want to change the
> master server to another system.how can i replace this master server
without
> affecting target relations? any help , appreciated.
|||Instead of defect the target and re enlist, is there any way to restore
the master and msdb on other system and continue the msx-tsx relationship?
Quentin Ran wrote:
> BOL says:
> Each target server reports to only one master server. You must defect a
> target server from one master before you can enlist it into a different one.
> "kpxus" <kpxus@.discussions.microsoft.com> wrote in message
> news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
>
> without
>
>

msx-tsx restore...

hi
SQLServer 2000 sp3 having master-target relationship. I want to change the
master server to another system.how can i replace this master server without
affecting target relations? any help , appreciated.BOL says:
Each target server reports to only one master server. You must defect a
target server from one master before you can enlist it into a different one.
"kpxus" <kpxus@.discussions.microsoft.com> wrote in message
news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
> hi
> SQLServer 2000 sp3 having master-target relationship. I want to change the
> master server to another system.how can i replace this master server
without
> affecting target relations? any help , appreciated.|||Instead of defect the target and re enlist, is there any way to restore
the master and msdb on other system and continue the msx-tsx relationship?
Quentin Ran wrote:
> BOL says:
> Each target server reports to only one master server. You must defect a
> target server from one master before you can enlist it into a different on
e.
> "kpxus" <kpxus@.discussions.microsoft.com> wrote in message
> news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
>
> without
>
>
>sql

msx-tsx restore...

hi
SQLServer 2000 sp3 having master-target relationship. I want to change the
master server to another system.how can i replace this master server without
affecting target relations? any help , appreciated.BOL says:
Each target server reports to only one master server. You must defect a
target server from one master before you can enlist it into a different one.
"kpxus" <kpxus@.discussions.microsoft.com> wrote in message
news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
> hi
> SQLServer 2000 sp3 having master-target relationship. I want to change the
> master server to another system.how can i replace this master server
without
> affecting target relations? any help , appreciated.|||Instead of defect the target and re enlist, is there any way to restore
the master and msdb on other system and continue the msx-tsx relationship?
Quentin Ran wrote:
> BOL says:
> Each target server reports to only one master server. You must defect a
> target server from one master before you can enlist it into a different one.
> "kpxus" <kpxus@.discussions.microsoft.com> wrote in message
> news:36E6CC5D-5EA3-474D-927E-0E7A29FFABE0@.microsoft.com...
>>hi
>>SQLServer 2000 sp3 having master-target relationship. I want to change the
>>master server to another system.how can i replace this master server
> without
>>affecting target relations? any help , appreciated.
>
>

MSSRS 2000 Restarts Windows XP system after the latest update

Hi Microsoft Sql server reproting services restarts the windows xp installed
desktops when we try to print using the print oprion in the report.
This is happening for lot of my clients.
How to fix this. This is happening only after the latest update in March.
My company has aroung 40,000 people who will be using the reports generated
by the reporting services most of them have windows xp with autometic update
switched on. Hence once the update happnes when they want to take a print out
of a report which shown using the MSSRS 2000 in internet explorere and
clicked onthe print icon in the report window system gets restarted.
Please help
Thanking you
SureshSuresh,
The first time you click the print icon a ActiveX control is installed. You
must have some sort of common desktop configuration that is blowing up when
you try to install this ActiveX.
First thing I would do is look at IE's security settings surrounding the
ActiveX downloading/installing.
--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@.(NOSPAM)lakeclaireenterprises.com
"Suresh" <Suresh@.discussions.microsoft.com> wrote in message
news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> Hi Microsoft Sql server reproting services restarts the windows xp
> installed
> desktops when we try to print using the print oprion in the report.
> This is happening for lot of my clients.
> How to fix this. This is happening only after the latest update in March.
> My company has aroung 40,000 people who will be using the reports
> generated
> by the reporting services most of them have windows xp with autometic
> update
> switched on. Hence once the update happnes when they want to take a print
> out
> of a report which shown using the MSSRS 2000 in internet explorere and
> clicked onthe print icon in the report window system gets restarted.
> Please help
> Thanking you
> Suresh
>|||Thanks Andy.
But the issue is not with installing the active x.
In many systems the active x was installed long before.
It was working fine until recently a windws xp update was released.
After the update only when clicked on the print icon in the report displayed
in desktops the systems get restarted.
So this should be a bug introduced due to the recent update by Microsft
update for windows Xp. I am looking for a patch for this.
Regards
Suresh
"Andy Potter" wrote:
> Suresh,
> The first time you click the print icon a ActiveX control is installed. You
> must have some sort of common desktop configuration that is blowing up when
> you try to install this ActiveX.
> First thing I would do is look at IE's security settings surrounding the
> ActiveX downloading/installing.
> --
> Andy Potter
> blog : http://sqlreportingservices.spaces.live.com
> info@.(NOSPAM)lakeclaireenterprises.com
> "Suresh" <Suresh@.discussions.microsoft.com> wrote in message
> news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > Hi Microsoft Sql server reproting services restarts the windows xp
> > installed
> > desktops when we try to print using the print oprion in the report.
> >
> > This is happening for lot of my clients.
> > How to fix this. This is happening only after the latest update in March.
> >
> > My company has aroung 40,000 people who will be using the reports
> > generated
> > by the reporting services most of them have windows xp with autometic
> > update
> > switched on. Hence once the update happnes when they want to take a print
> > out
> > of a report which shown using the MSSRS 2000 in internet explorere and
> > clicked onthe print icon in the report window system gets restarted.
> >
> > Please help
> > Thanking you
> > Suresh
> >
> >
>
>|||Suresh,
We are facing the same problem..
I was searching around when i got something on this issue in the below
URL.
Not sure to what extent it will identify and solve this problem, but
may be worth a read.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
Please let us know if any body gets some solution to this
On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> Thanks Andy.
> But the issue is not with installing the active x.
> In many systems the active x was installed long before.
> It was working fine until recently a windws xp update was released.
> After the update only when clicked on theprinticon in the report displayed
> in desktops the systems get restarted.
> So this should be a bug introduced due to the recent update by Microsft
> update for windows Xp. I am looking for a patch for this.
> Regards
> Suresh
>
> "Andy Potter" wrote:
> > Suresh,
> > The first time you click theprinticon a ActiveX control is installed. You
> > must have some sort of common desktop configuration that is blowing up when
> > you try to install this ActiveX.
> > First thing I would do is look at IE's security settings surrounding the
> > ActiveX downloading/installing.
> > --
> > Andy Potter
> > blog :http://sqlreportingservices.spaces.live.com
> > info@.(NOSPAM)lakeclaireenterprises.com
> > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > installed
> > > desktops when we try toprintusing theprintoprion in the report.
> > > This is happening for lot of my clients.
> > > How to fix this. This is happening only after the latest update in March.
> > > My company has aroung 40,000 people who will be using the reports
> > > generated
> > > by thereporting servicesmost of them have windows xp with autometic
> > > update
> > > switched on. Hence once the update happnes when they want to take aprint
> > > out
> > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > clicked ontheprinticon in the report windowsystemgets restarted.
> > > Please help
> > > Thanking you
> > > Suresh- Hide quoted text -
> - Show quoted text -|||Hi Shocky,
It is really great. the link you have given actually solved my problem.
Thanks a lot for the help. This was the need of the hour for me.
Once again
Thanking you
Suresh
"Shocky" wrote:
> Suresh,
> We are facing the same problem..
> I was searching around when i got something on this issue in the below
> URL.
> Not sure to what extent it will identify and solve this problem, but
> may be worth a read.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
>
> Please let us know if any body gets some solution to this
>
> On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> > Thanks Andy.
> >
> > But the issue is not with installing the active x.
> >
> > In many systems the active x was installed long before.
> > It was working fine until recently a windws xp update was released.
> > After the update only when clicked on theprinticon in the report displayed
> > in desktops the systems get restarted.
> >
> > So this should be a bug introduced due to the recent update by Microsft
> > update for windows Xp. I am looking for a patch for this.
> >
> > Regards
> > Suresh
> >
> >
> >
> > "Andy Potter" wrote:
> > > Suresh,
> >
> > > The first time you click theprinticon a ActiveX control is installed. You
> > > must have some sort of common desktop configuration that is blowing up when
> > > you try to install this ActiveX.
> >
> > > First thing I would do is look at IE's security settings surrounding the
> > > ActiveX downloading/installing.
> >
> > > --
> > > Andy Potter
> > > blog :http://sqlreportingservices.spaces.live.com
> > > info@.(NOSPAM)lakeclaireenterprises.com
> > > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> > >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > > installed
> > > > desktops when we try toprintusing theprintoprion in the report.
> >
> > > > This is happening for lot of my clients.
> > > > How to fix this. This is happening only after the latest update in March.
> >
> > > > My company has aroung 40,000 people who will be using the reports
> > > > generated
> > > > by thereporting servicesmost of them have windows xp with autometic
> > > > update
> > > > switched on. Hence once the update happnes when they want to take aprint
> > > > out
> > > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > > clicked ontheprinticon in the report windowsystemgets restarted.
> >
> > > > Please help
> > > > Thanking you
> > > > Suresh- Hide quoted text -
> >
> > - Show quoted text -
>
>sql

MSSQLServerOLAPService crashing frequently

System: Sql-server 2005 (x64) SP1 , Windows 2003 Server (x64)

SSAS seems to crash now and then and application log fills with :

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

and...

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

etc.

System log at just before: (event id 7034)

The SQL Server Analysis Services (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).

Please contact Customer Support to report your problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

The following messages have been happening on our system (Windows 2000 SP 4) while it was at SQL Server SP3 and AS SP2.

-Unexpected fatal error occurred. Attempting to restart server.

-mssqlserverolapservice service terminated unexpectedly. it has done this X times

We upgraded to SP4 on both SQL Server 2000 and AS. Same issue is still happening after the upgrade which was one of the recommendations.

What are we missing at this point?

|||

Let me make a wild guess here: You might have case of data corruption.

If you have kept your backups and you know how to restore your Analysis Services cubes here is what you can do:
Cleanup your data folder. For AS2000 that should be something like "C:\Program Files\Microsoft Analysis Services\Data". Delete everything from that folder.
You will loose all of you Analysis Services data, and you should only do that if you sure you can recover later.

If you are not sure you can get all of your data from backups, you should contact customer support and CSS guys will help you to recover from data corruption without loosing data.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Bizarre - we're getting this same behavior.

It's crashed every morning for the last week at about the same time....3-4AM. We're also on a x64 box, wonder if that has anything to do with it.

Ever figure out what the deal was?

|||

The solution I implemented was to upgrade to the latest SP on AS (I believe it we upgraded to SQL 2000 SP4, and AS SP 4 as well) - (AS Version 8.0.2039). Once we had the latest SPs in place, we proceeded to backup the entire <MSSQL\Microsoft Analysis Services\Data folder containing all the AS databases onto a different location as a fall back position. At this point, (with an empty /data folder) we proceeded to start the AS related services (MSSQLServerOLAPService) and they were steady. I then proceeded to iteratively re-introduce the AS Databases one folder at a time from the previously backed up location (<backuplocation>\MSSQL\Microsoft Analysis Services\Data\<AS databases> until the folder that caused the services to start crashing was identified. Once this folder was identified, I deleted it from the /data folder and process the appropriate dimensions/cubes to regenerate the AS databases. Make sure that your .odb file is backed up safely as an added precaution.

MSSQLServerOLAPService crashing frequently

System: Sql-server 2005 (x64) SP1 , Windows 2003 Server (x64)

SSAS seems to crash now and then and application log fills with :

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

and...

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

etc.

System log at just before: (event id 7034)

The SQL Server Analysis Services (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).

Please contact Customer Support to report your problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

The following messages have been happening on our system (Windows 2000 SP 4) while it was at SQL Server SP3 and AS SP2.

-Unexpected fatal error occurred. Attempting to restart server.

-mssqlserverolapservice service terminated unexpectedly. it has done this X times

We upgraded to SP4 on both SQL Server 2000 and AS. Same issue is still happening after the upgrade which was one of the recommendations.

What are we missing at this point?

|||

Let me make a wild guess here: You might have case of data corruption.

If you have kept your backups and you know how to restore your Analysis Services cubes here is what you can do:
Cleanup your data folder. For AS2000 that should be something like "C:\Program Files\Microsoft Analysis Services\Data". Delete everything from that folder.
You will loose all of you Analysis Services data, and you should only do that if you sure you can recover later.

If you are not sure you can get all of your data from backups, you should contact customer support and CSS guys will help you to recover from data corruption without loosing data.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Bizarre - we're getting this same behavior.

It's crashed every morning for the last week at about the same time....3-4AM. We're also on a x64 box, wonder if that has anything to do with it.

Ever figure out what the deal was?

|||

The solution I implemented was to upgrade to the latest SP on AS (I believe it we upgraded to SQL 2000 SP4, and AS SP 4 as well) - (AS Version 8.0.2039). Once we had the latest SPs in place, we proceeded to backup the entire <MSSQL\Microsoft Analysis Services\Data folder containing all the AS databases onto a different location as a fall back position. At this point, (with an empty /data folder) we proceeded to start the AS related services (MSSQLServerOLAPService) and they were steady. I then proceeded to iteratively re-introduce the AS Databases one folder at a time from the previously backed up location (<backuplocation>\MSSQL\Microsoft Analysis Services\Data\<AS databases> until the folder that caused the services to start crashing was identified. Once this folder was identified, I deleted it from the /data folder and process the appropriate dimensions/cubes to regenerate the AS databases. Make sure that your .odb file is backed up safely as an added precaution.

sql

MSSQLServerOLAPService crashing frequently

System: Sql-server 2005 (x64) SP1 , Windows 2003 Server (x64)

SSAS seems to crash now and then and application log fills with :

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

and...

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

etc.

System log at just before: (event id 7034)

The SQL Server Analysis Services (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).

Please contact Customer Support to report your problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

The following messages have been happening on our system (Windows 2000 SP 4) while it was at SQL Server SP3 and AS SP2.

-Unexpected fatal error occurred. Attempting to restart server.

-mssqlserverolapservice service terminated unexpectedly. it has done this X times

We upgraded to SP4 on both SQL Server 2000 and AS. Same issue is still happening after the upgrade which was one of the recommendations.

What are we missing at this point?

|||

Let me make a wild guess here: You might have case of data corruption.

If you have kept your backups and you know how to restore your Analysis Services cubes here is what you can do:
Cleanup your data folder. For AS2000 that should be something like "C:\Program Files\Microsoft Analysis Services\Data". Delete everything from that folder.
You will loose all of you Analysis Services data, and you should only do that if you sure you can recover later.

If you are not sure you can get all of your data from backups, you should contact customer support and CSS guys will help you to recover from data corruption without loosing data.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Bizarre - we're getting this same behavior.

It's crashed every morning for the last week at about the same time....3-4AM. We're also on a x64 box, wonder if that has anything to do with it.

Ever figure out what the deal was?

|||

The solution I implemented was to upgrade to the latest SP on AS (I believe it we upgraded to SQL 2000 SP4, and AS SP 4 as well) - (AS Version 8.0.2039). Once we had the latest SPs in place, we proceeded to backup the entire <MSSQL\Microsoft Analysis Services\Data folder containing all the AS databases onto a different location as a fall back position. At this point, (with an empty /data folder) we proceeded to start the AS related services (MSSQLServerOLAPService) and they were steady. I then proceeded to iteratively re-introduce the AS Databases one folder at a time from the previously backed up location (<backuplocation>\MSSQL\Microsoft Analysis Services\Data\<AS databases> until the folder that caused the services to start crashing was identified. Once this folder was identified, I deleted it from the /data folder and process the appropriate dimensions/cubes to regenerate the AS databases. Make sure that your .odb file is backed up safely as an added precaution.

|||

Hi,

I have this exact same problem error but it happens only when the cubes are being processed. In the middle of the dimension and cube processing AS crashes, returns that unexpected fatal error message to the event log, and then restarts. I've scheduled a Job that process the cubes after we load new data to our data mart, so SQL Server Agent is process that runs the job on the cubes. This happens erratically some days, some not.

If the process fails I go to Analysis Manager and reprocess the cubes without problem. I've seen this even happen in Analysis Manager, A first attempt to process fails and crashes the server, and then a second one works. Pretty strange. I have SP4 for both SQL and AS.

If anyone know how to deal with this I'd appreciate your advise.

Thanks,

Ricardo Sada

|||

we eventually opened up a case with MS, and found a resolution.

i wrote about it here: http://jesseorosz.spaces.live.com/blog/cns!E322FD91218E57CF!295.entry

basically it's a problem with the OLAP heap, we switched to use windows low frag and it's worked OK since

|||

Thanks Jesee

I read your post and I see that you are using SQL 2005, in our case we are still working with AS 2000.

May be the cause is similar and some out of Memory problem is the issue.

MSSQLServerOLAPService crashing frequently

System: Sql-server 2005 (x64) SP1 , Windows 2003 Server (x64)

SSAS seems to crash now and then and application log fills with :

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

and...

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

etc.

System log at just before: (event id 7034)

The SQL Server Analysis Services (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).

Please contact Customer Support to report your problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

The following messages have been happening on our system (Windows 2000 SP 4) while it was at SQL Server SP3 and AS SP2.

-Unexpected fatal error occurred. Attempting to restart server.

-mssqlserverolapservice service terminated unexpectedly. it has done this X times

We upgraded to SP4 on both SQL Server 2000 and AS. Same issue is still happening after the upgrade which was one of the recommendations.

What are we missing at this point?

|||

Let me make a wild guess here: You might have case of data corruption.

If you have kept your backups and you know how to restore your Analysis Services cubes here is what you can do:
Cleanup your data folder. For AS2000 that should be something like "C:\Program Files\Microsoft Analysis Services\Data". Delete everything from that folder.
You will loose all of you Analysis Services data, and you should only do that if you sure you can recover later.

If you are not sure you can get all of your data from backups, you should contact customer support and CSS guys will help you to recover from data corruption without loosing data.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Bizarre - we're getting this same behavior.

It's crashed every morning for the last week at about the same time....3-4AM. We're also on a x64 box, wonder if that has anything to do with it.

Ever figure out what the deal was?

|||

The solution I implemented was to upgrade to the latest SP on AS (I believe it we upgraded to SQL 2000 SP4, and AS SP 4 as well) - (AS Version 8.0.2039). Once we had the latest SPs in place, we proceeded to backup the entire <MSSQL\Microsoft Analysis Services\Data folder containing all the AS databases onto a different location as a fall back position. At this point, (with an empty /data folder) we proceeded to start the AS related services (MSSQLServerOLAPService) and they were steady. I then proceeded to iteratively re-introduce the AS Databases one folder at a time from the previously backed up location (<backuplocation>\MSSQL\Microsoft Analysis Services\Data\<AS databases> until the folder that caused the services to start crashing was identified. Once this folder was identified, I deleted it from the /data folder and process the appropriate dimensions/cubes to regenerate the AS databases. Make sure that your .odb file is backed up safely as an added precaution.

MSSQLServerOLAPService crashing frequently

System: Sql-server 2005 (x64) SP1 , Windows 2003 Server (x64)

SSAS seems to crash now and then and application log fills with :

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

and...

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

etc.

System log at just before: (event id 7034)

The SQL Server Analysis Services (MSSQLSERVER) service terminated unexpectedly. It has done this 2 time(s).

Please contact Customer Support to report your problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

The following messages have been happening on our system (Windows 2000 SP 4) while it was at SQL Server SP3 and AS SP2.

-Unexpected fatal error occurred. Attempting to restart server.

-mssqlserverolapservice service terminated unexpectedly. it has done this X times

We upgraded to SP4 on both SQL Server 2000 and AS. Same issue is still happening after the upgrade which was one of the recommendations.

What are we missing at this point?

|||

Let me make a wild guess here: You might have case of data corruption.

If you have kept your backups and you know how to restore your Analysis Services cubes here is what you can do:
Cleanup your data folder. For AS2000 that should be something like "C:\Program Files\Microsoft Analysis Services\Data". Delete everything from that folder.
You will loose all of you Analysis Services data, and you should only do that if you sure you can recover later.

If you are not sure you can get all of your data from backups, you should contact customer support and CSS guys will help you to recover from data corruption without loosing data.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Bizarre - we're getting this same behavior.

It's crashed every morning for the last week at about the same time....3-4AM. We're also on a x64 box, wonder if that has anything to do with it.

Ever figure out what the deal was?

|||

The solution I implemented was to upgrade to the latest SP on AS (I believe it we upgraded to SQL 2000 SP4, and AS SP 4 as well) - (AS Version 8.0.2039). Once we had the latest SPs in place, we proceeded to backup the entire <MSSQL\Microsoft Analysis Services\Data folder containing all the AS databases onto a different location as a fall back position. At this point, (with an empty /data folder) we proceeded to start the AS related services (MSSQLServerOLAPService) and they were steady. I then proceeded to iteratively re-introduce the AS Databases one folder at a time from the previously backed up location (<backuplocation>\MSSQL\Microsoft Analysis Services\Data\<AS databases> until the folder that caused the services to start crashing was identified. Once this folder was identified, I deleted it from the /data folder and process the appropriate dimensions/cubes to regenerate the AS databases. Make sure that your .odb file is backed up safely as an added precaution.

MSSQLServerADHelper is problem?

MSSQLServerADHelper isn't running and we can't get it to
start. System Event Log says "The MSSQLServerADHelper
service terminated with service-specific error 3221225572."
Any clues at all how to fix?

>--Original Message--
>That's SQL Server 2000 (sorry!) and Windows (Server)
>2000... it's almost like SQL isn't reading from or
>synchronizing with Active Directory properly, but we can
>find no other indicator that there is a problem.
>Again, any help is greatly appreciated!
>
>login
I
>a
the
>.
>That's normal behavior. You can't start the service
manually. It runs when requested to by SQL Server service or
Analysis Server service and then stops running when it's
completed it's work.
-Sue
On Thu, 25 Mar 2004 12:27:49 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>MSSQLServerADHelper isn't running and we can't get it to
>start. System Event Log says "The MSSQLServerADHelper
>service terminated with service-specific error 3221225572."
>Any clues at all how to fix?
>
>I
>the|||Well I was just trying to find something... is there any
way to see if it's working properly when it's supposed to
be working? My gut tells me this problem has to do with
AD somehow...
Can you think of any other options or ways to fix?

>--Original Message--
>That's normal behavior. You can't start the service
>manually. It runs when requested to by SQL Server service
or
>Analysis Server service and then stops running when it's
>completed it's work.
>-Sue
>On Thu, 25 Mar 2004 12:27:49 -0800, "Sandy Mach"
><anonymous@.discussions.microsoft.com> wrote:
>
3221225572."
can
if
in
adding
and
won't
then
>.
>|||Try revoking the login and then re-add it and see if you can
add the login as a database user.
Is the a problem for all logins or just one or a few? Is it
a problem with trying to add them to any database or just
one specific database?
-Sue
On Thu, 25 Mar 2004 13:31:55 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>Well I was just trying to find something... is there any
>way to see if it's working properly when it's supposed to
>be working? My gut tells me this problem has to do with
>AD somehow...
>Can you think of any other options or ways to fix?
>
>or
>3221225572."
>can
>if
>in
>adding
>and
>won't
>then|||Well, that did the job, but now I have to re-set the
group's permissions on each db, some of which contain over
200 tables... yikes. I guess I could look at the bright
side--I should only have to do this once!
Thanks for your help Sue.
Sandy

>--Original Message--
>Try revoking the login and then re-add it and see if you
can
>add the login as a database user.
>Is the a problem for all logins or just one or a few? Is
it
>a problem with trying to add them to any database or just
>one specific database?
>-Sue
>On Thu, 25 Mar 2004 13:31:55 -0800, "Sandy Mach"
><anonymous@.discussions.microsoft.com> wrote:
>
to
service
to
but
error
looked
use|||Your welcome...glad it's working now and thanks for posting
back.
-Sue
On Thu, 25 Mar 2004 14:22:19 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>Well, that did the job, but now I have to re-set the
>group's permissions on each db, some of which contain over
>200 tables... yikes. I guess I could look at the bright
>side--I should only have to do this once!
>Thanks for your help Sue.
>Sandy
>
>can
>it
>to
>service
>to
>but
>error
>looked
>use

MSSQLSERVER service hangs on loading DTC

Hi All,
MSSSQLSERVER service is hanging for ever after auto reboot.
it stops at DTC loading :
SQL Server terminating because of system shutdown.
SQL Server is starting at priority class 'normal'(4 CPUs detected).
SQL Server configured for thread mode processing.
Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
Attempting to initialize Distributed Transaction Coordinator.
.........
..............
DTC service is disabled and running under local system account.
Sql services are running under domain admin account.
We are starting it manually every time this occurs.
the version is
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
There is below DCOM error in the eveny log at the same time.Is this causing
the problem?
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
Can any one shed some light on it?
Thanks,
Suchi
Some more info:
Start up modes are as below:
Mssqlserver --manual
SQLagent--Manual
DTC --manual
Disabled auto-startup of the 3 services from within EM.
Thanks,
Suchi
"Suchi" wrote:

> Hi All,
> MSSSQLSERVER service is hanging for ever after auto reboot.
> it stops at DTC loading :
> SQL Server terminating because of system shutdown.
> SQL Server is starting at priority class 'normal'(4 CPUs detected).
> SQL Server configured for thread mode processing.
> Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> Attempting to initialize Distributed Transaction Coordinator.
> ........
> .............
> DTC service is disabled and running under local system account.
> Sql services are running under domain admin account.
> We are starting it manually every time this occurs.
> the version is
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
> There is below DCOM error in the eveny log at the same time.Is this causing
> the problem?
> DCOM got error "The service cannot be started, either because it is disabled
> or because it has no enabled devices associated with it. " attempting to
> start the service EventSystem with arguments "" in order to run the server:
> {1BE1F766-5536-11D1-B726-00C04FB926AF}
> Can any one shed some light on it?
> Thanks,
> Suchi
>
|||Did you try reinstalling DTC?
I dont' think DCOM alert has something to do with it...not sure doh.

MSSQLSERVER service hangs on loading DTC

Hi All,
MSSSQLSERVER service is hanging for ever after auto reboot.
it stops at DTC loading :
SQL Server terminating because of system shutdown.
SQL Server is starting at priority class 'normal'(4 CPUs detected).
SQL Server configured for thread mode processing.
Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
Attempting to initialize Distributed Transaction Coordinator.
........
.............
DTC service is disabled and running under local system account.
Sql services are running under domain admin account.
We are starting it manually every time this occurs.
the version is
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
There is below DCOM error in the eveny log at the same time.Is this causing
the problem?
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
Can any one shed some light on it?
Thanks,
SuchiSome more info:
Start up modes are as below:
Mssqlserver --manual
SQLagent--Manual
DTC --manual
Disabled auto-startup of the 3 services from within EM.
Thanks,
Suchi
"Suchi" wrote:
> Hi All,
> MSSSQLSERVER service is hanging for ever after auto reboot.
> it stops at DTC loading :
> SQL Server terminating because of system shutdown.
> SQL Server is starting at priority class 'normal'(4 CPUs detected).
> SQL Server configured for thread mode processing.
> Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> Attempting to initialize Distributed Transaction Coordinator.
> ........
> .............
> DTC service is disabled and running under local system account.
> Sql services are running under domain admin account.
> We are starting it manually every time this occurs.
> the version is
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
> There is below DCOM error in the eveny log at the same time.Is this causing
> the problem?
> DCOM got error "The service cannot be started, either because it is disabled
> or because it has no enabled devices associated with it. " attempting to
> start the service EventSystem with arguments "" in order to run the server:
> {1BE1F766-5536-11D1-B726-00C04FB926AF}
> Can any one shed some light on it?
> Thanks,
> Suchi
>|||Did you try reinstalling DTC?
I dont' think DCOM alert has something to do with it...not sure doh.

MSSQLSERVER service hangs on loading DTC

Am using SQL 2000 SP4
Whenever the system is re-booted, SQL service hangs while loading. The
last entry ion the startup log indicates is :
"Attempting to initialize Distributed Transaction Coordinator"
When I check the services, DTC is running.
To fix the problem I manually kill (pskill) the process, log off and
then log back in.
Once logged back in, I manually start the SQL server and agent.
SteveHi Steve
Do you have autostart DTC enabled, if so you may want to try removing it
(server properties page in EM).
John
"Steve Babcock" wrote:
> Am using SQL 2000 SP4
> Whenever the system is re-booted, SQL service hangs while loading. The
> last entry ion the startup log indicates is :
> "Attempting to initialize Distributed Transaction Coordinator"
> When I check the services, DTC is running.
> To fix the problem I manually kill (pskill) the process, log off and
> then log back in.
> Once logged back in, I manually start the SQL server and agent.
> Steve
>|||John - tried disabling DTC from starting up (which it did - service was not
running) this but the result was the same - last entry in startup log is :
"Attempting to initialize Distributed Transaction Coordinator"
Steve
John Bell wrote:
> Hi Steve
> Do you have autostart DTC enabled, if so you may want to try removing it
> (server properties page in EM).
> John
> "Steve Babcock" wrote:
> > Am using SQL 2000 SP4
> >
> > Whenever the system is re-booted, SQL service hangs while loading. The
> > last entry ion the startup log indicates is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > When I check the services, DTC is running.
> >
> > To fix the problem I manually kill (pskill) the process, log off and
> > then log back in.
> > Once logged back in, I manually start the SQL server and agent.
> >
> > Steve
> >
> >|||Hi Steve
Have you tried making SQLServer and DTC manual services, then starting SQL
Server from a command line, to see what happens?
John
"Steve Babcock" wrote:
> John - tried disabling DTC from starting up (which it did - service was not
> running) this but the result was the same - last entry in startup log is :
> "Attempting to initialize Distributed Transaction Coordinator"
> Steve
> John Bell wrote:
> > Hi Steve
> >
> > Do you have autostart DTC enabled, if so you may want to try removing it
> > (server properties page in EM).
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > Am using SQL 2000 SP4
> > >
> > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > last entry ion the startup log indicates is :
> > > "Attempting to initialize Distributed Transaction Coordinator"
> > >
> > > When I check the services, DTC is running.
> > >
> > > To fix the problem I manually kill (pskill) the process, log off and
> > > then log back in.
> > > Once logged back in, I manually start the SQL server and agent.
> > >
> > > Steve
> > >
> > >
>|||That's our next step - will have to do it later today outside of office hours.
John Bell wrote:
> Hi Steve
> Have you tried making SQLServer and DTC manual services, then starting SQL
> Server from a command line, to see what happens?
> John
> "Steve Babcock" wrote:
> > John - tried disabling DTC from starting up (which it did - service was not
> > running) this but the result was the same - last entry in startup log is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > (server properties page in EM).
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > Am using SQL 2000 SP4
> > > >
> > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > last entry ion the startup log indicates is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > When I check the services, DTC is running.
> > > >
> > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > then log back in.
> > > > Once logged back in, I manually start the SQL server and agent.
> > > >
> > > > Steve
> > > >
> > > >
> >
> >|||John :
I disabled auto-startup of the 3 services from within EM, re-booted and loaded
each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
Is there a way to see a more detailed log so that I can tell where it's hangin up
on loading. Even though it says it's waiting for DTC, DTC is running as a
service when SQL is trying to start up.
Steve
John Bell wrote:
> Hi Steve
> Have you tried making SQLServer and DTC manual services, then starting SQL
> Server from a command line, to see what happens?
> John
> "Steve Babcock" wrote:
> > John - tried disabling DTC from starting up (which it did - service was not
> > running) this but the result was the same - last entry in startup log is :
> > "Attempting to initialize Distributed Transaction Coordinator"
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > (server properties page in EM).
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > Am using SQL 2000 SP4
> > > >
> > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > last entry ion the startup log indicates is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > When I check the services, DTC is running.
> > > >
> > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > then log back in.
> > > > Once logged back in, I manually start the SQL server and agent.
> > > >
> > > > Steve
> > > >
> > > >
> >
> >|||Hi
The SQL Server log will log each event in the same way as you should see how
when it manually started. You could add a dependency of SQL Server on DTC so
that it does not even try to start before DTC has started. I don't know if
the DTC service logs anywhere other than the event log.
John
"Steve Babcock" wrote:
> John :
> I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> Is there a way to see a more detailed log so that I can tell where it's hangin up
> on loading. Even though it says it's waiting for DTC, DTC is running as a
> service when SQL is trying to start up.
> Steve
> John Bell wrote:
> > Hi Steve
> >
> > Have you tried making SQLServer and DTC manual services, then starting SQL
> > Server from a command line, to see what happens?
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > John - tried disabling DTC from starting up (which it did - service was not
> > > running) this but the result was the same - last entry in startup log is :
> > > "Attempting to initialize Distributed Transaction Coordinator"
> > >
> > > Steve
> > >
> > > John Bell wrote:
> > >
> > > > Hi Steve
> > > >
> > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > (server properties page in EM).
> > > >
> > > > John
> > > >
> > > > "Steve Babcock" wrote:
> > > >
> > > > > Am using SQL 2000 SP4
> > > > >
> > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > last entry ion the startup log indicates is :
> > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > >
> > > > > When I check the services, DTC is running.
> > > > >
> > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > then log back in.
> > > > > Once logged back in, I manually start the SQL server and agent.
> > > > >
> > > > > Steve
> > > > >
> > > > >
> > >
> > >
>|||How do I set up the dependency - I don;t see where in Services I can do this.
Steve
John Bell wrote:
> Hi
> The SQL Server log will log each event in the same way as you should see how
> when it manually started. You could add a dependency of SQL Server on DTC so
> that it does not even try to start before DTC has started. I don't know if
> the DTC service logs anywhere other than the event log.
> John
> "Steve Babcock" wrote:
> > John :
> >
> > I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> > each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> >
> > Is there a way to see a more detailed log so that I can tell where it's hangin up
> > on loading. Even though it says it's waiting for DTC, DTC is running as a
> > service when SQL is trying to start up.
> >
> > Steve
> >
> > John Bell wrote:
> >
> > > Hi Steve
> > >
> > > Have you tried making SQLServer and DTC manual services, then starting SQL
> > > Server from a command line, to see what happens?
> > >
> > > John
> > >
> > > "Steve Babcock" wrote:
> > >
> > > > John - tried disabling DTC from starting up (which it did - service was not
> > > > running) this but the result was the same - last entry in startup log is :
> > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > >
> > > > Steve
> > > >
> > > > John Bell wrote:
> > > >
> > > > > Hi Steve
> > > > >
> > > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > > (server properties page in EM).
> > > > >
> > > > > John
> > > > >
> > > > > "Steve Babcock" wrote:
> > > > >
> > > > > > Am using SQL 2000 SP4
> > > > > >
> > > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > > last entry ion the startup log indicates is :
> > > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > > >
> > > > > > When I check the services, DTC is running.
> > > > > >
> > > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > > then log back in.
> > > > > > Once logged back in, I manually start the SQL server and agent.
> > > > > >
> > > > > > Steve
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >|||Hi Steve
Dependencies should be a tab on the properties dialog for the services
applet (from administrators on the start menu or control panel). If you
double clicking your SQL Server service it should appear.
John
"Steve Babcock" wrote:
> How do I set up the dependency - I don;t see where in Services I can do this.
> Steve
> John Bell wrote:
> > Hi
> >
> > The SQL Server log will log each event in the same way as you should see how
> > when it manually started. You could add a dependency of SQL Server on DTC so
> > that it does not even try to start before DTC has started. I don't know if
> > the DTC service logs anywhere other than the event log.
> >
> > John
> >
> > "Steve Babcock" wrote:
> >
> > > John :
> > >
> > > I disabled auto-startup of the 3 services from within EM, re-booted and loaded
> > > each one from the SQL Manager in order for DTC, SQL, SQLA - all was OK.
> > >
> > > Is there a way to see a more detailed log so that I can tell where it's hangin up
> > > on loading. Even though it says it's waiting for DTC, DTC is running as a
> > > service when SQL is trying to start up.
> > >
> > > Steve
> > >
> > > John Bell wrote:
> > >
> > > > Hi Steve
> > > >
> > > > Have you tried making SQLServer and DTC manual services, then starting SQL
> > > > Server from a command line, to see what happens?
> > > >
> > > > John
> > > >
> > > > "Steve Babcock" wrote:
> > > >
> > > > > John - tried disabling DTC from starting up (which it did - service was not
> > > > > running) this but the result was the same - last entry in startup log is :
> > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > >
> > > > > Steve
> > > > >
> > > > > John Bell wrote:
> > > > >
> > > > > > Hi Steve
> > > > > >
> > > > > > Do you have autostart DTC enabled, if so you may want to try removing it
> > > > > > (server properties page in EM).
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "Steve Babcock" wrote:
> > > > > >
> > > > > > > Am using SQL 2000 SP4
> > > > > > >
> > > > > > > Whenever the system is re-booted, SQL service hangs while loading. The
> > > > > > > last entry ion the startup log indicates is :
> > > > > > > "Attempting to initialize Distributed Transaction Coordinator"
> > > > > > >
> > > > > > > When I check the services, DTC is running.
> > > > > > >
> > > > > > > To fix the problem I manually kill (pskill) the process, log off and
> > > > > > > then log back in.
> > > > > > > Once logged back in, I manually start the SQL server and agent.
> > > > > > >
> > > > > > > Steve
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>

MSSQLSERVER service hangs on loading DTC

Hi All,
MSSSQLSERVER service is hanging for ever after auto reboot.
it stops at DTC loading :
SQL Server terminating because of system shutdown.
SQL Server is starting at priority class 'normal'(4 CPUs detected).
SQL Server configured for thread mode processing.
Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner
Blocks.
Attempting to initialize Distributed Transaction Coordinator.
........
.............
DTC service is disabled and running under local system account.
Sql services are running under domain admin account.
We are starting it manually every time this occurs.
the version is
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
There is below DCOM error in the eveny log at the same time.Is this causing
the problem?
DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
Can any one shed some light on it?
Thanks,
SuchiSome more info:
Start up modes are as below:
Mssqlserver --manual
SQLagent--Manual
DTC --manual
Disabled auto-startup of the 3 services from within EM.
Thanks,
Suchi
"Suchi" wrote:

> Hi All,
> MSSSQLSERVER service is hanging for ever after auto reboot.
> it stops at DTC loading :
> SQL Server terminating because of system shutdown.
> SQL Server is starting at priority class 'normal'(4 CPUs detected).
> SQL Server configured for thread mode processing.
> Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Own
er Blocks.
> Attempting to initialize Distributed Transaction Coordinator.
> ........
> .............
> DTC service is disabled and running under local system account.
> Sql services are running under domain admin account.
> We are starting it manually every time this occurs.
> the version is
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
> There is below DCOM error in the eveny log at the same time.Is this causin
g
> the problem?
> DCOM got error "The service cannot be started, either because it is disabl
ed
> or because it has no enabled devices associated with it. " attempting to
> start the service EventSystem with arguments "" in order to run the server
:
> {1BE1F766-5536-11D1-B726-00C04FB926AF}
> Can any one shed some light on it?
> Thanks,
> Suchi
>|||Did you try reinstalling DTC?
I dont' think DCOM alert has something to do with it...not sure doh.

MSSQLServer

Hi
I have created a ghost of a system running SQL server 7 (on windows 2000 server).
When I try and start MSSQLServer I get the message:
Your SQL Server installation is either corrupt ot has been tampered with (unknown package id).
Any ideas on how I can fix this without rerunning setup.
Thanks
Conor
Re-run setup. See http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Conor" <anonymous@.discussions.microsoft.com> wrote in message
news:479704EB-01A0-4AF2-BCB0-5D699ECD2ABA@.microsoft.com...
> Hi
> I have created a ghost of a system running SQL server 7 (on windows 2000 server).
> When I try and start MSSQLServer I get the message:
> Your SQL Server installation is either corrupt ot has been tampered with (unknown package id).
> Any ideas on how I can fix this without rerunning setup.
> Thanks
> Conor
|||This is correct. SQL Server 7.0 does not support ghosted installations.
Rand
This posting is provided "as is" with no warranties and confers no rights.