error pending file

I've uninstall my previous sql2000 developer edition with leave some dll file undeleted.

once I tried to reinstall the sqlserver, the installation setup stop the process with message: A previous installation created pending file operations on the installation machine.
you must restart the computer before running setup.

I fail in continueing setup although i've restart the pc.

What should i do to handle this?

Regards,

BHT

Hhh.... please someone help me...

I don't want to reinstall the O/S as previously i've done. headache and waisting my days.

Regards,

BHT

http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b312995&Product=sql

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Jens,

At last I saved. Thank you for your help.

Trully it is very suffer when become a begginer. (

Regards,

BHT

Error on INSERT Query

I want to insert "489d68bf-baa1-415d-94c7-a8e56b-609c61" in a column in sql
server . The data type of this column is varchar (100). i am getting the
folloing error - incorrect syntax near '68bf'. I think it is not accepting
the '-'. How can i get a work around for the '-' so that the above values
gets inserted successfully.
Vijay,
can you post some sample DDL for the table, as well as the insert statement
that's throwing the error? that value should be legal in the column.
David
"Vijay" <Vijay@.discussions.microsoft.com> wrote in message
news:233A3D0E-1A73-424A-BB00-608D9676247B@.microsoft.com...
>I want to insert "489d68bf-baa1-415d-94c7-a8e56b-609c61" in a column in sql
> server . The data type of this column is varchar (100). i am getting the
> folloing error - incorrect syntax near '68bf'. I think it is not accepting
> the '-'. How can i get a work around for the '-' so that the above values
> gets inserted successfully.
|||Are you trying to insert via a stored procedure, or a simple insert
statement?
Try delimiting the string with single quotes. As in:
INSERT INTO YourTable (YourColumn) VALUES
('489d68bf-baa1-415d-94c7-a8e56b-609c61')
Replace YourTable and YourColumn with whatever is appropriate
Keith Kratochvil
"Vijay" <Vijay@.discussions.microsoft.com> wrote in message
news:233A3D0E-1A73-424A-BB00-608D9676247B@.microsoft.com...
>I want to insert "489d68bf-baa1-415d-94c7-a8e56b-609c61" in a column in sql
> server . The data type of this column is varchar (100). i am getting the
> folloing error - incorrect syntax near '68bf'. I think it is not accepting
> the '-'. How can i get a work around for the '-' so that the above values
> gets inserted successfully.
sql

ERROR on atach MDF file!

Code Snippet

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'MS-DB'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.
During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Could not open new database 'aws'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 3456)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3456&LinkId=20476

BUTTONS:

OK

HELP ME!!

try to attach only the mdf file of your database.

run a command like this :

create database yourdb on (name =yourdb, filename='C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\yourmdffile.mdf') for attach

If it doesn't work do what your message say

|||

Don't work...

The message....

Code Snippet

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'aws'. CREATE DATABASE is aborted.

Msg 3456, Level 21, State 1, Line 1

Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.

Msg 3313, Level 21, State 2, Line 1

During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.

|||

A last try :

when i said to attach only the mdf file i thaught to following thing:

don't use the log file when making the operation of attaching (put only de mdf file in the folder); so , SQL should recreate the log file.

|||

Ok,

I try this...

and

Code Snippet

File activation failure. The physical file name "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\aws_log.ldf" may be incorrect.

The log cannot be rebuilt because the database was not cleanly shut down.

Msg 1813, Level 16, State 2, Line 1

Could not open new database 'aws'. CREATE DATABASE is aborted.

|||

If you have not a backup try to recover with third party. It say :

"Selective recovery means repairing only those transactions and objects that are damaged" Maybe they can help you.

To the other part you have to review the procedures of using servers in your organization (using UPS etc) because "the database was not cleanly shutdown"

|||

As your db was not cleanly shut down you can perform as below

(a) Create a database with the same name in another directory as the one you're trying to attach
(b) Re-create all filesgroups and files as necessary
(c) Shutdown the server
(d) Swap in the old mdf file and any ndf files
(e) Bring up the server and let the database attempt to be recovered and then go into suspect
(f) Put the database in single-user mode.
(g) Run DBCC CHECKDB (dbname, REPAIR_ALLOW_DATA_LOSS) which will rebuild the log and run full repair
(h) Return database to online, multi-user mode.

|||

As your db was not cleanly shut down you can perform as below

ok(a) Create a database with the same name in another directory as the one you're trying to attach
ok(b) Re-create all filesgroups and files as necessary
ok(c) Shutdown the server
ok(d) Swap in the old mdf file and any ndf files
ok(e) Bring up the server and let the database attempt to be recovered and then go into suspect
(f) Put the database in single-user mode.

Well

I cant put the database in single-user mode, i receive this message whend i did this commands...

Commands:

Use aws

go

sp_dboption 'aws', 'dbo use only', false

go

sp_dboption 'aws','single_user', true

go

dbcc checkdb ('aws',repair_allow_data_loss)

aws is my DB

Message:

Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
sp_dboption command failed.
Msg 3456, Level 21, State 1, Line 1
Could not redo log record (805:390:13), for transaction ID (0:55765), on page (1:1061), database 'aws' (database ID 5). Page: LSN = (804:451:25), type = 2. Log: OpCode = 2, context 3, PrevPageLSN: (805:150:13). Restore from a backup of the database, or repair the database.
Msg 3313, Level 21, State 2, Line 1
During redoing of a logged operation in database 'aws', an error occurred at log record ID (805:390:13). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Msg 3414, Level 21, State 1, Line 1
An error occurred during recovery, preventing the database 'aws' (database ID 5) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

===================

Then i put the server in Single User mode and execute the command below: ( -m -c )

DBCC CHECKDB (aws, REPAIR_ALLOW_DATA_LOSS)

and receive this message:

Msg 926, Level 14, State 1, Line 1
Database 'aws' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

======

Well

The DB was atach again, but i cant recovery the data =(

Error messages upsizing from MSAccess database to SQLServer

I am trying to use SQLServer for the first time and I am trying to use the upsizing wizard on Access to get moved over to SQLServer. I am getting the following error messages:

Connection failed:

SQLState: '01000'

SQL Server Error: 2

[Microsoft][ODBC SQL Server][Shared Memory]ConnectionOpen (Connect()).

Connection failed:

SQLState: '08001'

SQLServer Error: 17

[Microsoft][ODBC SQL Server][Shared Memory]SQL Server does not exist or access denied.

Does anyone know how I should proceed? Any help would be appreciated.

Thanks

Which version of SQL Server are you using?

Does the following help

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

|||I am using SQL Server 2005 Express|||Did you try the steps in the link I provided?|||

I did all the steps and I got the following error message:

ODBC - call failed.

I also tried this: I wrote a new database that had only one table in it (no forms or queries) and a few records in that table. That test database did get upsized just fine. But when trying to upsize the database I really need, I still got the "ODBC - call failed" error message.

Do you have any recommendations.

Thanks

Mark

|||

http://support.microsoft.com/?scid=kb;en-us;303257&spid=2509&sid=49

HTH

Error messages upsizing from MSAccess database to SQLServer

I am trying to use SQLServer for the first time and I am trying to use the upsizing wizard on Access to get moved over to SQLServer. I am getting the following error messages:

Connection failed:

SQLState: '01000'

SQL Server Error: 2

[Microsoft][ODBC SQL Server][Shared Memory]ConnectionOpen (Connect()).

Connection failed:

SQLState: '08001'

SQLServer Error: 17

[Microsoft][ODBC SQL Server][Shared Memory]SQL Server does not exist or access denied.

Does anyone know how I should proceed? Any help would be appreciated.

Thanks

Which version of SQL Server are you using?

Does the following help

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

|||I am using SQL Server 2005 Express|||Did you try the steps in the link I provided?|||

I did all the steps and I got the following error message:

ODBC - call failed.

I also tried this: I wrote a new database that had only one table in it (no forms or queries) and a few records in that table. That test database did get upsized just fine. But when trying to upsize the database I really need, I still got the "ODBC - call failed" error message.

Do you have any recommendations.

Thanks

Mark

|||

http://support.microsoft.com/?scid=kb;en-us;303257&spid=2509&sid=49

HTH

Error Message on optimization plan in sqlserver 2000

I am not a SQL Server DBA but trying to figure this out,
The 'OptimizationsJob For Db Maintenance Plan' is failing with an
error -- When I checked the error message the index rebuild is failing
for one of the tables with an error of
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL Server Driver][SQL Server]DBCC failed because the following
SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
This table "t" exists in both our Dev and Prod Servers but I see this
issue only in the Prod server (the prod server has more data)...
I ran this query:
select * from sysobjects where type = 'V'
and objectproperty(id, 'IsIndexed') = 1
for any indexed views and returns null
What are my options?
TIA,
MagWhat about computed columns. If memory serves me, it is enough to have statistics on a computed
column for this error to happen.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message news:1175025577.736504.80620@.b75g2000hsg.googlegroups.com...
>I am not a SQL Server DBA but trying to figure this out,
> The 'OptimizationsJob For Db Maintenance Plan' is failing with an
> error -- When I checked the error message the index rebuild is failing
> for one of the tables with an error of
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
> [ODBC SQL Server Driver][SQL Server]DBCC failed because the following
> SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
> This table "t" exists in both our Dev and Prod Servers but I see this
> issue only in the Prod server (the prod server has more data)...
> I ran this query:
> select * from sysobjects where type = 'V'
> and objectproperty(id, 'IsIndexed') = 1
> for any indexed views and returns null
>
> What are my options?
>
> TIA,
> Mag
>|||On Mar 27, 3:09 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What about computed columns. If memory serves me, it is enough to have statistics on a computed
> column for this error to happen.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://www.solidqualitylearning.com/
>
> <aspirin...@.gmail.com> wrote in messagenews:1175025577.736504.80620@.b75g2000hsg.googlegroups.com...
> >I am not a SQL Server DBA but trying to figure this out,
> > The 'OptimizationsJob For Db Maintenance Plan' is failing with an
> > error -- When I checked the error message the index rebuild is failing
> > for one of the tables with an error of
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
> > [ODBC SQL Server Driver][SQL Server]DBCC failed because the following
> > SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> > This table "t" exists in both our Dev and Prod Servers but I see this
> > issue only in the Prod server (the prod server has more data)...
> > I ran this query:
> > select * from sysobjects where type = 'V'
> > and objectproperty(id, 'IsIndexed') = 1
> > for any indexed views and returns null
> > What are my options?
> > TIA,
> > Mag- Hide quoted text -
> - Show quoted text -
There is no computed columns on this table and how come the DEV/Test
instance is not showing the same exception...|||> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
That could have been because auto-statistics could have been created on the dev server but not the
prod server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message
news:1175029664.750939.316180@.p77g2000hsh.googlegroups.com...
> On Mar 27, 3:09 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> What about computed columns. If memory serves me, it is enough to have statistics on a computed
>> column for this error to happen.
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://www.solidqualitylearning.com/
>>
>> <aspirin...@.gmail.com> wrote in
>> messagenews:1175025577.736504.80620@.b75g2000hsg.googlegroups.com...
>> >I am not a SQL Server DBA but trying to figure this out,
>> > The 'OptimizationsJob For Db Maintenance Plan' is failing with an
>> > error -- When I checked the error message the index rebuild is failing
>> > for one of the tables with an error of
>> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
>> > [ODBC SQL Server Driver][SQL Server]DBCC failed because the following
>> > SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>> > This table "t" exists in both our Dev and Prod Servers but I see this
>> > issue only in the Prod server (the prod server has more data)...
>> > I ran this query:
>> > select * from sysobjects where type = 'V'
>> > and objectproperty(id, 'IsIndexed') = 1
>> > for any indexed views and returns null
>> > What are my options?
>> > TIA,
>> > Mag- Hide quoted text -
>> - Show quoted text -
> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
>

Error Message on optimization plan in sqlserver 2000

I am not a SQL Server DBA but trying to figure this out,
The 'OptimizationsJob For Db Maintenance Plan' is failing with an
error -- When I checked the error message the index rebuild is failing
for one of the tables with an error of
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL Server Driver][SQL Server]DBCC failed because the following
SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
This table "t" exists in both our Dev and Prod Servers but I see this
issue only in the Prod server (the prod server has more data)...
I ran this query:
select * from sysobjects where type = 'V'
and objectproperty(id, 'IsIndexed') = 1
for any indexed views and returns null
What are my options?
TIA,
Mag
What about computed columns. If memory serves me, it is enough to have statistics on a computed
column for this error to happen.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message news:1175025577.736504.80620@.b75g2000hsg.googlegro ups.com...
>I am not a SQL Server DBA but trying to figure this out,
> The 'OptimizationsJob For Db Maintenance Plan' is failing with an
> error -- When I checked the error message the index rebuild is failing
> for one of the tables with an error of
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
> [ODBC SQL Server Driver][SQL Server]DBCC failed because the following
> SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
> This table "t" exists in both our Dev and Prod Servers but I see this
> issue only in the Prod server (the prod server has more data)...
> I ran this query:
> select * from sysobjects where type = 'V'
> and objectproperty(id, 'IsIndexed') = 1
> for any indexed views and returns null
>
> What are my options?
>
> TIA,
> Mag
>
|||On Mar 27, 3:09 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What about computed columns. If memory serves me, it is enough to have statistics on a computed
> column for this error to happen.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://www.solidqualitylearning.com/
>
> <aspirin...@.gmail.com> wrote in messagenews:1175025577.736504.80620@.b75g2000hsg.go oglegroups.com...
>
>
>
>
> - Show quoted text -
There is no computed columns on this table and how come the DEV/Test
instance is not showing the same exception...
|||> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
That could have been because auto-statistics could have been created on the dev server but not the
prod server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message
news:1175029664.750939.316180@.p77g2000hsh.googlegr oups.com...
> On Mar 27, 3:09 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
>

Error Message on optimization plan in sqlserver 2000

I am not a SQL Server DBA but trying to figure this out,
The 'OptimizationsJob For Db Maintenance Plan' is failing with an
error -- When I checked the error message the index rebuild is failing
for one of the tables with an error of
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL Server Driver][SQL Server]DBCC failed because the followin
g
SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
This table "t" exists in both our Dev and Prod Servers but I see this
issue only in the Prod server (the prod server has more data)...
I ran this query:
select * from sysobjects where type = 'V'
and objectproperty(id, 'IsIndexed') = 1
for any indexed views and returns null
What are my options?
TIA,
MagWhat about computed columns. If memory serves me, it is enough to have stati
stics on a computed
column for this error to happen.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message news:1175025577.736504.80620@.b75g2000hsg.googlegroup
s.com...
>I am not a SQL Server DBA but trying to figure this out,
> The 'OptimizationsJob For Db Maintenance Plan' is failing with an
> error -- When I checked the error message the index rebuild is failing
> for one of the tables with an error of
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
> [ODBC SQL Server Driver][SQL Server]DBCC failed because the follow
ing
> SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
> This table "t" exists in both our Dev and Prod Servers but I see this
> issue only in the Prod server (the prod server has more data)...
> I ran this query:
> select * from sysobjects where type = 'V'
> and objectproperty(id, 'IsIndexed') = 1
> for any indexed views and returns null
>
> What are my options?
>
> TIA,
> Mag
>|||On Mar 27, 3:09 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What about computed columns. If memory serves me, it is enough to have sta
tistics on a computed
> column for this error to happen.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://www.solidqualitylearning.com/
>
> <aspirin...@.gmail.com> wrote in messagenews:1175025577.736504.80620@.b75g20
00hsg.googlegroups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -
There is no computed columns on this table and how come the DEV/Test
instance is not showing the same exception...|||> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
That could have been because auto-statistics could have been created on the
dev server but not the
prod server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message
news:1175029664.750939.316180@.p77g2000hsh.googlegroups.com...
> On Mar 27, 3:09 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
>