MSSQL Mistake: windows

Showing posts with label windows. Show all posts

Wednesday, March 21, 2012

MSTDC and windows domain

Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.
make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> SQL2000/MSTDC
> 'SQLOLEDB'
> any
>
|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default...b;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>

MSTDC and windows domain

Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> i have this scenario :
>> a have web application (NT4) that use a MSTDC service on my application
>> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
>> The service MSTDC on application server and db server start with the same
>> domain administration account (administrator)
>> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC
>> on 2 windows 2003 server and try to modify my application to point to new
>> windows 2003 cluster but when i try to test it a error appared :
>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
>> was unable to begin a distributed transaction. OLE/DB provider returned
>> message: New transaction cannot enlist in the specified transaction
>> coordinator.
>> and found a kb article and make the modify adding a network service into
>> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
>> This is because are 2 different domain and network service on 2003 isn't
> any
>> account on NT4 domain ?
>> If i try to trust a windows 2003 and NT4 domain i resolved it ?
>> The trust is only one solution or exist other solution ?
>> Thanks in advance.
>>
>|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827805http://support.microsoft.com/default.aspx?scid=kb;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>

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

MSSQServer 2000 for pocket pc

Hi to all.
I have a windows ce mssqlserver 2000 version.
I have writted a java application and i needed a database connection.
I wish a driver for execute the connection to mssql server 2000 into pocket pc.

The connection string that i use is

connessione = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;databasename=A&MMobile", "sa", "sa");

Ok?

Which are the driver that i needed?

Thanx,

SimonaOriginally posted by simona
Hi to all.
I have a windows ce mssqlserver 2000 version.
I have writted a java application and i needed a database connection.
I wish a driver for execute the connection to mssql server 2000 into pocket pc.

The connection string that i use is

connessione = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;databasename=A&MMobile", "sa", "sa");

Ok?

Which are the driver that i needed?

Thanx,

Simona

Sorry but i'cant help you.

But i'm interrested for your java application.

which is the JVM which you use ?
Could you give me a java for ppc sample code 'HELLO WORLD!' ?

thank you,

Guiguix.|||Hi,
yhe java code is traditionally.

You write a "Hello world" java code and you copy it in the pocket pc.
The jvm is Creme. It support swing! But the needed java version is very old. I use the java 1.1.8 ;(

Bye :)|||There are two steps to establish a connection:

(1) loading the driver
If you want to use the JDBC-ODBC Bridge driver, the following code will load it.

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

(2) making the connection
If you are using the JDBC-ODBC Bridge driver, you can use

String url = "jdbc: odbc:ODBC_DataSourceName";
Connection con = DriverManager.getConnection(url, "myLogin", "myPassword");

Note that there is no space between jdbc: and odbc in url. If I remove it a sign will be shown in the code.|||And is this ok for pocket pc?
Wow!|||When you say "pocket PC", it is a laptop, right? I didn't try the connection on SQL Server 2000 Windows CE Edition, but it works for the other versions of SQL Server 2000.|||Pocket pc is a palm. Not Palm OS, but pocket pc.
MSSqlServer 2000 works on pc desktop but not on pocket pc.
Moreover the strings

----------------------
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

String url = "jdbc: odbc://localhost:1433;databasename=AeMMobile";

connessione = DriverManager.getConnection(url, "sa", "sa");
-----------------------

don't work.

While with

----------------------

Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");

connessione = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;databasename=AeMMobile", "sa", "sa");

--------------------

on pc desktop is ok.
My problem is on pocket pc?
Do you know the solution?|||I do not know what the pocket PC is. I have a question. Since the SQL server is on the desktop which should be a Windows server, is your pocket PC connected to that server?|||The pocket pc is an hp 2002.
If you means that pocket pc is connected with replication data... yes.

MSSQLSeverADHelper

When trying to add the SQL server to the Windows 2000
Active Directory I get the following error
Error 14354: Cannot start the MSSQLSeverADHelper
Service. Verify that the service account for this SQL
Server instance has the necessary permissions to start
the MSSQLSeverADHelper service.Is the service on the machine? If not, something probably
went wrong with the install where some registry keys are
missing - reinstalling is the cleanest option in this case.
Otherwise check the service account for SQL Server to make
sure it has the appropriate permissions.
-Sue
On Fri, 15 Aug 2003 17:29:15 -0700, "Michael Luna"
<michael@.winvotes.com> wrote:
>When trying to add the SQL server to the Windows 2000
>Active Directory I get the following error
>Error 14354: Cannot start the MSSQLSeverADHelper
>Service. Verify that the service account for this SQL
>Server instance has the necessary permissions to start
>the MSSQLSeverADHelper service.

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 :

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 :

and...

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 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?

|||

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 :

and...

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 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?

|||

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 :

and...

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 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?

|||

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 :

and...

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 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?

|||

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server. In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart. Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
--
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server. In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart. Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR

> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server.
In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart.
Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR
> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
--
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

mssqlserverADhelper service terminated, Access Denied when trying to connect

This problem just started recently. This computer connected to the database
when it was first installed. All computer are new Compaq running Windows xp
pro.
This is a problem with MSDE. We are running MS Retail Management system.
One Point of Sale station won't connect to the server. I am running MSDE on
4 computers. One is the peer server it is named "serverxp" the one that
won't connect is "POS2". Other computers are POS1 and notebook. Below is
the case notes so far.
This one POS station is having a problem connection to the server database.
It has no problem connecting to the local database. What I see is on the SQL
Service Manager, When I select the network server "ServerXP" there is
nothing in the dropdown for services. When I select the local server then
three options are listed Dist. Tran, SQL Server and SQL Server agent.
This POS2 computer can connect to ServerXP and see shared folders etc. So I
haven't found any problem with the LAN or hardware.
Can you tell by this description what is wrong or what to try to do to fix
this?
Thanks
----
6/9/2004 1:28:00 PM CDT -- Allison Haaland
Steven,
I have a few more questions for you in order to further troubleshoot this
issue:
1. When you look at the SQL Server Service Manager and choose the "ServerXP"
option, does it say Not Connected at the bottom? yes
2. When you select the local server option in SQL Server Service Manager,
can you then connect to the database in Administrator? (You would choose
local as your server in Administrator as well.) yes
3. If you go to Start | Control | Administrative Tools | Services, do you
see your MSSQL and SQLAgent options there? If so, is the Status showing as
'Started'? If not, you should make sure that the Services are started if
you're trying to use them.
.MSSQLServer is started
MSSQLServerADhelper is set to manual and will not start "could not start
access denied"
4. Is there anything else that is different about this workstation from the
others? This might help us find out why it is not working, but all of the
others are. no
Thanks,
Allison
----
6/9/2004 3:51:00 PM CDT -- Steven
Allison:
More Info. An error in the System error log shows.
The mssqlserverADhelper service terminated with service specific error
3221225572 error 2270 refer to Knowledge base 314094. ID 7024
this is talking about the computer name. The name of this PC is POS2 it is
unique on this network.
----
6/9/2004 4:43:00 PM CDT -- Allison Haaland
Steven,
It looks like the error you are running into now is a network related issue
related to your computer name. I see that you have already referenced
Knowledge base article #314094 - have you tried the steps that it gives to
resolve this error? YES.
POS2 was working correctly at the time it was installed. No name have been
changed.
Can anyone with more experience working with SQL server give me some help
correcting this problem? Thank you.Hi Steve,
What error is generated with the connection fails?
Create an ODBC Test DSN and post the entire message here.
The ADHelper servers is not required for machines to connect to one
another. It's used to publish objects to Active Directory.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

mssqlserverADhelper service terminated, Access Denied when trying to connect

This problem just started recently. This computer connected to the database
when it was first installed. All computer are new Compaq running Windows xp
pro.
This is a problem with MSDE. We are running MS Retail Management system.
One Point of Sale station won't connect to the server. I am running MSDE on
4 computers. One is the peer server it is named "serverxp" the one that
won't connect is "POS2". Other computers are POS1 and notebook. Below is
the case notes so far.
This one POS station is having a problem connection to the server database.
It has no problem connecting to the local database. What I see is on the SQL
Service Manager, When I select the network server "ServerXP" there is
nothing in the dropdown for services. When I select the local server then
three options are listed Dist. Tran, SQL Server and SQL Server agent.
This POS2 computer can connect to ServerXP and see shared folders etc. So I
haven't found any problem with the LAN or hardware.
Can you tell by this description what is wrong or what to try to do to fix
this?
Thanks
6/9/2004 1:28:00 PM CDT -- Allison Haaland
Steven,
I have a few more questions for you in order to further troubleshoot this
issue:
1. When you look at the SQL Server Service Manager and choose the "ServerXP"
option, does it say Not Connected at the bottom? yes
2. When you select the local server option in SQL Server Service Manager,
can you then connect to the database in Administrator? (You would choose
local as your server in Administrator as well.) yes
3. If you go to Start | Control | Administrative Tools | Services, do you
see your MSSQL and SQLAgent options there? If so, is the Status showing as
'Started'? If not, you should make sure that the Services are started if
you're trying to use them.
..MSSQLServer is started
MSSQLServerADhelper is set to manual and will not start "could not start
access denied"
4. Is there anything else that is different about this workstation from the
others? This might help us find out why it is not working, but all of the
others are. no
Thanks,
Allison
6/9/2004 3:51:00 PM CDT -- Steven
Allison:
More Info. An error in the System error log shows.
The mssqlserverADhelper service terminated with service specific error
3221225572 error 2270 refer to Knowledge base 314094. ID 7024
this is talking about the computer name. The name of this PC is POS2 it is
unique on this network.
6/9/2004 4:43:00 PM CDT -- Allison Haaland
Steven,
It looks like the error you are running into now is a network related issue
related to your computer name. I see that you have already referenced
Knowledge base article #314094 - have you tried the steps that it gives to
resolve this error? YES.
POS2 was working correctly at the time it was installed. No name have been
changed.
Can anyone with more experience working with SQL server give me some help
correcting this problem? Thank you.
Hi Steve,
What error is generated with the connection fails?
Create an ODBC Test DSN and post the entire message here.
The ADHelper servers is not required for machines to connect to one
another. It's used to publish objects to Active Directory.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Monday, March 19, 2012

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
Aaron
Hi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.c om...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron
|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.c om...

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
AaronHi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.com...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP
11.phx.gbl>...[vbcol=seagreen]
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.com...

MSSQLSERVER service security

I have a Windows 2000 server on which I am running SQL Server 2000
SP3. Unfortunately, this particular Windows server has far too many
accounts in the Local Administrators group. Recently we had an
incident in which a production SQL Server was stopped and restarted
unexpectedly. I suspect it was a person who did this since the service
was started back up within a minute or so of being shutdown, and the
SQL Server Agent was not restarted. No one has fessed up yet, and I
don't expect anyone to do so.
Securing the server is a long-term solution, but I need to do
something in the short term to prevent this from happening again. The
only thing I can think to do is to further limit who can stop and
start the SQL Server Service. Is there a way to specify who can and
cannot stop/start the SQL Server service, excluding even members of
the Local Administrators group?
P.S. Auditing has been ruled out as an option.
Thanks,
AaronHi,
OS Users who fall under local admin group can stop and start any services.
The best solution is to remove the
users from Local admin groups of sql server machine.
--
Thanks
Hari
MCDBA
"Vols Fan" <volsfan1998@.hotmail.com> wrote in message
news:2489efb1.0407191441.7c492135@.posting.google.com...
> I have a Windows 2000 server on which I am running SQL Server 2000
> SP3. Unfortunately, this particular Windows server has far too many
> accounts in the Local Administrators group. Recently we had an
> incident in which a production SQL Server was stopped and restarted
> unexpectedly. I suspect it was a person who did this since the service
> was started back up within a minute or so of being shutdown, and the
> SQL Server Agent was not restarted. No one has fessed up yet, and I
> don't expect anyone to do so.
> Securing the server is a long-term solution, but I need to do
> something in the short term to prevent this from happening again. The
> only thing I can think to do is to further limit who can stop and
> start the SQL Server Service. Is there a way to specify who can and
> cannot stop/start the SQL Server service, excluding even members of
> the Local Administrators group?
> P.S. Auditing has been ruled out as an option.
> Thanks,
> Aaron|||I am aware of this, but as I said, until we can further secure this
server, I need a short term solution.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message news:<e5EEzXhbEHA.3480@.TK2MSFTNGP11.phx.gbl>...
> Hi,
> OS Users who fall under local admin group can stop and start any services.
> The best solution is to remove the
> users from Local admin groups of sql server machine.
> --
> Thanks
> Hari
> MCDBA
> "Vols Fan" <volsfan1998@.hotmail.com> wrote in message
> news:2489efb1.0407191441.7c492135@.posting.google.com...
> > I have a Windows 2000 server on which I am running SQL Server 2000
> > SP3. Unfortunately, this particular Windows server has far too many
> > accounts in the Local Administrators group. Recently we had an
> > incident in which a production SQL Server was stopped and restarted
> > unexpectedly. I suspect it was a person who did this since the service
> > was started back up within a minute or so of being shutdown, and the
> > SQL Server Agent was not restarted. No one has fessed up yet, and I
> > don't expect anyone to do so.
> >
> > Securing the server is a long-term solution, but I need to do
> > something in the short term to prevent this from happening again. The
> > only thing I can think to do is to further limit who can stop and
> > start the SQL Server Service. Is there a way to specify who can and
> > cannot stop/start the SQL Server service, excluding even members of
> > the Local Administrators group?
> >
> > P.S. Auditing has been ruled out as an option.
> >
> > Thanks,
> > Aaron

Monday, March 12, 2012

MSSqlServer service and Windows password reset

Hello,
I hope you guys can help me with a problem that I am facing...

I have started the MSSqlServer service and SQLServerAgent services
with a domain username and password.
There are periodic password resets to this user. Security policies
within the company dictate that the password for this domain account
cannot be permenant.

Would there be any way to automatically reset the pwd in these
services instead of manually changing them each time?

ThanksKannan (pv_kannan@.yahoo.com) writes:
> Would there be any way to automatically reset the pwd in these
> services instead of manually changing them each time?

I doubt there is, but since this is not really a MS SQL Server issue,
but rather a generic Windows question, a question to the approriate
newsgroup for Windows.

Personally, I would investigate possibilities to set up the account
so that it only can log in as service or some such, which would permit
unexpirable passwords.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

MSSqlServer service and Windows password reset

Hello,
I hope you guys can help me with a problem that I am facing...
I have started the MSSqlServer service and SQLServerAgent services
with a domain username and password.
There are periodic password resets to this user. Security policies
within the company dictate that the password for this domain account
cannot be permenant.
Would there be any way to automatically reset the pwd in these
services instead of manually changing them each time?
ThanksKannan,
Is there a specific reason why these can't run under
system?
If not, try to shift the responsibility back to the group
with the security requirement. It would be reasonable to
ask that the admin user who changes the password should
also update the password in the services at the same time
(to ensure continuous availability). If this becomes too
onerous for them, perhaps they'll rethink their
application of the policy in this case.
BTW, I don't think services need to be stopped in order to
change the account password (i.e., wouldn't affect
availability). Can anyone else confirm?
...Jeff
>--Original Message--
>Hello,
>I hope you guys can help me with a problem that I am
facing...
>I have started the MSSqlServer service and SQLServerAgent
services
>with a domain username and password.
>There are periodic password resets to this user. Security
policies
>within the company dictate that the password for this
domain account
>cannot be permenant.
>Would there be any way to automatically reset the pwd in
these
>services instead of manually changing them each time?
>Thanks
>.
>

Wednesday, March 21, 2012

MSTDC and windows domain

MSTDC and windows domain

MSSRS 2000 Restarts Windows XP system after the latest update

MSSQServer 2000 for pocket pc

MSSQLSeverADHelper

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPServi - Server - 129

MSSQLServerOLAPServi - Server - 129

MSSQLServerOLAPServi - Server - 129

mssqlserverADhelper service terminated, Access Denied when trying to connect

mssqlserverADhelper service terminated, Access Denied when trying to connect

Monday, March 19, 2012

MSSQLSERVER service security

MSSQLSERVER service security

MSSQLSERVER service security

Monday, March 12, 2012

MSSqlServer service and Windows password reset

MSSqlServer service and Windows password reset

MSSQL Mistake

Blog Archive

About Me