Showing posts with label log. Show all posts
Showing posts with label log. Show all posts

Wednesday, March 21, 2012

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Smile Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Smile Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

sql

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Smile Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Smile Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Smile Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MStudio Always "helps" me to connect to server

From database tree I want to open table trigger (I think this problem for all objects).

MStudio ALWAYS offer me to log on. Why?

I would like to open object from the SAME database, not other.

Can you provide more detail on exactly what you're trying to accomplish and the steps you're taking. Start with "I launch SSMS".

MSSQLService (MSDE) Not Re-Configured correctly

Hi all,

I have a question regarding restarting MS SQL Service under a different user, in other words, re-starting MSSQLService as a "Log on as" user instead of "Local System" account. By default MSSQLService starts as a local system account.

Now my problem is, that I install MSDE 2000 for my application. And I install it as a seperate instance with name "MyInstance". So after Install my service is called MSSQL$MyInstance.

so my process basically creates an NT user on the machine with administartors rights, stops the service, change the service configuration to my NT user account credentials and then starts it using scm. The whole process works fine on my machine running Win XP Pro v.2002 SP1. But it fails to work on Win XP Pro v2002 SP2.

on SP2 machine, service gets reconfigured because I can see the Log on as account being changed from Local System to MyNTUser. But when I try to start it every time error is "Log on failure". But when I go to service properties and change the Password to my NT users password service starts properly.

So i'm not sure what exactly is going on, because if reconfiguration process works for my machine, typically it should work on SP2 machine as well, as the notes on ChangeServiceConfig winapi method(requires Advapi32.dll) suggests that it will work for XP, NT and win 2002.

Does anyone has any idea why is that.

Code Snippets:

Create User:


DirectoryEntry AD = new DirectoryEntry("WinNT://" + machineName + ", computer");
DirectoryEntry newUser;
try {
newUser = AD.Children.Find(userName, "user");
DeleteNTUserAccount(userName);
newUser = AD.Children.Add(userName, "user");
}

catch (Exception) {
newUser = AD.Children.Add(userName, "user");
}
newUser.Invoke("Put", new object[] {"Description", userDescription});
newUser.Invoke("SetPassword", new object[] {userPWD});
newUser.CommitChanges();
DirectoryEntry group;
group = AD.Children.Find("Administrators", "group");
if (group != null)
group.Invoke("Add", new object[] {newUser.Path.ToString()});
group.Close();
newUser.Close();
AD.Close();


Code to Stop Service:


ServiceController sc;
TimeSpan timeout = new TimeSpan(0, 0, 60);
OperatingSystem os;
os = Environment.OSVersion;
if (os.Platform != PlatformID.Win32NT) {
txtInstallInfo.Text += "\r\n\tApplication is built only for NT, 2000, XP or Later";
this.Refresh();
retVal = false;
}
os = null;
sc = new ServiceController(serviceName);
if (sc.Status == ServiceControllerStatus.Running) {
if (sc.CanStop) {
txtInstallInfo.Text += "\r\n\tRestarting the " + serviceName + " service";
this.Refresh();
sc.Stop();
try {
sc.WaitForStatus(ServiceControllerStatus.Stopped, timeout);
txtInstallInfo.Text += "\r\n\t" + serviceName + " service stopped successfully";
this.Refresh();
}

catch(TimeoutException) {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service did not respond to the stop command in a timely fashion. Please Restart Installer at later time.";
this.Refresh();
retVal = false;
}
}
else {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service cannot be stopped. Please Wait make sure no application is running.";
this.Refresh();
retVal = false;
}
}
else {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service was not running.";
this.Refresh();
}
sc.Close();
sc = null;


Code to Re-Configure Service:


string UserName = "MyNTUser";
string UserPwd = "abc123";

int HandleToScm = OpenSCManager( null, null, ServiceControlAccessRights.AllAccess );

int HandleToSvc = OpenService( HandleToScm, ServiceName, ServiceSpecificAccessType.ChangeConfig );

if ( ChangeServiceConfig(
HandleToSvc,
ServiceControlType.OwnProcess,
ServiceStartType.AutoStart,
ServiceNoChange,
null,
null,
IntPtr.Zero,
null,
@.".\" + UserName,
UserPwd,
ServiceName ) ) {
CloseServiceHandle( HandleToSvc );
CloseServiceHandle( HandleToScm );
}


Code to Start Service:

scm -Action 1 -Service MSSQL$MyInstance -Silent 1 -SvcAccount .\MYNTUserAccount -SvcPwd MYNTAccountPassword

I've never seen this post before, yet it is dated May 2005. Bumping message...sql

MSSQLServerOLAPService crashing frequently

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

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

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

and...

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

etc.

System log at just before: (event id 7034)

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

Please contact Customer Support to report your problem.

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

|||

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

-Unexpected fatal error occurred. Attempting to restart server.

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

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

What are we missing at this point?

|||

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

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

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

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

|||

Bizarre - we're getting this same behavior.

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

Ever figure out what the deal was?

|||

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

MSSQLServerOLAPService crashing frequently

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

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

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

and...

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

etc.

System log at just before: (event id 7034)

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

Please contact Customer Support to report your problem.

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

|||

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

-Unexpected fatal error occurred. Attempting to restart server.

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

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

What are we missing at this point?

|||

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

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

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

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

|||

Bizarre - we're getting this same behavior.

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

Ever figure out what the deal was?

|||

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

sql

MSSQLServerOLAPService crashing frequently

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

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

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

and...

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

etc.

System log at just before: (event id 7034)

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

Please contact Customer Support to report your problem.

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

|||

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

-Unexpected fatal error occurred. Attempting to restart server.

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

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

What are we missing at this point?

|||

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

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

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

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

|||

Bizarre - we're getting this same behavior.

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

Ever figure out what the deal was?

|||

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

|||

Hi,

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

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

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

Thanks,

Ricardo Sada

|||

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

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

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

|||

Thanks Jesee

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

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

MSSQLServerOLAPService crashing frequently

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

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

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

and...

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

etc.

System log at just before: (event id 7034)

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

Please contact Customer Support to report your problem.

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

|||

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

-Unexpected fatal error occurred. Attempting to restart server.

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

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

What are we missing at this point?

|||

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

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

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

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

|||

Bizarre - we're getting this same behavior.

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

Ever figure out what the deal was?

|||

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

MSSQLServerOLAPService crashing frequently

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

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

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

and...

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

etc.

System log at just before: (event id 7034)

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

Please contact Customer Support to report your problem.

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

|||

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

-Unexpected fatal error occurred. Attempting to restart server.

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

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

What are we missing at this point?

|||

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

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

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

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

|||

Bizarre - we're getting this same behavior.

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

Ever figure out what the deal was?

|||

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

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.

Monday, March 19, 2012

MSSQLServerADHelper is problem?

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

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

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

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

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLSERVER service terminated unexpectedly

HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.
If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>