Showing posts with label fix. Show all posts
Showing posts with label fix. Show all posts

Tuesday, March 27, 2012

Error 8905

I am getting a lot of corruption reports in my database and the performance
is down dramatically. The MS support site says I can fix this this a
checkdb repair with data loss. I run the repair over and over and no
change.
CHECKALLOC found 951 allocation errors and 0 consistency errors in database
'envision'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKALLOC (envision ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
We are on SQL 2000 service pack 4.
Any ideas'
Thanks!
RichardResolving Errors
If DBCC CHECKALLOC reports any errors, we recommend that you restore the
database from the database backup instead of running a repair. If a backup
does not exist, running a repair can correct the reported errors; however,
correcting the errors might require some pages, and therefore data, to be
deleted.
A repair can be performed in a user transaction. This allows for changes to
be rolled back. If changes are rolled back, the database will still contain
errors and must be restored from a backup. After the repairs finish, back up
the database.
Good luck!
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"Richard Douglass" wrote:

> I am getting a lot of corruption reports in my database and the performanc
e
> is down dramatically. The MS support site says I can fix this this a
> checkdb repair with data loss. I run the repair over and over and no
> change.
> CHECKALLOC found 951 allocation errors and 0 consistency errors in databas
e
> 'envision'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKALLOC (envision ).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> We are on SQL 2000 service pack 4.
> Any ideas'
> Thanks!
> Richard
>
>

Error 8905

I am getting a lot of corruption reports in my database and the performance
is down dramatically. The MS support site says I can fix this this a
checkdb repair with data loss. I run the repair over and over and no
change.
CHECKALLOC found 951 allocation errors and 0 consistency errors in database
'envision'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKALLOC (envision ).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
We are on SQL 2000 service pack 4.
Any ideas?
Thanks!
Richard
Resolving Errors
If DBCC CHECKALLOC reports any errors, we recommend that you restore the
database from the database backup instead of running a repair. If a backup
does not exist, running a repair can correct the reported errors; however,
correcting the errors might require some pages, and therefore data, to be
deleted.
A repair can be performed in a user transaction. This allows for changes to
be rolled back. If changes are rolled back, the database will still contain
errors and must be restored from a backup. After the repairs finish, back up
the database.
Good luck!
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"Richard Douglass" wrote:

> I am getting a lot of corruption reports in my database and the performance
> is down dramatically. The MS support site says I can fix this this a
> checkdb repair with data loss. I run the repair over and over and no
> change.
> CHECKALLOC found 951 allocation errors and 0 consistency errors in database
> 'envision'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKALLOC (envision ).
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> We are on SQL 2000 service pack 4.
> Any ideas?
> Thanks!
> Richard
>
>

Monday, March 26, 2012

Error 823 that I cant fix

Hi,

I am running SQL 2000 server for datawarehousing and I am getting the following error in the application log when I build large tables:

Error: 823, Severity: 24, State: 3
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x00000829618000 in file '<file name.mdf>'

I have run through MS Support and really haven't found helpful info on this. I don't know what process is locking the mdf file, but I don't beleive there are any server or even client side programs running against this datafile.

Any thoughts?

joeNot come across that error before, but I would try looking under the Managment section of your server in Enterprise Manager then Locks/Objects and see if you can spot an offending process. If there is one it may be worth trying to kill it.

Monday, March 19, 2012

Error 7105, how to fix it?

Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 7105, how to fix it?

Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Friday, February 24, 2012

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>

<add name="MyConnectionDB" connectionString="Data Source=(MyServer\SqlServer2005);Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA"providerName="System.Data.SqlClient" />

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

<add name="MyConnectionDB" connectionString="Data Source=(MyServer\SqlServer2005);Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

</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 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:

<add name="MyConnectionDB" connectionString="Data Source=MyServer\SqlServer2005;Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

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

|||

Hi

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>

<add name="MyConnectionDB" connectionString="Data Source=(MyServer\SqlServer2005);Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

</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 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:

<add name="MyConnectionDB" connectionString="Data Source=MyServer\SqlServer2005;Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

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

|||

Hi

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>

<add name="MyConnectionDB" connectionString="Data Source=(MyServer\SqlServer2005);Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

</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 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:

<add name="MyConnectionDB" connectionString="Data Source=MyServer\SqlServer2005;Initial Catalog=MyDB;User ID=sa;Password=PasswordforSA" providerName="System.Data.SqlClient" />

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

|||

Hi

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

barak

Wednesday, February 15, 2012

Error 208

Getting a lot of error 208 in trace. Does this mean
anything to health and performance of the box? Is this
something developers have to fix? Thnx.Hi,
Are you talking about the appearance of the message ' DBCC TRACEON 208,
server process ID (SPID)' in the SQL Server log file ?If so, this is the
logging of the 'MS Query Quoted Identifier' trace flag .This is for the DBA
to fix by using the start up parameter -T2505 with SQL Server.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"BH" <hubrian@.hotmail.com> wrote in message
news:027a01c37d4b$d2a36a50$a401280a@.phx.gbl...
> Getting a lot of error 208 in trace. Does this mean
> anything to health and performance of the box? Is this
> something developers have to fix? Thnx.