MSSQL Mistake: sp1

Showing posts with label sp1. Show all posts

Friday, March 30, 2012

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leil|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>> I am running two instances of SQL Server 2005 Developer Edition (SP1)
>> on the same machine. Both SQL Server and Agent services use a local
>> user account which is member of Windows Administrators. The wizard for
>> Enlisting TSX fails with the following report:
>> Enlist TSX Progress
>> - Create MSXOperator (Success)
>> Checking for an existing MSXOperator.
>> Updating existing MSXOperator.
>> Successfully updated MSXOperator.
>> - Make sure the Agent service for 'NIMA\sql2005_1' is running
>> (Success)
>> The service 'SQLAgent$SQL2005_1' is running.
>> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
>> Enlisting target server 'NIMA\sql2005_2' with master server
>> 'NIMA\sql2005_1'.
>> Using new enlistment method.
>> Messages
>> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
>> (Microsoft.SqlServer.Smo)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
>> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
>> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
>> 6
>> --
>> ADDITIONAL INFORMATION:
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The enlist operation failed (reason: SQLServerAgent Error: Unable to
>> connect to server. .) (Microsoft SQL Server, Error: 22026)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
>> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
>> Any help would be greatly appreciated,
>> leila
>

Multi Server Jobs

Wednesday, March 28, 2012

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management. Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>

Wednesday, March 21, 2012

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?

|||

Friday, March 9, 2012

MSSQL2K and WIN2K3 SP1

We have a Windows Server 2003 Standard with SQL Server 2000 Standard
edition serving as a development server. There are several DTS packages
hosted on the server and they connect to an entry from the local hosts
table. The reason for this is that each of the DEV, QA and PROD
servers in this group have an entry with the same name (ex. SVR_DBNAME)
but each of which point to their own IP address, allowing us to copy
the packages between servers without going back and changing all the
server name references.
Recently, WIN2K3 SP1 was installed on the machine and immediately, the
DTS packages - which use WIndows Authentication - failed with a message
indicating that the system could not authenticate against the local
Windows user:
Login failed for user '(null)'
Once SP1 was removed, the packages resumed working. What setting does
the service pack change that is causing this?
thanks
mark
Hi
A couple of questions
Does the server/s have Mixed authentication mode or windows only?
Did you try ( If I understood correctly) to add an owner of DTS Packages to
the group of Admin of WIN2K3?
<markfcook@.gmail.com> wrote in message
news:1161054855.189750.67760@.m73g2000cwd.googlegro ups.com...
> We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> edition serving as a development server. There are several DTS packages
> hosted on the server and they connect to an entry from the local hosts
> table. The reason for this is that each of the DEV, QA and PROD
> servers in this group have an entry with the same name (ex. SVR_DBNAME)
> but each of which point to their own IP address, allowing us to copy
> the packages between servers without going back and changing all the
> server name references.
> Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> DTS packages - which use WIndows Authentication - failed with a message
> indicating that the system could not authenticate against the local
> Windows user:
> Login failed for user '(null)'
> Once SP1 was removed, the packages resumed working. What setting does
> the service pack change that is causing this?
> thanks
> mark
>
|||Q1) mixed mode authentication is used
Q2) the windows account is a member of the local administrators group
Uri Dimant wrote:[vbcol=seagreen]
> Hi
> A couple of questions
> Does the server/s have Mixed authentication mode or windows only?
> Did you try ( If I understood correctly) to add an owner of DTS Packages to
> the group of Admin of WIN2K3?
>
>
>
> <markfcook@.gmail.com> wrote in message
> news:1161054855.189750.67760@.m73g2000cwd.googlegro ups.com...

MSSQL2K and WIN2K3 SP1

We have a Windows Server 2003 Standard with SQL Server 2000 Standard
edition serving as a development server. There are several DTS packages
hosted on the server and they connect to an entry from the local hosts
table. The reason for this is that each of the DEV, QA and PROD
servers in this group have an entry with the same name (ex. SVR_DBNAME)
but each of which point to their own IP address, allowing us to copy
the packages between servers without going back and changing all the
server name references.
Recently, WIN2K3 SP1 was installed on the machine and immediately, the
DTS packages - which use WIndows Authentication - failed with a message
indicating that the system could not authenticate against the local
Windows user:
Login failed for user '(null)'
Once SP1 was removed, the packages resumed working. What setting does
the service pack change that is causing this?
thanks
markHi
A couple of questions
Does the server/s have Mixed authentication mode or windows only?
Did you try ( If I understood correctly) to add an owner of DTS Packages to
the group of Admin of WIN2K3?
<markfcook@.gmail.com> wrote in message
news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...
> We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> edition serving as a development server. There are several DTS packages
> hosted on the server and they connect to an entry from the local hosts
> table. The reason for this is that each of the DEV, QA and PROD
> servers in this group have an entry with the same name (ex. SVR_DBNAME)
> but each of which point to their own IP address, allowing us to copy
> the packages between servers without going back and changing all the
> server name references.
> Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> DTS packages - which use WIndows Authentication - failed with a message
> indicating that the system could not authenticate against the local
> Windows user:
> Login failed for user '(null)'
> Once SP1 was removed, the packages resumed working. What setting does
> the service pack change that is causing this?
> thanks
> mark
>|||Q1) mixed mode authentication is used
Q2) the windows account is a member of the local administrators group
Uri Dimant wrote:[vbcol=seagreen]
> Hi
> A couple of questions
> Does the server/s have Mixed authentication mode or windows only?
> Did you try ( If I understood correctly) to add an owner of DTS Packages
to
> the group of Admin of WIN2K3?
>
>
>
> <markfcook@.gmail.com> wrote in message
> news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...

MSSQL2K and WIN2K3 SP1

We have a Windows Server 2003 Standard with SQL Server 2000 Standard
edition serving as a development server. There are several DTS packages
hosted on the server and they connect to an entry from the local hosts
table. The reason for this is that each of the DEV, QA and PROD
servers in this group have an entry with the same name (ex. SVR_DBNAME)
but each of which point to their own IP address, allowing us to copy
the packages between servers without going back and changing all the
server name references.
Recently, WIN2K3 SP1 was installed on the machine and immediately, the
DTS packages - which use WIndows Authentication - failed with a message
indicating that the system could not authenticate against the local
Windows user:
Login failed for user '(null)'
Once SP1 was removed, the packages resumed working. What setting does
the service pack change that is causing this?
thanks
markHi
A couple of questions
Does the server/s have Mixed authentication mode or windows only?
Did you try ( If I understood correctly) to add an owner of DTS Packages to
the group of Admin of WIN2K3?
<markfcook@.gmail.com> wrote in message
news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...
> We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> edition serving as a development server. There are several DTS packages
> hosted on the server and they connect to an entry from the local hosts
> table. The reason for this is that each of the DEV, QA and PROD
> servers in this group have an entry with the same name (ex. SVR_DBNAME)
> but each of which point to their own IP address, allowing us to copy
> the packages between servers without going back and changing all the
> server name references.
> Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> DTS packages - which use WIndows Authentication - failed with a message
> indicating that the system could not authenticate against the local
> Windows user:
> Login failed for user '(null)'
> Once SP1 was removed, the packages resumed working. What setting does
> the service pack change that is causing this?
> thanks
> mark
>|||Q1) mixed mode authentication is used
Q2) the windows account is a member of the local administrators group
Uri Dimant wrote:
> Hi
> A couple of questions
> Does the server/s have Mixed authentication mode or windows only?
> Did you try ( If I understood correctly) to add an owner of DTS Packages to
> the group of Admin of WIN2K3?
>
>
>
> <markfcook@.gmail.com> wrote in message
> news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...
> > We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> > edition serving as a development server. There are several DTS packages
> > hosted on the server and they connect to an entry from the local hosts
> > table. The reason for this is that each of the DEV, QA and PROD
> > servers in this group have an entry with the same name (ex. SVR_DBNAME)
> > but each of which point to their own IP address, allowing us to copy
> > the packages between servers without going back and changing all the
> > server name references.
> >
> > Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> > DTS packages - which use WIndows Authentication - failed with a message
> > indicating that the system could not authenticate against the local
> > Windows user:
> >
> > Login failed for user '(null)'
> >
> > Once SP1 was removed, the packages resumed working. What setting does
> > the service pack change that is causing this?
> >
> > thanks
> >
> > mark
> >

MSSQL2005 SP1 setup

I have an Evaluation version of Enterprise edition MSSQL2005 for development. I tried to install MSSQL2005 sp1 and it is necessary to upgrade to the release version of SQL2005. Currently, I just got the release CD on hand, how can I upgrade the evaluation version to release version except uninstalling the eval and install with the release edition? Thanks in advance

You can "Upgrade" from Eval to the release version by launching setup from the CD. Setup will find the existing eval instance inform you that you can upgrade the instance.

jeff.

Saturday, February 25, 2012

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech Znaniecki
Is SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegro ups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech ZnanieckiIs SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegroups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSSQL Server 2005 Not Reporting Errors to Windows Event Log

Hello All,

I just performed a fresh install of MSSQL 2005 Server Developer Edition on my XPSP2 machine along with MSSQL 2005 SP1 and I noticed that errors are not being reported in the Windows Event Viewer. Is there a way to enable/disable logging here?

I need to view these logs because when the tasks > 'copy database' task fails it submits its error in the Windows Event Log however since I reinstalled MSSQL 2005 these log entries don't appear here.

thanks in advance.

Hi,

if you are using a job for this you can switch the Windows event logging on.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Its not a job. I just manually select the task from Management Studio. In the last installation performing this task created log entries in the windows event log but for some reason they aren't appearing now.

|||

Hi:

The main log for SQL Server 2005 installation has changed, and placed in the following location:

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

For more information, please refer to the following MSDN reference.

http://msdn2.microsoft.com/en-us/library/ms143702.aspx

Hope this helps. :-)

Thanks.

|||

Interesting... I wonder why events don't show up in the Windows Event Log anymore? Especially since MSSQL 2005 specifically says that it will make log entries in the Windows Event Log in the Copy Database task wizard.

|||

Hi,

If the Severity Level is 19 or Higher then only it will be logged in the Windows Event Log.

HTH

Hemantgiri S. Goswami

Friday, March 30, 2012

Multi Server Jobs

Multi Server Jobs

Wednesday, March 28, 2012

Multi Server Jobs

Wednesday, March 21, 2012

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

MSSQLServerOLAPService crashing frequently

Friday, March 9, 2012

MSSQL2K and WIN2K3 SP1

MSSQL2K and WIN2K3 SP1

MSSQL2K and WIN2K3 SP1

MSSQL2005 SP1 setup

Saturday, February 25, 2012

MSsql Standard connect error

MSsql Standard connect error

MSSQL Server 2005 Not Reporting Errors to Windows Event Log

MSSQL Mistake

Blog Archive

About Me