Error 207: standard

Showing posts with label standard. Show all posts

Thursday, March 29, 2012

Error 913

OS: Win2K3 x64 SP2
SQL: Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02
Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on
Windows NT 5.2 (Build 3790: Service Pack 2)
I changed a database to single user, and the machine hung for over two
hours, to I stopped the program. Now I get an error saying 'Could not find
database ID x. Database may not be activated yet ot may be in transition.
Error: 913.
Does anyone have an idea of how to fix this?right click database, tasks, take offline. Then same thing only bring
online.
"Daniel Rimmelzwaan [MVP - Dynamics NAV]"
<daniel.rimmelzwaan@.nospam.tectura.com> wrote in message
news:ujMVnOBsHHA.3432@.TK2MSFTNGP02.phx.gbl...
> OS: Win2K3 x64 SP2
> SQL: Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02
> Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit)
> on Windows NT 5.2 (Build 3790: Service Pack 2)
> I changed a database to single user, and the machine hung for over two
> hours, to I stopped the program. Now I get an error saying 'Could not find
> database ID x. Database may not be activated yet ot may be in transition.
> Error: 913.
> Does anyone have an idea of how to fix this?
>|||Hi
"Daniel Rimmelzwaan [MVP - Dynamics NAV]"
<daniel.rimmelzwaan@.nospam.tectura.com> wrote in message
news:ujMVnOBsHHA.3432@.TK2MSFTNGP02.phx.gbl...
> OS: Win2K3 x64 SP2
> SQL: Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02
> Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit)
> on Windows NT 5.2 (Build 3790: Service Pack 2)
> I changed a database to single user, and the machine hung for over two
> hours, to I stopped the program. Now I get an error saying 'Could not find
> database ID x. Database may not be activated yet ot may be in transition.
> Error: 913.
> Does anyone have an idea of how to fix this?
My assumption is that stopping the process did not release the connection in
which case,
if you executed sp_who from a SSIS query window you may see one process
using the database, issue a KILL on the spid would allow a different process
to use the database.
Johnsql

Error 913

Sunday, February 26, 2012

Error 3449 SQL Server shutdown

SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.

I have had two production servers shut down this week due to Error 3449: SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

Previous to the shutdown I received multiple Error 3314 & 602: Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

Also, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.

I am getting the same error message except ofr the last one (, Error 9001: During undoing of a logged operation in database 'msdb', an error occurred at log record ID (838:208:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.)

How did you solve this problem,? and why this error showing up?

Thanks

|||

Alright Chaps,

There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:

http://support.microsoft.com/kb/916086

regards

Jag

Error 3449 SQL Server shutdown

SQL Server 2005 X64 Standard running on Windows Server 2003 X64 Htper Threaded Quad processors with 16 GB RAM.

Does anyone have an idea why I have begun receiving these error messages? I have run dbcc checkdb on Master and msdb and they do not show any problems.

How did you solve this problem,? and why this error showing up?

Thanks

|||

Alright Chaps,

There is a hotfix available from microsoft for the errors that you guys are getting. Please check the below link:

http://support.microsoft.com/kb/916086

regards

Jag

Friday, February 24, 2012

Error 29503 - SQL Server 2005 DB Engine install Fails

Hi, I've just tried to install SQL Server 2005 Standard and I'm getting an error that I can't find any information on. In the log, I find Error 29503. A message after it indicates that it couldn't start the server.

In the setup, I'm getting the error when it is trying to start SQL Server and it can't. I've tried to go to the services window to manually start the engine, but immediately after it starts, it shutsdown again.

I read the help file in MSDN that is also included in the error details regarding manually starting the service. It indicates to use the Configuration Manager, but at this point in the installation, the instance of the server is not visible in the manager.

One other thing of interest is that I did have SQL Server 2000 installed, but I removed the installation. There was a SQL Server Native client left in my add/remove programs that I didn't uninstall because I wasn't sure of where it came from.

Any help with this issue would be appreciated.Sorry I can't solve your issue, but I can join your pain ;-(
I tried to install SQL 2005 Standard on my machine and got a similar problem. Below is an excerpt from the log file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Product : Microsoft SQL Server 2005

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_ MYMACHINE _SQL.log

Last Action : InstallFinalize

Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{ODBC Driver Manager} Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Error Number : 29515

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Anyone out there from Microsoft ready to help? PLEASE.

|||On an additional note, I've tried to install SQL Server Express as well and it is giving me the same error. I have also tried removing everything related to SQL (including the SQL native client) and I am still running into a brick wall.

Does anyone know what this error indicates? The weird thing is that it looks like it installs fine, it just can't start the DB engine. Is it doing some wierd check that wouldn't allow it to start? If so, I can't imagine what it would be.

Again, any help on this issue would be greatly appreciated.|||We've seen this happen in two particular cases:

1) There was an older version of SQL Native Access Client (SNAC) on the machine
There was a bug in an earlier (early Pre-RTM) build of SNAC that prevented it from being upgraded. The solution here is to completely remove SQL and SNAC from the machine and rerun setup. SNAC will have a separate entry in Add/Remove Programs so be sure to remove it doing so after you've removed all of the other SQL Components.

2) Norton Firewall 2004 on Windows 2003
This is a problem with Norton that causes problems starting the SQL DB Engine service. It's been reported to Symantec but I'm not aware of any fix for it. My understanding is this only happens on Windows 2003 which is not a supported platform for Norton Firewall 2004. Norton Firewall 2006 doesn't support Windows 2003 either. The work around is to disable or remove Norton Firewall from the system prior to installing SQL Server. This is not an issue on non Windows 2003 platforms.

Dan|||Thanks for that information. I'll look at my machine. I'm pretty sure I don't have a problem with the first issue, however I have just recently upgraded my machine from Norton Internet Security 2004 to 2006 and this includes their firewall.

I will attempt to disable it and reinstall.|||Hi,

I managed to install my SQL2005 standard after about 10 tries :-(
Here are the things I tried:
Remove everything that was installed for SQL2005,
Then install it piece by piece, that is I started with the native client, no tools or books.
When this was succesfull, I installed the DB services, then the tools and at the very end the books.

However, also this procedure did not work the first time. It seems that everytime I removed it (about 4 times) it cleaned up a little better.

Finally it worked. After that I installed VS studio 2005 w/o the SQL 2005 express and all works fine.

It does however, leaves me with an uneasy feeling because I don't know why all this happened.

I suppose that Microsoft will have an update for SQL 2005 soon to fix all these issues with installation.

Good luck to all of you.
Gerhard|||Hello,

I experienced the same error while installing SQL Server 2005 Express, but found a different solution. I must say, however, that your post kept me from loosing all hope and giving up.

You will find my post in this group with the title
Possible Fix SQL Server 2005 Express Install Errors 29503 or 1067

SQL Wizard

|||Thanks for your response SQL Wizard. I'll try that and let you know how it goes. By the way, I was doing everything you mentioned except for starting the service as local service. I was attempting to install using local system.

Dan,
I tried disabling Norton Internet Security and I still had the same problems. However, this time, I came across some errors in my event logs. I can't get them right now, but I'll post them later today when I get can.|||John I have the same problem with an SQL Server Standard installation. Have you trobleshoot it?|||Please search for the post above by SQL Wizard. That helped me out with my issue.

Error 29503 - SQL Server 2005 DB Engine install Fails

Product : Microsoft SQL Server 2005

Product Version : 9.00.1399.06

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_ MYMACHINE _SQL.log

Last Action : InstallFinalize

Error Number : 29515

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Anyone out there from Microsoft ready to help? PLEASE.

Again, any help on this issue would be greatly appreciated.|||We've seen this happen in two particular cases:

I will attempt to disable it and reinstall.|||Hi,

However, also this procedure did not work the first time. It seems that everytime I removed it (about 4 times) it cleaned up a little better.

Finally it worked. After that I installed VS studio 2005 w/o the SQL 2005 express and all works fine.

It does however, leaves me with an uneasy feeling because I don't know why all this happened.

I suppose that Microsoft will have an update for SQL 2005 soon to fix all these issues with installation.

Good luck to all of you.
Gerhard|||Hello,

I experienced the same error while installing SQL Server 2005 Express, but found a different solution. I must say, however, that your post kept me from loosing all hope and giving up.

You will find my post in this group with the title
Possible Fix SQL Server 2005 Express Install Errors 29503 or 1067

SQL Wizard

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Hi,

I've been trying to fix this error for two days! and I really need the advice of the experts please!

Computer XP Professional Service Pack2, SQL Server 2005 and Visual Studio 2005 (both Standard Edition)

ConnectionString:

connectionStrings>

</connectionStrings>

C# code

string

myConnectionString = ConfigurationManager.ConnectionStrings["MyConnectionDB"].ConnectionString;

SqlConnection myConnection = new SqlConnection(myConnectionString);

myConnection.Open();

Here I get the error: {"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}

What I checked so far:

ServerName and Instance NameOK!Database, Username and passwordOK!SQL Server 2005 Surface Are Configuration - Remote connections using both TCP/IP and Pipe NamesOK!SQL Configuration Manager - Protocolos Enabled (TCP/IP, Pipes, shared)OK!SQL Server Browse running and activeOK!

Am I missing something? I never had this problem with SQL Server 2000 and Visual Studio 2003.

Thanks in advance for any help or suggestion you can give me.

Sasa

Nevermind, I reinstalled again .NET 2.0 and it works. I can't believe that I expend two days thinking it was a configuration setting

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Hi,

I've been trying to fix this error for two days! and I really need the advice of the experts please!

Computer XP Professional Service Pack2, SQL Server 2005 and Visual Studio 2005 (both Standard Edition)

ConnectionString:

</connectionStrings>

C# code

string

myConnectionString = ConfigurationManager.ConnectionStrings["MyConnectionDB"].ConnectionString;

SqlConnection myConnection = new SqlConnection(myConnectionString);

myConnection.Open();

What I checked so far:

ServerName and Instance Name OK! Database, Username and password OK! SQL Server 2005 Surface Are Configuration - Remote connections using both TCP/IP and Pipe Names OK! SQL Configuration Manager - Protocolos Enabled (TCP/IP, Pipes, shared) OK! SQL Server Browse running and active OK! No Firewall

Am I missing something? I never had this problem with SQL Server 2000 and Visual Studio 2003.

Thanks in advance for any help or suggestion you can give me.

Sasa

Hi there,

I have managed to replicate your problem on my machine. I also managed to resolve it by removing the brackets, i.e. the "(" and ")", from the name of your data source.

So, your connection string would be:

Before removing the brackets I got the same errors you were getting. After removing the brackets I could connect successfully.

Have a go at removing the brackets and see if that works for you.

Hope this helps, but sorry if it doesn't
|||

You are my hero!!!

I don't know how many times I checked that connectionstring, I was thinking it was any configuration setting.

Thanks a lot

|||Where do I go to remove the "()"?|||

you need to open de Web.config file in the <connectionStrings> section

Sasa

|||

I thought it is a joke to remove the "()" but it works, You are my hero.

barak

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Hi,

I've been trying to fix this error for two days! and I really need the advice of the experts please!

Computer XP Professional Service Pack2, SQL Server 2005 and Visual Studio 2005 (both Standard Edition)

ConnectionString:

</connectionStrings>

C# code

string

myConnectionString = ConfigurationManager.ConnectionStrings["MyConnectionDB"].ConnectionString;

SqlConnection myConnection = new SqlConnection(myConnectionString);

myConnection.Open();

What I checked so far:

Am I missing something? I never had this problem with SQL Server 2000 and Visual Studio 2003.

Thanks in advance for any help or suggestion you can give me.

Sasa

Hi there,

I have managed to replicate your problem on my machine. I also managed to resolve it by removing the brackets, i.e. the "(" and ")", from the name of your data source.

So, your connection string would be:

Before removing the brackets I got the same errors you were getting. After removing the brackets I could connect successfully.

Have a go at removing the brackets and see if that works for you.

Hope this helps, but sorry if it doesn't
|||

You are my hero!!!

I don't know how many times I checked that connectionstring, I was thinking it was any configuration setting.

Thanks a lot

|||Where do I go to remove the "()"?|||

you need to open de Web.config file in the <connectionStrings> section

Sasa

|||

I thought it is a joke to remove the "()" but it works, You are my hero.

barak

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Hi,

I've been trying to fix this error for two days! and I really need the advice of the experts please!

Computer XP Professional Service Pack2, SQL Server 2005 and Visual Studio 2005 (both Standard Edition)

ConnectionString:

</connectionStrings>

C# code

string

myConnectionString = ConfigurationManager.ConnectionStrings["MyConnectionDB"].ConnectionString;

SqlConnection myConnection = new SqlConnection(myConnectionString);

myConnection.Open();

What I checked so far:

Am I missing something? I never had this problem with SQL Server 2000 and Visual Studio 2003.

Thanks in advance for any help or suggestion you can give me.

Sasa

Hi there,

I have managed to replicate your problem on my machine. I also managed to resolve it by removing the brackets, i.e. the "(" and ")", from the name of your data source.

So, your connection string would be:

Before removing the brackets I got the same errors you were getting. After removing the brackets I could connect successfully.

Have a go at removing the brackets and see if that works for you.

Hope this helps, but sorry if it doesn't
|||

You are my hero!!!

I don't know how many times I checked that connectionstring, I was thinking it was any configuration setting.

Thanks a lot

|||Where do I go to remove the "()"?|||

you need to open de Web.config file in the <connectionStrings> section

Sasa

|||

I thought it is a joke to remove the "()" but it works, You are my hero.

barak

Wednesday, February 15, 2012

Error 1934 Severity 16 State 1

SQL Server 2000 Standard Sp3. on Windows 2003
What is Error 1934.
I can't find documentaiton on this anywhere. There's only one article in KB
in relation to merge replication. And other stuff on the web about ANSI
settings and indexed views (which I'm not using).
I get these errors in different contexts.
Here's one:
Profiler screenshot
http://www.vinnychi.com/vince/images/sql.jpg
This is a stored procedure that SQL Agent is running from a job. When i run
it this way, I get the 1934 error. If I run it from Query Analyzer I get no
error, and it runs to completion.
SP:
CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
AS
exec UTIL_DEFRAG
RETURN
======== UTIL_DEFRAG is:
CREATE procedure UTIL_DEFRAG
AS
TRUNCATE TABLE BLCSO
TRUNCATE TABLE IBFF_BOL_Temp
TRUNCATE TABLE IBFF_Container_Temp
TRUNCATE TABLE IBFFContainerImportPhase2
TRUNCATE TABLE JobOrderDoor_Temp
TRUNCATE TABLE JobOrderDoorContainer_Temp
TRUNCATE TABLE JobOrderITM_Temp
TRUNCATE TABLE JobOrderITMContainer_Temp
TRUNCATE TABLE JTQ510
TRUNCATE TABLE JTQ520
TRUNCATE TABLE NAIBFF
TRUNCATE TABLE NAIBFF_DeleteTable
TRUNCATE TABLE SpecialRequirementMilestone
declare @.tablename nvarchar(125)
declare cur CURSOR
FORWARD_ONLY
STATIC
READ_ONLY
FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
and name not like 'conflict_%' and name not like 'dt%' and name not like
'MS%' and name not like 'sys%'
order by name
open cur
fetch next from cur
into @.tablename
while @.@.fetch_status = 0
BEGIN
PRINT 'REINDEXING ' + @.tablename
dbcc dbreindex (@.tablename)
fetch next from cur
into @.tablename
END
CLOSE cur
DEALLOCATE curI wouldn't rule out the ANSI settings. This issue has come
up before. SQL Agent and Query Analyzer use different set
options/ansi settings when they connect to SQL Server.
Whatever the set option errors you are seeing as missing,
add to your job script and make sure they are just before
the calling of your stored procedures.
-Sue
On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:
>SQL Server 2000 Standard Sp3. on Windows 2003
>What is Error 1934.
>I can't find documentaiton on this anywhere. There's only one article in KB
>in relation to merge replication. And other stuff on the web about ANSI
>settings and indexed views (which I'm not using).
>I get these errors in different contexts.
>Here's one:
>Profiler screenshot
>http://www.vinnychi.com/vince/images/sql.jpg
>This is a stored procedure that SQL Agent is running from a job. When i run
>it this way, I get the 1934 error. If I run it from Query Analyzer I get no
>error, and it runs to completion.
>SP:
>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>AS
>exec UTIL_DEFRAG
> RETURN
>
>========>UTIL_DEFRAG is:
>CREATE procedure UTIL_DEFRAG
>AS
>TRUNCATE TABLE BLCSO
>TRUNCATE TABLE IBFF_BOL_Temp
>TRUNCATE TABLE IBFF_Container_Temp
>TRUNCATE TABLE IBFFContainerImportPhase2
>TRUNCATE TABLE JobOrderDoor_Temp
>TRUNCATE TABLE JobOrderDoorContainer_Temp
>TRUNCATE TABLE JobOrderITM_Temp
>TRUNCATE TABLE JobOrderITMContainer_Temp
>TRUNCATE TABLE JTQ510
>TRUNCATE TABLE JTQ520
>TRUNCATE TABLE NAIBFF
>TRUNCATE TABLE NAIBFF_DeleteTable
>TRUNCATE TABLE SpecialRequirementMilestone
>declare @.tablename nvarchar(125)
>declare cur CURSOR
>FORWARD_ONLY
>STATIC
>READ_ONLY
>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>and name not like 'conflict_%' and name not like 'dt%' and name not like
>'MS%' and name not like 'sys%'
>order by name
>open cur
>fetch next from cur
>into @.tablename
>while @.@.fetch_status = 0
>BEGIN
>PRINT 'REINDEXING ' + @.tablename
>dbcc dbreindex (@.tablename)
>fetch next from cur
>into @.tablename
>END
>CLOSE cur
>DEALLOCATE cur
>|||It ended up being
Set ArithAbort ON
needed to be set.
How come this error isn't documented anywhere "official?
I'm also gettinga lot of error 1933 and 1935
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>I wouldn't rule out the ANSI settings. This issue has come
> up before. SQL Agent and Query Analyzer use different set
> options/ansi settings when they connect to SQL Server.
> Whatever the set option errors you are seeing as missing,
> add to your job script and make sure they are just before
> the calling of your stored procedures.
> -Sue
> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>|||Based on your errors, I would guess that you have computed
columns. ANSI settings and computed columns is addressed in
books online under the topics:
SET Options That Affect Results
Creating Indexes on Computed Columns
The Arithabort setting is addressed in the books online
topic Create Index
The article does mention the following:
It is strongly recommended that the ARITHABORT user option
be set server-wide to ON as soon as the first indexed view
or index on a computed column is created in any database on
the server.
You can also find related information in the following:
http://www.microsoft.com/sql/techinfo/tips/development/july2.asp
-Sue
On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:
>It ended up being
>Set ArithAbort ON
>needed to be set.
>
>How come this error isn't documented anywhere "official?
>I'm also gettinga lot of error 1933 and 1935
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>>I wouldn't rule out the ANSI settings. This issue has come
>> up before. SQL Agent and Query Analyzer use different set
>> options/ansi settings when they connect to SQL Server.
>> Whatever the set option errors you are seeing as missing,
>> add to your job script and make sure they are just before
>> the calling of your stored procedures.
>> -Sue
>> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
>> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>>
>|||Sue: Thanks for your leads. A large part of the problem was ArithAbort.
Thank you very much.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4c6fv0l327hq7dm20npbajt0vv2nsf10u1@.4ax.com...
> Based on your errors, I would guess that you have computed
> columns. ANSI settings and computed columns is addressed in
> books online under the topics:
> SET Options That Affect Results
> Creating Indexes on Computed Columns
> The Arithabort setting is addressed in the books online
> topic Create Index
> The article does mention the following:
> It is strongly recommended that the ARITHABORT user option
> be set server-wide to ON as soon as the first indexed view
> or index on a computed column is created in any database on
> the server.
> You can also find related information in the following:
> http://www.microsoft.com/sql/techinfo/tips/development/july2.asp
> -Sue
> On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>>It ended up being
>>Set ArithAbort ON
>>needed to be set.
>>
>>How come this error isn't documented anywhere "official?
>>I'm also gettinga lot of error 1933 and 1935
>>
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>>I wouldn't rule out the ANSI settings. This issue has come
>> up before. SQL Agent and Query Analyzer use different set
>> options/ansi settings when they connect to SQL Server.
>> Whatever the set option errors you are seeing as missing,
>> add to your job script and make sure they are just before
>> the calling of your stored procedures.
>> -Sue
>> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
>> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article
>>in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>>
>

Thursday, March 29, 2012

Error 913

Error 913

Error 913

Sunday, February 26, 2012

Error 3449 SQL Server shutdown

Error 3449 SQL Server shutdown

Friday, February 24, 2012

Error 29503 - SQL Server 2005 DB Engine install Fails

Error 29503 - SQL Server 2005 DB Engine install Fails

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Error 26: When connecting to Local Server with SQL Server 2005 Standard Edition

Wednesday, February 15, 2012

Error 1934 Severity 16 State 1

Error 1934 Severity 16 State 1

Error 1934 Severity 16 State 1

Error 207

Blog Archive

About Me