Error: Changed language to ...

When I try to open some tables in a database using QueryAnalyzer I receive
the following error:
"[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language to
bulgarian".
And in result the table is not opened.
Bulgarian is my native language by the way.
I made the following experiment :
I created a new table with the same definition as one of the problem tables.
Then I inserted all records from the problem table in the new one. Then I
had no problems opening the new table using QueryAnalyzer.
Do you have any idea what the problem is?
Thank you!What language is SQL Server set to? And was it the same as to when you
created the table the first time?
Yovan
"ggeshev" <ggeshev@.tonegan.bg> wrote in message
news:eVajZeDeDHA.2324@.TK2MSFTNGP11.phx.gbl...
> When I try to open some tables in a database using QueryAnalyzer I receive
> the following error:
> "[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language to
> bulgarian".
> And in result the table is not opened.
> Bulgarian is my native language by the way.
> I made the following experiment :
> I created a new table with the same definition as one of the problem
tables.
> Then I inserted all records from the problem table in the new one. Then I
> had no problems opening the new table using QueryAnalyzer.
> Do you have any idea what the problem is?
> Thank you!
>

error: Attempt to fetch logical page

Hi,
During an upgrade from sql server 6.5 to sql server 2000 I receive the
follwoing error and the upgrade process remains stuck until terminated
manually:
ODBC error 605 (HY000) Attempt to fetch logical page 1430280 in database
'nice_cls' belongs to object 'NICE_CLS_CALLS_0008', not to object
'NICE_CLS_CALLS_0007'.
I tried using dbcc checkdb and received the same error.
Is there any idea how to address this situation or how to delete the
specific page?
Thanks,
YanivHi Yaniv,
This error occurs when Microsoft SQL Server detects database corruption.
The second object specified in the text not to object '%.*ls' is probably
corrupt. Because this error can mask the existence of other errors, execute
DBCC CHECKDB to determine the extent of the damage.
I am assuming that the corruption is happening on your SQL Server 6.5
server. The best way to recover from corruption is to restore from your
good backup.
I hope this helps !!!
Thanks,
Fargham
Microsoft - SQL Server

error: Attempt to fetch logical page

Hi,
During an upgrade from sql server 6.5 to sql server 2000 I receive the
follwoing error and the upgrade process remains stuck until terminated
manually:
ODBC error 605 (HY000) Attempt to fetch logical page 1430280 in database
'nice_cls' belongs to object 'NICE_CLS_CALLS_0008', not to object
'NICE_CLS_CALLS_0007'.
I tried using dbcc checkdb and received the same error.
Is there any idea how to address this situation or how to delete the
specific page?
Thanks,
YanivHi Yaniv,
This error occurs when Microsoft® SQL Server detects database corruption.
The second object specified in the text not to object '%.*ls' is probably
corrupt. Because this error can mask the existence of other errors, execute
DBCC CHECKDB to determine the extent of the damage.
I am assuming that the corruption is happening on your SQL Server 6.5
server. The best way to recover from corruption is to restore from your
good backup.
I hope this helps !!!
Thanks,
Fargham
Microsoft - SQL Server

error: Attempt to fetch logical page

Hi,
During an upgrade from sql server 6.5 to sql server 2000 I receive the
follwoing error and the upgrade process remains stuck until terminated
manually:
ODBC error 605 (HY000) Attempt to fetch logical page 1430280 in database
'nice_cls' belongs to object 'NICE_CLS_CALLS_0008', not to object
'NICE_CLS_CALLS_0007'.
I tried using dbcc checkdb and received the same error.
Is there any idea how to address this situation or how to delete the
specific page?
Thanks,
Yaniv
Hi Yaniv,
This error occurs when Microsoft SQL Server detects database corruption.
The second object specified in the text not to object '%.*ls' is probably
corrupt. Because this error can mask the existence of other errors, execute
DBCC CHECKDB to determine the extent of the damage.
I am assuming that the corruption is happening on your SQL Server 6.5
server. The best way to recover from corruption is to restore from your
good backup.
I hope this helps !!!
Thanks,
Fargham
Microsoft - SQL Server

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

SQL Server 2005 9.0.3161 on Win 2k3 R2

I receive the following error:

"Error: 8624, Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."

I have traced this to an insert statement that executes as part of a stored procedure.

INSERT INTO ledger (journal__id, account__id,account_recv_info__id,amount)

VALUES (@.journal_id, @.acct_id, @.acct_recv_id, @.amount)

There is also an auto-increment column called id. There are FK contraints on all of the columns ending in "__id". I have found that if I remove the contraint on account__id the procedure will execute without error. None of the other constraints seem to make a difference. Of course I don't want to remove this key because it is important to the database integrity and should not be causing problems, but apparently it confuses the optimizer.

Also, the strange thing is that I can get the procedure to execute without error when I run it directly through management studio, but I receive the error when executing from .NET code or anything using ODBC (Access).

I'd suggest calling PSS. It does sound like a bug here.

|||

I ran into this exact problem today, and it turned out to be related to a catalog being inconsistent, when we performed a migration from a SQL 2000 server to a SQL 2005 server, by restoring a backup . There was a foreign key constraint that was not functioning correctly following the migration and that was causing the error to show up.

We had restored the SQL 2000 backup to a 2005 server, then changed the compatability mode from 80 to 90, then updated statistics. We did not however, run the DBCC following all of that. We had run tests prior to the migration, but this hadn't showed up as an issue until the day of the migration. As a matter of fact, we had run DBCC's on the SQL 2000 database and things were fine. We checked the backup file, and that was fine. The problem was in some part of the page migrations that happen within the engine itself. Maybe this was a page alignment issue, whereby a given catalog page was in a decent state for migration when we were testing, but changed it's alignment on a given page between the time we tested and the time that we migrated. Who know....that's just my speculation.

The error from running a simple insert statement looks like this:

Msg 8624, Level 16, State 1, Line 1

Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

The error from the DBCC CHECKDB looks like this:

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=238623893,key_index_id=3) of row (object_id=951674438) in sys.foreign_keys does not have a matching row (object_id=238623893,index_id=3) in sys.indexes.

CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

This lead us to the conclusion that we could drop the FK and recreate it, and have everything work. And, it did.

The moral of the story, like it's been said many times...run DBCC's after restores when going from SQL 2000 to SQL 2005.

Hope this helps someone else in the future.

-- Don

|||

I consulted tech support. It was finally classified as a bug. The database was in 80 compatibility and changing it to 90 made the problem go away. The other work around was to set arithabort on. This explained why it worked from management studio and not anywhere else. Apparently management studio has arithabort set to on by default. The following is the case closure confirmation from the MS engineer:

PROBLEM:

=======

An insert query to a table that has foreign key references cannot generate a plan with error 8624 when arithabort is set to be off.

Server: Msg 8624, Level 16, State 1, Line 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

AGREED UPON CRITERIA FOR RESOLUTION:

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

Investigate root cause

CAUSE:

=====

This issue appears to be related to the fact database compatibility is set to 80.I have filed a product bug for tracking purpose

RESOLUTION:

===========

Setting database compatibility to be 90 resolved the issue

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

SQL Server 2005 9.0.3161 on Win 2k3 R2

I receive the following error:

"Error: 8624, Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."

I have traced this to an insert statement that executes as part of a stored procedure.

INSERTINTO ledger (journal__id, account__id,account_recv_info__id,amount)

VALUES(@.journal_id, @.acct_id, @.acct_recv_id, @.amount)

There is also an auto-increment column called id. There are FK contraints on all of the columns ending in "__id". I have found that if I remove the contraint on account__id the procedure will execute without error. None of the other constraints seem to make a difference. Of course I don't want to remove this key because it is important to the database integrity and should not be causing problems, but apparently it confuses the optimizer.

Also, the strange thing is that I can get the procedure to execute without error when I run it directly through management studio, but I receive the error when executing from .NET code or anything using ODBC (Access).

I'd suggest calling PSS. It does sound like a bug here.

|||

I ran into this exact problem today, and it turned out to be related to a catalog being inconsistent, when we performed a migration from a SQL 2000 server to a SQL 2005 server, by restoring a backup . There was a foreign key constraint that was not functioning correctly following the migration and that was causing the error to show up.

We had restored the SQL 2000 backup to a 2005 server, then changed the compatability mode from 80 to 90, then updated statistics. We did not however, run the DBCC following all of that. We had run tests prior to the migration, but this hadn't showed up as an issue until the day of the migration. As a matter of fact, we had run DBCC's on the SQL 2000 database and things were fine. We checked the backup file, and that was fine. The problem was in some part of the page migrations that happen within the engine itself. Maybe this was a page alignment issue, whereby a given catalog page was in a decent state for migration when we were testing, but changed it's alignment on a given page between the time we tested and the time that we migrated. Who know....that's just my speculation.

The error from running a simple insert statement looks like this:

Msg 8624, Level 16, State 1, Line 1

Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

The error from the DBCC CHECKDB looks like this:

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=238623893,key_index_id=3) of row (object_id=951674438) in sys.foreign_keys does not have a matching row (object_id=238623893,index_id=3) in sys.indexes.

CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

This lead us to the conclusion that we could drop the FK and recreate it, and have everything work. And, it did.

The moral of the story, like it's been said many times...run DBCC's after restores when going from SQL 2000 to SQL 2005.

Hope this helps someone else in the future.

-- Don

|||

I consulted tech support. It was finally classified as a bug. The database was in 80 compatibility and changing it to 90 made the problem go away. The other work around was to set arithabort on. This explained why it worked from management studio and not anywhere else. Apparently management studio has arithabort set to on by default. The following is the case closure confirmation from the MS engineer:

PROBLEM:

=======

An insert query to a table that has foreign key references cannot generate a plan with error 8624 when arithabort is set to be off.

Server: Msg 8624, Level 16, State 1, Line 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

AGREED UPON CRITERIA FOR RESOLUTION:

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

Investigate root cause

CAUSE:

=====

This issue appears to be related to the fact database compatibility is set to 80.I have filed a product bug for tracking purpose

RESOLUTION:

===========

Setting database compatibility to be 90 resolved the issue

Error: 18456, Severity: 14, State: 16

I receive the following two errors in the sql log.
2006-10-16 08:47:06.33 Logon Error: 18456, Severity: 14, State: 16.
2006-10-16 08:47:06.33 Logon Login failed for user 'domain\user'.
[CLIENT: <named pipe>]
And the following in the windows event log.
Login failed for user 'domain\user'. [CLIENT: <named pipe>]
I have replaced my domain and user name with domain\user above. The problem
I am seeing is that if my service starts right after sql server 2005 says its
ready I get the following errors above. If I manually start my service
several seconds later I'm ok. Looking through the sql log it says the db and
everything is up and ready before the login actually takes place. However,
the tempdb does not get ready until after. Probably the cause of the problem.
Is there a reason why the tempdb is not made to be 'ready' before sql server
says its ready? Any workarounds other than putting in a delay?
Thanks,
Bruce
Hi,
are you sure that the service user has to appropiate rights on the
server to create the tempdb as a service user in the folder for the
temp db ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||It seems to be a timing issue. I can start sql and then quickly start my
service. My service waits for the sql service to be in the 'running' state
before continuing. However, eventhough SQL says its running (per the logs
too) the tempdb not being completed seems to be an issue.
So basically it appears to be a timing issue. SQL Server should be not be
saying its ready when it is still working on the tempdb.
sql

Error: 18456, Severity: 14, State: 16

I receive the following two errors in the sql log.
2006-10-16 08:47:06.33 Logon Error: 18456, Severity: 14, State: 16.
2006-10-16 08:47:06.33 Logon Login failed for user 'domain\user'.
[CLIENT: <named pipe>]
And the following in the windows event log.
Login failed for user 'domain\user'. [CLIENT: <named pipe>]
I have replaced my domain and user name with domain\user above. The problem
I am seeing is that if my service starts right after sql server 2005 says it
s
ready I get the following errors above. If I manually start my service
several seconds later I'm ok. Looking through the sql log it says the db and
everything is up and ready before the login actually takes place. However,
the tempdb does not get ready until after. Probably the cause of the problem
.
Is there a reason why the tempdb is not made to be 'ready' before sql server
says its ready? Any workarounds other than putting in a delay?
Thanks,
BruceHi,
are you sure that the service user has to appropiate rights on the
server to create the tempdb as a service user in the folder for the
temp db ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||It seems to be a timing issue. I can start sql and then quickly start my
service. My service waits for the sql service to be in the 'running' state
before continuing. However, eventhough SQL says its running (per the logs
too) the tempdb not being completed seems to be an issue.
So basically it appears to be a timing issue. SQL Server should be not be
saying its ready when it is still working on the tempdb.

Error: 18456, Severity: 14, State: 16

I receive the following two errors in the sql log.
2006-10-16 08:47:06.33 Logon Error: 18456, Severity: 14, State: 16.
2006-10-16 08:47:06.33 Logon Login failed for user 'domain\user'.
[CLIENT: <named pipe>]
And the following in the windows event log.
Login failed for user 'domain\user'. [CLIENT: <named pipe>]
I have replaced my domain and user name with domain\user above. The problem
I am seeing is that if my service starts right after sql server 2005 says its
ready I get the following errors above. If I manually start my service
several seconds later I'm ok. Looking through the sql log it says the db and
everything is up and ready before the login actually takes place. However,
the tempdb does not get ready until after. Probably the cause of the problem.
Is there a reason why the tempdb is not made to be 'ready' before sql server
says its ready? Any workarounds other than putting in a delay?
Thanks,
--
BruceHi,
are you sure that the service user has to appropiate rights on the
server to create the tempdb as a service user in the folder for the
temp db ?
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--|||It seems to be a timing issue. I can start sql and then quickly start my
service. My service waits for the sql service to be in the 'running' state
before continuing. However, eventhough SQL says its running (per the logs
too) the tempdb not being completed seems to be an issue.
So basically it appears to be a timing issue. SQL Server should be not be
saying its ready when it is still working on the tempdb.sql

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?
There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&l...om+sq l+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
[url]http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883[/u
rl]
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>sql

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>

Error: ""The transaction has exceeded the allotted time"

I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

XavierWas any one able to find an answer to this? I'm getting the exact same error. Thanks.

Originally posted by xfolch
I receive this error "The transaction has exceeded the allotted time" in a pop-up sometimes when I use DTS. This happens in an alleatory way, when I run a package, when I try to open a package or save it, and normally happens when the machine is very busy with another process. I'm running SQL Server 2000 with SP2, and Windows 2000 Advanced Server with SP2.

Thank you very much in advance,

Xavier|||I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||So what is the difference between the two: "Local Packages" and "Meta Data Services Packages".

Thanks.

Originally posted by xfolch
I solve it saving the packages as Local Packages instead of Meta Data Services Package: it never happens again|||It works the same, but it's store in a different format:

When you save a Data Transformation Services (DTS) package, you save all DTS connections, DTS tasks, DTS transformations, and workflow steps and preserve the graphical layout of these objects on the DTS Designer design sheet.

You can save a package to:

Microsoft SQL Server.
With this default save option, you can store a package as a SQL Server msdb table, allowing you to: store packages on any instances of SQL Server on your network; keep a convenient inventory of saved packages in SQL Server Enterprise Manager; and create, delete, and branch multiple package versions during the package development process.

SQL Server 2000 Meta Data Services.
With this save option, you can maintain historical information about the data manipulated by the package. However, Meta Data Services and the repository database must be installed and operational on your server. You can track the columns and tables that are used by the package as a source or destination. You also can use the data lineage feature to track which version of a package created a particular row. You can use these types of information for decision-support applications.

error with OpenRowSet

I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet,
but receive the following error:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
Connection Closed
here's the sql:
select *
into MyTable
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
any help is appreciated...I think it should work if file name is correct. Check whether the file
name is correct
Madhivanan|||Hi
Try this one
SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="d:\MyData.xls";
User ID=Admin;Password=;Extended properties=Excel 8.0')...Sheet1$
OR
Specify all columns
insert into MyTable (col1,col2)
SELECT col1,col2
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
".bill" <wSweetman@.ucsd.edu> wrote in message news:O3rAPZfHFHA.3612@.TK2MSFTN
GP09.phx.gbl...
I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet,
but receive the following error:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
Connection Closed
here's the sql:
select *
into MyTable
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
any help is appreciated...|||Do you have the file opened in Excel when you try to do this?
That would cause an error, but otherwise the syntax looks ok.
If the file C:\Default.xls exists and has a sheet named
Sheet1, it should work. Does the SQL Server
login have access to that file? What happens if you try
exec master..xp_cmdshell N'dir C:\*.xls'
Steve Kass
Drew University
.bill wrote:

>I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet,
but receive the following error:
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>Connection Closed
>here's the sql:
>select *
>into MyTable
>FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\Default.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
>any help is appreciated...
>
>|||Hi there,
Has anyone found an answer to this yet?
I tried:
insert into tblTestSql (RowNo,RecNo,LdUserName,
Code,LogIn,LogOut)
SELECT RowNo,RecNo,LdUserName,
Code,LogIn,LogOut
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\ReleaseTwo\LogInandOut.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
Which gives me
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Unspecified error]
When I try:
exec master..xp_cmdshell N'dir c:\ReleaseTwo\LogInandOut.xls'
I get
The system cannot find the file specified.
Any ideas?
Paul
".bill" wrote:

> I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet
, but receive the following error:
> OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
> Connection Closed
> here's the sql:
> select *
> into MyTable
> FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\Default.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
> any help is appreciated..|||Hi Paul,
The file is in the local machine and you might have run the query in
the server which is not the local machine
Madhivanan|||Hi Madhivanan,
It dosn't matter whether the excel (or txt/csv) file is on the server on on
my local machine I get the same result.
Paul.
"Madhivanan" wrote:

> Hi Paul,
> The file is in the local machine and you might have run the query in
> the server which is not the local machine
> Madhivanan
>|||Paul,
How do you know the file exists?
If it does, and exec master..xp_cmdshell N'dir
c:\ReleaseTwo\LogInandOut.xls' fails,
it's not a problem with OPENROWSET. It sounds like the account used by
SQL Server does not have permission to access the Excel file.
SK
Paul in Harrow wrote:
>Hi there,
>Has anyone found an answer to this yet?
>I tried:
>insert into tblTestSql (RowNo,RecNo,LdUserName,
>Code,LogIn,LogOut)
>SELECT RowNo,RecNo,LdUserName,
>Code,LogIn,LogOut
>FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\ReleaseTwo\LogInandOut.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
>Which gives me
>Server: Msg 7399, Level 16, State 1, Line 1
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: Unspecified error]
>When I try:
>exec master..xp_cmdshell N'dir c:\ReleaseTwo\LogInandOut.xls'
>I get
>The system cannot find the file specified.
>Any ideas?
>Paul
>".bill" wrote:
>
>|||> How do you know the file exists?
Because I created it.

> If it does, and exec master..xp_cmdshell N'dir
> c:\ReleaseTwo\LogInandOut.xls' fails,
> it's not a problem with OPENROWSET. It sounds like the account used by
> SQL Server does not have permission to access the Excel file.
I've just shown that to my techie and he's looking blank! How do I/we find
out what permissions SQL Server has & how do I/we (proberly me) change them?
Many thanks
Paul.|||
Paul in Harrow wrote:

>Because I created it.
>
>
>I've just shown that to my techie and he's looking blank! How do I/we find
>out what permissions SQL Server has & how do I/we (proberly me) change them
?
>
>
It might be as simple as: navigate to the file in Windows Explorer,
right-click, go to the security tab, and make sure the file is available
to the account under which the SQL Server service is running.
But managing Windows accounts is not my strong point, so you could also
look at "Setting up Windows Services Accounts" in Books Online and
see what you find on Usenet:
http://groups.google.co.uk/groups? ...missions%20file
http://www.google.co.uk/search? q=%...missions%20file
For the openquery statement to work, you should be able to log on to
Windows with the same account used by the SQL Server service and
then access the file.
SK

>Many thanks
>Paul.
>

Error while creating database

While trying to recreate a database i receive error 5149
database already exists.. Yet it doesn't. Have deleted
the files in the subdirectory the data and index files but
i can't see that there are any others to delete. Not sure
what else to do..Can you post the actual message text? This is important in diagnosing
possible causes if this error.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Debbie" <debbieba@.spokesman.com> wrote in message
news:0e0301c3676e$535579c0$a001280a@.phx.gbl...
> While trying to recreate a database i receive error 5149
> database already exists.. Yet it doesn't. Have deleted
> the files in the subdirectory the data and index files but
> i can't see that there are any others to delete. Not sure
> what else to do..