I have MS SQL 2000. I wanted to install SP3a and
encountered the following error :
FRunCM : Process <> generated Fatal exception c0000005.
Exception Access Violation - SQL Server is terminating
this process.
This happens during the running of the script
sp3_server_repl.sql. After that, I couldn't start the SQL
server anymore. I tried the solution given by Microsoft
but it didn't work.
SO, I decided to uninstall MS SQL and install again. But
after installing a fresh copy, I still get the same error
when the SQL Server tries to startup.
Please help, thank you.
PhilipHI Philip.
Check this article
814572 FIX: SQL Server Does Not Start and an Access Violation Occurs After
You
http://support.microsoft.com/?id=814572
If that does not help, download MDAC 2.7 SP1 from
http://www.microsoft.com/downloads/...00f2-cae7-493d-
b0f3-ae36c570ade8&languageid=f49e8428-7071-4979-8a67-3cffcb0c2524&displaylan
g=en
Reinstall MDAC 2.7 SP1 refresh and rerun SP3 installation.
Hope that helps.
Regards,
Gayathri Rau [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.|||As a safety, pls check the dasetup,log to make sure that mdac installed
successfully.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Showing posts with label generated. Show all posts
Showing posts with label generated. Show all posts
Monday, March 26, 2012
MS SQL server cannot start
I have MS SQL 2000. I wanted to install SP3a and
encountered the following error :
FRunCM : Process <> generated Fatal exception c0000005.
Exception Access Violation - SQL Server is terminating
this process.
This happens during the running of the script
sp3_server_repl.sql. After that, I couldn't start the SQL
server anymore. I tried the solution given by Microsoft
but it didn't work.
SO, I decided to uninstall MS SQL and install again. But
after installing a fresh copy, I still get the same error
when the SQL Server tries to startup.
Please help, thank you.
PhilipAs a safety, pls check the dasetup,log to make sure that mdac installed
successfully.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
encountered the following error :
FRunCM : Process <> generated Fatal exception c0000005.
Exception Access Violation - SQL Server is terminating
this process.
This happens during the running of the script
sp3_server_repl.sql. After that, I couldn't start the SQL
server anymore. I tried the solution given by Microsoft
but it didn't work.
SO, I decided to uninstall MS SQL and install again. But
after installing a fresh copy, I still get the same error
when the SQL Server tries to startup.
Please help, thank you.
PhilipAs a safety, pls check the dasetup,log to make sure that mdac installed
successfully.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
Monday, February 20, 2012
MS Scripting bug
SQL Server 2005
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?
You can report it at http://connect.microsoft.com
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?
You can report it at http://connect.microsoft.com
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
MS Scripting bug
SQL Server 2005
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?You can report it at http://connect.microsoft.com
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/.../1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?You can report it at http://connect.microsoft.com
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/.../1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
MS Scripting bug
SQL Server 2005
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?You can report it at http://connect.microsoft.com
--
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
(after both specifying 2000 in the scripting options and
setting database compatibility to 80) still used sys.objects and WITH
(IGNORE_DUP_KEY = OFF).
Since I wasn't expecting it, it was kind of a pain.
If this is, in fact, a bug, where would I report it?You can report it at http://connect.microsoft.com
--
Jason Massie
Web: http://statisticsio.com
RSS: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%233LgD74NIHA.3852@.TK2MSFTNGP06.phx.gbl...
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>|||Hi Jay,
I tried the same on SQL Server 2005 (Service Pack 2) and didnt find any
problem. Right click >>tasks>>generate scripts wizard generated the scripts
for indexes correctly for both 2000 and 2005.
Not sure whether in SP 2 MS resolved it.
Manu
"Jay" wrote:
> SQL Server 2005
> I generated some DDL in 2005 MS (Tasks->Scripting) the DDL it generated
> (after both specifying 2000 in the scripting options and
> setting database compatibility to 80) still used sys.objects and WITH
> (IGNORE_DUP_KEY = OFF).
> Since I wasn't expecting it, it was kind of a pain.
> If this is, in fact, a bug, where would I report it?
>
>
Subscribe to:
Posts (Atom)