Can't start Query Analyzer on SQL Cluster

Have you experienced such problem in a Windows Cluster environment :
Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
Error : The Query Analyzer could not be started on the first node :
ISQLW.EXE - Entry Point Not Found
The procedure entry point ''? could not be located in the dynamic
link library SQLGUI.dll.>
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise
Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
--
It's possible the SQLGUI.DLL is corrupt. Rename the file in the cluster and
copy from a machine which works.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)|||> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)

Can't start Query Analyzer on SQL Cluster

Have you experienced such problem in a Windows Cluster environment :
Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
Error : The Query Analyzer could not be started on the first node :
ISQLW.EXE - Entry Point Not Found
The procedure entry point ??? could not be located in the dynamic
link library SQLGUI.dll.
>
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise
Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
It's possible the SQLGUI.DLL is corrupt. Rename the file in the cluster and
copy from a machine which works.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)
|||
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)

Can't select a datetime field in a query without time portion

Hi,
I am doing some project with SQL Server 2000 and C#. I am using a
SELECT statement to get a column and to bind it to a dropdown list. The
column is a datetime format. I don't need time portion of it. Before I
tried any CONVERT functions my query looked like this:
SELECT DISTINCT DateEntered FROM TBL_PTM_Report
I can get the data this way but only with time portion in it. I read
about CONVERT but can't get it working. I am getting all kinds of error
messages from Visual Studio.
I tried the lowwoling:
SELECT COVVERT(CHAR(10), DateEntered, 101) FROM TBL_PTM_Report
It didn't work. I need data in the following format MM/DD/YYYY
Thank you,
Stan> SELECT COVVERT(CHAR(10), DateEntered, 101) FROM TBL_PTM_Report
CONVERT.
AMB
"suslishe@.mail.ru" wrote:

> Hi,
> I am doing some project with SQL Server 2000 and C#. I am using a
> SELECT statement to get a column and to bind it to a dropdown list. The
> column is a datetime format. I don't need time portion of it. Before I
> tried any CONVERT functions my query looked like this:
> SELECT DISTINCT DateEntered FROM TBL_PTM_Report
> I can get the data this way but only with time portion in it. I read
> about CONVERT but can't get it working. I am getting all kinds of error
> messages from Visual Studio.
> I tried the lowwoling:
>
> SELECT COVVERT(CHAR(10), DateEntered, 101) FROM TBL_PTM_Report
> It didn't work. I need data in the following format MM/DD/YYYY
> Thank you,
> Stan
>|||This was my typing mistake, sorry! The statement looks like this:
SELECT CONVERT(CHAR(10), DateEntered, 101) FROM TBL_PTM_Report|||I just ran this in query analyser and everything works! But Visual
Studio gives me an error.

Cant seem to make this query work

Hi,

I have a query thatI need to make into one query for the sake of an application reading only one cursor.

Here's the syntax:

select (select distinct(x.amount) from escrow k inner join e120 x on k.escrow = x.escrow
inner join a10 g on x.escrow = g.escrow where k.ftype = 'S' group by x.amount, g.officer) As New,
a.officer as Officer, count(distinct(j.fstatus))as Escrow_Type, count(distinct(j.amount))as Amount, count(distinct(d.open_date))as [Open], count(distinct(d.close_date)) as Closed, count(distinct(can_date))as Cancelled

from a10 a
inner join escrow d on a.escrow = d.escrow
inner join e120 j on j.escrow = d.escrow where j.id_scr = 'e21' and j.fstatus = 'PAID' group by a.officer

The error message i'm recieving is the following:

Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

Any ideas? any suggestions would be great.

Thanks

This error came from the only subquery in your query (which produces the New column). You're trying to return a result set 'distinct(x.amount)' and then use it as an expression, which is not permitted. Because SQL can not predict how many rows will be returned by the subquery, and there is no relationship between the column New by the subquery and other columns in the whole query, thus SQL can't join theNew column to the whole result set as other columns. In this case, you should either make the subquery return a single value:

select (select max(distinct(x.amount)) from escrow k inner join e120 x on k.escrow = x.escrow
inner join a10 g on x.escrow = g.escrow where k.ftype = 'S' group by x.amount, g.officer) As New,
a.officer as Officer, count(distinct(j.fstatus))as Escrow_Type, count(distinct(j.amount))as Amount, count(distinct(d.open_date))as [Open], count(distinct(d.close_date)) as Closed, count(distinct(can_date))as Cancelled

from a10 a
inner join escrow d on a.escrow = d.escrow
inner join e120 j on j.escrow = d.escrow where j.id_scr = 'e21' and j.fstatus = 'PAID' group by a.officer

or move the tables referenced by the subquery and find join conditions with other tables, then returned a column data which satisfies the join conditions, rather than using subquery.

|||

Hi when I run the query I get the following error:

Server: Msg 512, Level 16, State 1, Line 1
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
Warning: Null value is eliminated by an aggregate or other SET operation.

Is there a substitute for the = operator I can use to get this to parse correctly?

Thanks,

|||

Strange What's the query you're using? Are you sure you add a MAX to make the subquery return single value?

selectmax(distinct(x.amount))

can't seem to get my GROUP BY ordering right

I have the following query, which works, but the ordering isn't quite
right, can anyone help?
SELECT
to_char(date_created,'DD-MON-YYYY') as date_joined,
COUNT(user_id) AS user_count
FROM
project_users
GROUP BY
to_char(date_created,'DD-MON-YYYY')
ORDER BY
to_char(date_created,'DD-MON-YYYY')
the output is shwon as follows:
02-APR-2006 - 1
03-APR-2006 - 1
04-APR-2006 - 4
05-APR-2006 - 8
06-APR-2006 - 11
08-MAR-2006 - 2
16-MAR-2006 - 2
17-MAR-2006 - 2
20-MAR-2006 - 3
21-MAR-2006 - 1
22-MAR-2006 - 1
but I would rather it was more logically ordered for a report, as so:
06-APR-2006 - 11
05-APR-2006 - 8
04-APR-2006 - 4
03-APR-2006 - 1
02-APR-2006 - 1
22-MAR-2006 - 1
21-MAR-2006 - 1
20-MAR-2006 - 3
17-MAR-2006 - 2
16-MAR-2006 - 2
08-MAR-2006 - 2
i.e. reverse order of date, and calendar month (not by month starting
letter)
TIA for any help and advicedid you try using DESC (for descending)?|||Kevin,
try
ORDER BY date_created DESC|||Also I suspect you're going to have to order desc by year/month/day
instead of d/m/y|||whooops.. forgot the mention that bit.. yup.. if I add DESC then the
order is reversed by DD, then MON, then YYYY... but that means that the
MAR dates appear before APR, as alphabetically, and in reverse order, M
comes before A.
I guess I should have mentioned that bit, eh' thanks for the quick
replies btw|||What if you try this (let me know if it helps..)
SELECT
to_char(date_created,'DD-MON-YYYY') as date_joined,
COUNT(user_id) AS user_count
FROM
project_users
GROUP BY
to_char(date_created,'DD-MON-YYYY')
ORDER BY
date_created desc
"Kevin Blount" wrote:

> I have the following query, which works, but the ordering isn't quite
> right, can anyone help?
> SELECT
> to_char(date_created,'DD-MON-YYYY') as date_joined,
> COUNT(user_id) AS user_count
> FROM
> project_users
> GROUP BY
> to_char(date_created,'DD-MON-YYYY')
> ORDER BY
> to_char(date_created,'DD-MON-YYYY')
>
> the output is shwon as follows:
> 02-APR-2006 - 1
> 03-APR-2006 - 1
> 04-APR-2006 - 4
> 05-APR-2006 - 8
> 06-APR-2006 - 11
> 08-MAR-2006 - 2
> 16-MAR-2006 - 2
> 17-MAR-2006 - 2
> 20-MAR-2006 - 3
> 21-MAR-2006 - 1
> 22-MAR-2006 - 1
> but I would rather it was more logically ordered for a report, as so:
> 06-APR-2006 - 11
> 05-APR-2006 - 8
> 04-APR-2006 - 4
> 03-APR-2006 - 1
> 02-APR-2006 - 1
> 22-MAR-2006 - 1
> 21-MAR-2006 - 1
> 20-MAR-2006 - 3
> 17-MAR-2006 - 2
> 16-MAR-2006 - 2
> 08-MAR-2006 - 2
> i.e. reverse order of date, and calendar month (not by month starting
> letter)
> TIA for any help and advice
>|||"Kevin Blount" <kevin.blount@.gmail.com> wrote in message
news:1144353616.181845.72600@.e56g2000cwe.googlegroups.com...
> whooops.. forgot the mention that bit.. yup.. if I add DESC then the
> order is reversed by DD, then MON, then YYYY... but that means that the
> MAR dates appear before APR, as alphabetically, and in reverse order, M
> comes before A.
> I guess I should have mentioned that bit, eh' thanks for the quick
> replies btw
>
I think you should have mentioned that this isn't a SQL Server query at all.
Oracle?
Anyway, try:
ORDER BY MIN(date_created)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Thanks David, using ' MIN(date_created) DESC ' worked a charm (just '
date_created DESC ' didn't work at all for some reason).
I must confess, I saw SQL in the group name, but missed the SQLSERVER
part.. but then it's tricky finding a general group for queries..
unless someone knows of one?|||"Kevin Blount" <kevin.blount@.gmail.com> wrote in message
news:1144354904.773319.110340@.i40g2000cwc.googlegroups.com...
> I must confess, I saw SQL in the group name, but missed the SQLSERVER
> part.. but then it's tricky finding a general group for queries..
> unless someone knows of one?
There are specific groups for Oracle:
comp.databases.oracle.server
comp.databases.oracle.misc
For others check out http://groups.google.com
Whatever the product you are using, *always* state your version number.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

can't see print messages during the running a of stored procedure

I have a stored procedure running from Query Analyzer that runs for a long
time and would like to have status messages print out during the procedure.
They all seem to come when the procedure is complete - is there any way to
have them print while it is running. I 've actually tried having the main
SP call a smaller SP with prints, but they don't come out till the end as
well.
Help to a new Transact SQL writer,
Thanks
TW
TW,
I don't know how to do just what you want, but you could try pumping your
messages into a trace table. Then you could query that table while the
long-running stored procedure continues. Transaction isolation levels would
affect how this works for you.
Russell Fields
"Weave" <tweaver60@.suscom.net> wrote in message
news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the
procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>
|||You could use RAISERROR and the NOWAIT option instead of PRINT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Weave" <tweaver60@.suscom.net> wrote in message news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>

Can't see data anymore!

I have had an issue when I try to return all rows or do a query on my data
tables. I get the error 8007007F unknown error
I have tried to instal the newest service releases sp3, and have had no
luck. I have upgraded my server to MS Server 2003.
If you have any ideas, I desparately need them!
Thanks
DerekTry re-install MDAC2.8.
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:A58B499A-6AD8-4AA7-9E7B-C8FCD27C0B4F@.microsoft.com...
> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek|||Install SP3a. The SQL Server version will be 8.00.760 (SP3).
"dkoz" wrote:
> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek|||Still no go. I have installed the sp3a, and have done just about everything
I can think of other then reinstalling the SQL server.
Quite frustrating!
"Richard_SQL" wrote:
> Install SP3a. The SQL Server version will be 8.00.760 (SP3).
>
> "dkoz" wrote:
> > I have had an issue when I try to return all rows or do a query on my data
> > tables. I get the error 8007007F unknown error
> > I have tried to instal the newest service releases sp3, and have had no
> > luck. I have upgraded my server to MS Server 2003.
> >
> > If you have any ideas, I desparately need them!
> > Thanks
> > Derek|||Did you try re-install MDAC2.8?
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:5DF77B1A-C076-46CF-B854-B830F5171B9D@.microsoft.com...
> Still no go. I have installed the sp3a, and have done just about
everything
> I can think of other then reinstalling the SQL server.
> Quite frustrating!
> "Richard_SQL" wrote:
> > Install SP3a. The SQL Server version will be 8.00.760 (SP3).
> >
> >
> >
> > "dkoz" wrote:
> >
> > > I have had an issue when I try to return all rows or do a query on my
data
> > > tables. I get the error 8007007F unknown error
> > > I have tried to instal the newest service releases sp3, and have had
no
> > > luck. I have upgraded my server to MS Server 2003.
> > >
> > > If you have any ideas, I desparately need them!
> > > Thanks
> > > Derek

Can't see data anymore!

I have had an issue when I try to return all rows or do a query on my data
tables. I get the error 8007007F unknown error
I have tried to instal the newest service releases sp3, and have had no
luck. I have upgraded my server to MS Server 2003.
If you have any ideas, I desparately need them!
Thanks
DerekTry re-install MDAC2.8.
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:A58B499A-6AD8-4AA7-9E7B-C8FCD27C0B4F@.microsoft.com...
> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek|||Install SP3a. The SQL Server version will be 8.00.760 (SP3).
"dkoz" wrote:

> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek|||Still no go. I have installed the sp3a, and have done just about everything
I can think of other then reinstalling the SQL server.
Quite frustrating!
"Richard_SQL" wrote:
[vbcol=seagreen]
> Install SP3a. The SQL Server version will be 8.00.760 (SP3).
>
> "dkoz" wrote:
>|||Did you try re-install MDAC2.8?
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:5DF77B1A-C076-46CF-B854-B830F5171B9D@.microsoft.com...
> Still no go. I have installed the sp3a, and have done just about
everything[vbcol=seagreen]
> I can think of other then reinstalling the SQL server.
> Quite frustrating!
> "Richard_SQL" wrote:
>
data[vbcol=seagreen]
no[vbcol=seagreen]

Can't see data anymore!

I have had an issue when I try to return all rows or do a query on my data
tables. I get the error 8007007F unknown error
I have tried to instal the newest service releases sp3, and have had no
luck. I have upgraded my server to MS Server 2003.
If you have any ideas, I desparately need them!
Thanks
Derek
Try re-install MDAC2.8.
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:A58B499A-6AD8-4AA7-9E7B-C8FCD27C0B4F@.microsoft.com...
> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek
|||Install SP3a. The SQL Server version will be 8.00.760 (SP3).
"dkoz" wrote:

> I have had an issue when I try to return all rows or do a query on my data
> tables. I get the error 8007007F unknown error
> I have tried to instal the newest service releases sp3, and have had no
> luck. I have upgraded my server to MS Server 2003.
> If you have any ideas, I desparately need them!
> Thanks
> Derek
|||Still no go. I have installed the sp3a, and have done just about everything
I can think of other then reinstalling the SQL server.
Quite frustrating!
"Richard_SQL" wrote:
[vbcol=seagreen]
> Install SP3a. The SQL Server version will be 8.00.760 (SP3).
>
> "dkoz" wrote:
|||Did you try re-install MDAC2.8?
Ayad
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:5DF77B1A-C076-46CF-B854-B830F5171B9D@.microsoft.com...
> Still no go. I have installed the sp3a, and have done just about
everything[vbcol=seagreen]
> I can think of other then reinstalling the SQL server.
> Quite frustrating!
> "Richard_SQL" wrote:
data[vbcol=seagreen]
no[vbcol=seagreen]

Can't run Stored Procedure

I am trying to run a stored procedure from an SQL task:

First, here is the proc (execs fine in : SSMS query)

CREATE PROC [dbo].[sp_Hist_Max_Dates]

@.Interval varchar(8),

@.Name1 varchar(32),

@.Max_Date datetime OUTPUT

AS

IF @.Interval = 'd'

BEGIN

SELECT @.Max_Date = MAX(Max_Daily_Date) FROM SiteTable WHERE Site_Name = @.Name1

END

ELSE IF @.Interval = 'm'

BEGIN

SELECT @.Max_Date = MAX(Max_Monthly_Date) FROM SIteTable WHERE SIte_Name = @.Name1

END

Here is the call from the Execute SQL Task:

EXEC sp_Hist_Max_Dates ?, ?, ? OUTPUT

Here are how the parameters are defined in the Execute SQL Task:

gv_VarInterval INPUT varchar 0

gv_Name1 INPUT varchar 1

gv_MaxDate OUTPUT datetime 2

(Variables used as input parameters defined as strings with package scope)

Here is the error I am getting:

[Execute SQL Task] Error: Executing the query "EXEC dbo.sp_Hist_Max_Dates ?, ?, ? OUTPUT" failed with the following error: "Error HRESULT E_FAIL has been returned from a call to a COM component.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The connection is just OLEDB to SQL Server 2005. Any ideas why is this not working?

Thanks!

Kayda

Try adding the parameter name (as declared in the SP) and the '=' sign to the SQL command:

EXEC sp_Hist_Max_Dates @.Parametername1 = ?,@.Parametername2= ?, @.Parametername3 = ? OUTPUT

|||another cryptic error message? hardly surprising... check if the account under which a package is run, has rights to execute the stored procedure|||On your SQL Task, set the "BypassPrepare" to TRUE. Otherwise the validation tries to validate the ?'s, and can't.

Cant run query today that ran yesterday

I converted an MS Access db to SQL Server 2005 Express yesterday. I used FullConvert Enterprise for the conversion and it worked great. I ran several queries and saved them, and they ran fine. Today, running the same queries, I get this error message:
Msg 208, Level 16, State 1, Line 1
Invalid object name 'tblTXMup'

I googled the message and found someone who had a similar problem and their answer was they were not the dbo. I checked the new database and it was owned by sa so I logged in as sa and got the same error.

Can anyone set me straight so I can get into this db?

Thanks,probably you are executing your query in the context of some other database, not the one you created yesterday.|||The error seems to suggest that the object that you referenced doesn't exist in the schema.

Regards,|||Thanks for looking at this. I only converted the one database so I know it is the right one. I can display the table I am trying to query, so I know I am logged in to the right one. The query was saved from yesterday and it got a result then but throws the error now.

Any other ideas?

Thanks,|||Sure,

Can you execute a query (or if you fancy, a DML statement for a change) against the table. It is important to differentiate between just seeing the table listed as a database object and the ability to execute a statement against it.

Regards,|||I can't execute a query because I get the error above, but I can not only see the table in the left panel of SQL Management Studio Express but can also display the table's data by right clicking on it and selecting "Open Table".|||OK. Something is not right here.

From what you say above, this is in no a security issue. When you right click on a table and click 'Open Table', the underlying event will just execute a SELECT statement against the table.

Therefore, you should be able to execute:

select * from tblTXMup

If you still receive the same message, try the following and let me know what the result is.

select
*
from
information_schema.tables
wehre
table_name = 'tblTXMup'

Regards,|||Robert,

Thanks again for helping. After running your query I got what looked like five column headers as follows: blank, TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, TABLE_TYPE

What does that tell us?|||What was the output returned for each query?

For the first, did you receive an error message, an empty result set, or a set of rows? And similarly for the second, did you receive a single row describing the table,or did you just receive the column headers, but no rows?

Regards,|||Thanks, Robert. From the first, that is the one that I started this thread with, and it still throws the same error. In the second, I got no error, did get headers, got no rows. The headers act like buttons that "depress" when clicked on.|||Could you please try to create the table under the same login account that from which you ran the above queries. At this stage, we wish to examine ownership configurations for the table and the databases that your account is accessing.

What may be happening is that you have two sessions open, each accessing a different database. Your first session may display the 'Welcome Page' to SQL Server 2005 management studio. When you browse the object tree, you select the appropriate database and then browse the object. Having selected 'DatabaseA' from the Object List, you see the results that you had expected.

On the other hand your second session (which appears as a new tab) has opened to an SQL Query interface, but the session is connected to a different database by default. This may well be the Master database. Consequently when you run the select query against the master database, SQL Server reports that your table does not exist.

You may just want to check which database your SQL Query interface session is connected to, and ensure that this is indeed the database that contains the table you wish to query. If this session appears to be accessing the correct database, then you can create a simple table from this session with the same name as the one you are trying to query, and note the outcome.

Once you have created this table, check to see that it appears in the database you expected it to, in the Object Browser. Once you have found it, compare this location to that of the original table that you mentioned in you first post, against which you were able to right click and select 'Open Table'.

The following code will create a simple one column table.

create table tblTXMup (id int);

Regards,|||Has it got anything to do with 3 part naming?
Objects that aren't given a 2nd part are assumed to be owned by "dbo"
i.e.

SELECT * FROM myTable
--equivalent to
SELECT * FROM dbo.myTable

Try running the following and let me know if you get any results

SELECT *
FROM sysobjects
WHERE type IN ('U', 'V')
AND name LIKE '%tblTXMup%'|||George, I ran your query and got a number of column headings but no rows returned. Headings started off name, id, xtype, uid, ...

Does that tell us anything?

Thanks for helping.|||Loyd,

Have you performed the steps that I mentioned in my most recent post? They are designed such that by the end, you should almost certainly know the answer to your problem.

The essence of the problem is this: We need to identify the a) where the table is, b) which account owns it, and most importantly, c) which account you are connected as when you are running these queries that we have supplied.|||OK, so you can open the table via enterprise manager, but can not get to it in Query Analyzer. That sums up the problem? From the results of the queries above, I suspect the two tools are looking at different databases. Run this query to see what database you are currently in in Query Analyzer:

select db_name()

Do you get the expected result?|||r123456 and MCrowley you are both on to something. When I created the table it appeared in the master system db. How can I move to or attach to the correct db?|||Exactly what I thought. You had two sessions open, each pointing to different databases.

I would attach a screen shot to explain, but I don't have SQL Server Management Studio installed. There is a drop down list on the tool bar, just above the query windows, which contains the list of databases that you're account has access to. The database name that appears selected in this list, is the one that all statements in the current session will be executed against, unless of course you explicitly define the database name in the query, which evidently you have not done on this occasion.

Once you've selected the session in which you want to run the SQL Query (not the one you used to browse the Object Tree), ensure that the value in this drop down list is the one for which you want your query to be executed against.

Regards,|||One note, putting user tables in the master database is generally a bad thing. Recovering the master database from backup requires a series of steps that include stopping and restarting the whole server several times. This gets to be annoying to anyone else who happens to be using the server at the time. I would suggest either redoing the upgrade to a user database (you can create one through Enterprise Manager easily enough), or exporting the data from master to a user database. The choice will depend on how many foreign keys you have created in there.|||Ah yes. I will second that suggestion. The number of times I have gone to execute a query, only to notice that the database is pointing to Master.

Another suggestion is to create administrator accounts that are a step down in terms of access rights from the DBO account. This is common practice in most organisations as it achieves two major benefits. Firstly, you have accountability for all access to the database if you configure access to SQL Server to be through Windows NT accounts. Secondly, you can ensure that users only have access to the databases that is permitted by your firm's access policy.

Regards,|||Thanks once more for all the assistance. I am finding out what a newbie I am with SQL Server. I have been submitting SQL queries to SQL Server for years, but have not had a great deal of experience with administering it.

I can submit a query by specifying the database, but the dropdown where I could specify a database to connect to is grayed out and I can't access it. What can I do in SQL Server Management Studio Express to get access to that dropdown?

BTW, as far as permissions, I am working on SQL Server on my own development machine, trying to get all the queries working before uploading to the host development site.

Thanks again|||Thanks once more for all the assistance. I am finding out what a newbie I am with SQL Server. I have been submitting SQL queries to SQL Server for years, but have not had a great deal of experience with administering it.

I can submit a query by specifying the database, but the dropdown where I could specify a database to connect to is grayed out and I can't access it. What can I do in SQL Server Management Studio Express to get access to that dropdown?

BTW, as far as permissions, I am working on SQL Server on my own development machine, trying to get all the queries working before uploading to the host development site.

Thanks again

Loyd,

You will need to ensure that you have the set the focus on an SQL Server query session, for it is these sessions that the drop down list applies to. When you want to access the Database name drop down list, first click anywhere in the session window (example: the window where you type the SQL queries) and then the drop down list become available.

It is unlikely that there are other reasons for the drop down list not being available for you to access.

Regards,

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1.
Any immediate thoughts would be welcome.Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1
.
Any immediate thoughts would be welcome.Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1.
Any immediate thoughts would be welcome.
Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't run OpenQuery against OLAP Database

I'm trying to execute a query against an AS 2000 database from query analyzer. I've created the linked server using the "Microsoft OLE DB Provider for OLAP Services" ("Allow InProcess" checked) but I'm getting an error message: "Could not get the data of the row from the OLE DB provider 'MSOLAP'.
[OLE/DB provider returned message: An unexpected internal error has occurred.]
OLE DB error trace [OLE/DB Provider 'MSOLAP' IRowset::GetData returned 0x80040e21: Data status returned from the provider: [COLUMN_NAME=[Measures].[Act] STATUS=DBSTATUS_E_UNAVAILABLE]]."

Has anyone seen this problem before? Do you know what is needed to fix it? I had been able to execute an OpenQuery against another AS2000 database but that was with another machine and I can't pin point what I did to get it to work (the machine had a lot installed on it and I'm not sure what did the trick).

Any help is greatly appreciated.

Carmen.

Please make sure that AS2000 SP4 client components are installed on that machine. I recall similar bug that was fixed in one of the SPs.|||

Thanks, Irina. All machines involved have SP4 installed on them. I think there is something missing on the client as well as on the server. Here is why:

Old laptop connecting to Server A: OK

Old laptop connecting to Server B: Error

New laptop connecting to Server A: Error

New laptop connecting to Server B: Error

If the problem was only on the new laptop, the old one should be able to connect to Server B. And if the problem was only on Server B, the new laptop should connect to Server A.

Thanks,

Carmen.

|||

Actually, I found that what is different on my old laptop is that it has SP3 instead of SP4.... And I think I read it somewhere about SP4 causing this problem. Does anyone knows of a fix for this?

Thanks,

Carmen

Can't run LDAP Query From Remote Machine

Hi all,
I have a SQL 2005 server with a linked server which points to our
active directory. I am able to query the active directory from the
local machine when RDC'ed into the server, but when I run the query
from a remote machine using Management Studio, I get this error:
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT *
FROM 'LDAP://prudc/DC=<domain>,DC=com'
" against OLE DB provider "ADSDSOObject" for linked server "ADSI".
The query is:
SELECT *
FROM OPENQUERY( ADSI,
'SELECT *
FROM ''LDAP://prudc/DC=<domain>,DC=com''
'
)
(note I replaced our domain name with <domain> in the above query and
error message)
This issue isn't specific to the above query as I've tried many ldap
queries and they have all worked on the local machine but failed on the
remote machine.
I'm completely stomped on this and would greatly appreciate any help I
can get.
ThanksHi Jim
This was a previous post when someone had the same error
http://tinyurl.com/pjg7s I am not sure how much use it will be!
If the query works on the server then I would expect it to be ok, which
probably leaves permission/access as the main issue. Can you use VB script to
query the AD e.g. using the scripts from http://www.rlmueller.net/?
John
"Jim" wrote:
> Hi all,
> I have a SQL 2005 server with a linked server which points to our
> active directory. I am able to query the active directory from the
> local machine when RDC'ed into the server, but when I run the query
> from a remote machine using Management Studio, I get this error:
>
> Msg 7320, Level 16, State 2, Line 1
> Cannot execute the query "SELECT *
> FROM 'LDAP://prudc/DC=<domain>,DC=com'
> " against OLE DB provider "ADSDSOObject" for linked server "ADSI".
>
> The query is:
> SELECT *
> FROM OPENQUERY( ADSI,
> 'SELECT *
> FROM ''LDAP://prudc/DC=<domain>,DC=com''
> '
> )
> (note I replaced our domain name with <domain> in the above query and
> error message)
>
> This issue isn't specific to the above query as I've tried many ldap
> queries and they have all worked on the local machine but failed on the
> remote machine.
> I'm completely stomped on this and would greatly appreciate any help I
> can get.
> Thanks
>|||Thanks for the help but unfortunately, I've already looked at that post
and the issue is a bit different.
The issue I'm having seems to have something to do with running a query
from a remote machine. So if I run a query on our SQL Server box from
my local desktop machine, I get the error. Running the query directly
on the SQL Server box while RDCed into the machine works flawlessly.
I did try to run a .vbs script from my machine which was able to query
the active directory...thanks for the link =). This leads me to
believe that it has something to do with SQL server security
restricting queries run from remote machines. I ran the surface area
configuration utility and didn't really see anything that jumped out at
me...
Anyone have any ideas?|||Alright, I've figured out a fix..
The AD linked server that I originally created was set to login to AD
with the credentials of the current security context. I changed this
to log in with a specified login and it worked fine. Whats strange is
that I set it to my own login account which I was using to run the
query remotely anyways. I guess SQL server queries ran remotely are
not run under the logged in users' security context after all?
Thanks for your help John =).

Can't run LDAP Query From Remote Machine

Hi all,
I have a SQL 2005 server with a linked server which points to our
active directory. I am able to query the active directory from the
local machine when RDC'ed into the server, but when I run the query
from a remote machine using Management Studio, I get this error:
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT *
FROM 'LDAP://prudc/DC=<domain>,DC=com'
" against OLE DB provider "ADSDSOObject" for linked server "ADSI".
The query is:
SELECT *
FROM OPENQUERY( ADSI,
'SELECT *
FROM ''LDAP://prudc/DC=<domain>,DC=com''
'
)
(note I replaced our domain name with <domain> in the above query and
error message)
This issue isn't specific to the above query as I've tried many ldap
queries and they have all worked on the local machine but failed on the
remote machine.
I'm completely stomped on this and would greatly appreciate any help I
can get.
ThanksHi Jim
This was a previous post when someone had the same error
http://tinyurl.com/pjg7s I am not sure how much use it will be!
If the query works on the server then I would expect it to be ok, which
probably leaves permission/access as the main issue. Can you use VB script t
o
query the AD e.g. using the scripts from http://www.rlmueller.net/?
John
"Jim" wrote:

> Hi all,
> I have a SQL 2005 server with a linked server which points to our
> active directory. I am able to query the active directory from the
> local machine when RDC'ed into the server, but when I run the query
> from a remote machine using Management Studio, I get this error:
>
> Msg 7320, Level 16, State 2, Line 1
> Cannot execute the query "SELECT *
> FROM 'LDAP://prudc/DC=<domain>,DC=com'
> " against OLE DB provider "ADSDSOObject" for linked server "ADSI".
>
> The query is:
> SELECT *
> FROM OPENQUERY( ADSI,
> 'SELECT *
> FROM ''LDAP://prudc/DC=<domain>,DC=com''
> '
> )
> (note I replaced our domain name with <domain> in the above query and
> error message)
>
> This issue isn't specific to the above query as I've tried many ldap
> queries and they have all worked on the local machine but failed on the
> remote machine.
> I'm completely stomped on this and would greatly appreciate any help I
> can get.
> Thanks
>|||Thanks for the help but unfortunately, I've already looked at that post
and the issue is a bit different.
The issue I'm having seems to have something to do with running a query
from a remote machine. So if I run a query on our SQL Server box from
my local desktop machine, I get the error. Running the query directly
on the SQL Server box while RDCed into the machine works flawlessly.
I did try to run a .vbs script from my machine which was able to query
the active directory...thanks for the link =). This leads me to
believe that it has something to do with SQL server security
restricting queries run from remote machines. I ran the surface area
configuration utility and didn't really see anything that jumped out at
me...
Anyone have any ideas?|||Alright, I've figured out a fix..
The AD linked server that I originally created was set to login to AD
with the credentials of the current security context. I changed this
to log in with a specified login and it worked fine. Whats strange is
that I set it to my own login account which I was using to run the
query remotely anyways. I guess SQL server queries ran remotely are
not run under the logged in users' security context after all?
Thanks for your help John =).

Can't run LDAP Query From Remote Machine

Hi all,
I have a SQL 2005 server with a linked server which points to our
active directory. I am able to query the active directory from the
local machine when RDC'ed into the server, but when I run the query
from a remote machine using Management Studio, I get this error:
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT *
FROM 'LDAP://prudc/DC=<domain>,DC=com'
" against OLE DB provider "ADSDSOObject" for linked server "ADSI".
The query is:
SELECT *
FROM OPENQUERY( ADSI,
'SELECT *
FROM ''LDAP://prudc/DC=<domain>,DC=com''
'
)
(note I replaced our domain name with <domain> in the above query and
error message)
This issue isn't specific to the above query as I've tried many ldap
queries and they have all worked on the local machine but failed on the
remote machine.
I'm completely stomped on this and would greatly appreciate any help I
can get.
Thanks
Hi Jim
This was a previous post when someone had the same error
http://tinyurl.com/pjg7s I am not sure how much use it will be!
If the query works on the server then I would expect it to be ok, which
probably leaves permission/access as the main issue. Can you use VB script to
query the AD e.g. using the scripts from http://www.rlmueller.net/?
John
"Jim" wrote:

> Hi all,
> I have a SQL 2005 server with a linked server which points to our
> active directory. I am able to query the active directory from the
> local machine when RDC'ed into the server, but when I run the query
> from a remote machine using Management Studio, I get this error:
>
> Msg 7320, Level 16, State 2, Line 1
> Cannot execute the query "SELECT *
> FROM 'LDAP://prudc/DC=<domain>,DC=com'
> " against OLE DB provider "ADSDSOObject" for linked server "ADSI".
>
> The query is:
> SELECT *
> FROM OPENQUERY( ADSI,
> 'SELECT *
> FROM ''LDAP://prudc/DC=<domain>,DC=com''
> '
> )
> (note I replaced our domain name with <domain> in the above query and
> error message)
>
> This issue isn't specific to the above query as I've tried many ldap
> queries and they have all worked on the local machine but failed on the
> remote machine.
> I'm completely stomped on this and would greatly appreciate any help I
> can get.
> Thanks
>
|||Thanks for the help but unfortunately, I've already looked at that post
and the issue is a bit different.
The issue I'm having seems to have something to do with running a query
from a remote machine. So if I run a query on our SQL Server box from
my local desktop machine, I get the error. Running the query directly
on the SQL Server box while RDCed into the machine works flawlessly.
I did try to run a .vbs script from my machine which was able to query
the active directory...thanks for the link =). This leads me to
believe that it has something to do with SQL server security
restricting queries run from remote machines. I ran the surface area
configuration utility and didn't really see anything that jumped out at
me...
Anyone have any ideas?
|||Alright, I've figured out a fix..
The AD linked server that I originally created was set to login to AD
with the credentials of the current security context. I changed this
to log in with a specified login and it worked fine. Whats strange is
that I set it to my own login account which I was using to run the
query remotely anyways. I guess SQL server queries ran remotely are
not run under the logged in users' security context after all?
Thanks for your help John =).

Can't query linked Access database specified by UNC

Hello,
I link Access database to sql server 2000 with ole db 4 provider; tell it to
logon with username ADMIN, empty password.
If the database is on a local drive, everything works correctly, I see the
tables of the access database in EM, and I successfully run query like
select * from accessdb...table1
If the database is on a remote drive and is specified by UNC, I still see
the tables in EM when EM runs on the server; but when I run EM on another
machine, focusing the tables under the linked server returns error
0x80004005. Same when I try to run a query (even on the server):
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\server\share\accessdb.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
Sql server is running on domain administrative account. At the same time as
the message is issued, I can log on that account on the server, launch
Access, and successfully open that same remote database using the same UNC
path.
What gives?
thanks,
Vadim Rapp
Polyscience, Inc.The first is to do is ensure that the database is not being
opened exclusively by other users. If that's all fine then
the error is likely related to permissions.
The account accessing the database needs a minimum of
something similar to Create, Destroy, Read, Write (depending
on the OS) on the folder where the mdb and ldb lives so it
can work with the .ldb file. Those are the minimum
permissions needed in general but it depends upon what
version of Access, what version of MDAC, what OS.
If the permissions are correct, you need to drill down
further to the access control and make sure that the account
has change permissions on the folder where the ldb file
resides. Make sure these are correct by explicitly setting
the permissions for the account.
I've seen several places just use a specific folder for just
the mdb (and consequently the ldb) and give the account full
control over that folder to make things less convoluted in
terms of permissions and the requirement for the ldb file.
-Sue
On Mon, 17 Jan 2005 13:35:38 -0600, "Vadim Rapp"
<vrapp@.nospam.polyscience.com> wrote:
>Hello,
>I link Access database to sql server 2000 with ole db 4 provider; tell it to
>logon with username ADMIN, empty password.
>If the database is on a local drive, everything works correctly, I see the
>tables of the access database in EM, and I successfully run query like
>select * from accessdb...table1
>If the database is on a remote drive and is specified by UNC, I still see
>the tables in EM when EM runs on the server; but when I run EM on another
>machine, focusing the tables under the linked server returns error
>0x80004005. Same when I try to run a query (even on the server):
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\server\share\accessdb.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>Sql server is running on domain administrative account. At the same time as
>the message is issued, I can log on that account on the server, launch
>Access, and successfully open that same remote database using the same UNC
>path.
>What gives?
>
>thanks,
>Vadim Rapp
>Polyscience, Inc.|||Hello Sue:
You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
SH> The first is to do is ensure that the database is not being
SH> opened exclusively by other users. If that's all fine then
SH> the error is likely related to permissions.
I thought that as well; that's why, as I wrote, I manually logged on the sql
server machine, with the same userid as sqlserver; started Access and opened
the same database successfully.
In other words, I manually did exactly what sql server couldn't do, with the
same login id on the same machine.
Vadim|||Yes...but you still need to check the permissions - the
whole ldb thing. And you need to make sure the permissions
are explicitly set. Logging on and starting access and
opening the database manually is not the same thing.
-Sue
On Tue, 18 Jan 2005 16:07:49 -0600, "Vadim Rapp"
<vrapp@.nospam.polyscience.com> wrote:
>Hello Sue:
>You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
> SH> The first is to do is ensure that the database is not being
> SH> opened exclusively by other users. If that's all fine then
> SH> the error is likely related to permissions.
>I thought that as well; that's why, as I wrote, I manually logged on the sql
>server machine, with the same userid as sqlserver; started Access and opened
>the same database successfully.
>In other words, I manually did exactly what sql server couldn't do, with the
>same login id on the same machine.
>Vadim|||Not that it's to much help, but I've seen a similar issue with Excel files.
I never really found a solution other than having the files on the
SQLServer. I've also tried with various accounts that has full admin access
to the server, domain, local machine etc. but to no avail. I'd be happy to
know the solution/reason since it's a bit annoying that I have to put the
files on the SQLServer to make it work.
Regards
Steen
Vadim Rapp wrote:
> Hello Sue:
> You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
>> The first is to do is ensure that the database is not being
>> opened exclusively by other users. If that's all fine then
>> the error is likely related to permissions.
> I thought that as well; that's why, as I wrote, I manually logged on
> the sql server machine, with the same userid as sqlserver; started
> Access and opened the same database successfully.
> In other words, I manually did exactly what sql server couldn't do,
> with the same login id on the same machine.
> Vadim|||Hello Steen:
You wrote in conference
microsoft.public.sqlserver.security,microsoft.public.sqlserver.server on
Fri, 21 Jan 2005 13:02:07 +0100:
SP> Not that it's to much help, but I've seen a similar issue with Excel
SP> files. I never really found a solution other than having the files on
SP> the SQLServer. I've also tried with various accounts that has full
SP> admin access to the server, domain, local machine etc. but to no avail.
SP> I'd be happy to know the solution/reason since it's a bit annoying that
SP> I have to put the files on the SQLServer to make it work.
the only good news is that, as I've found, it works correctly with SQL
Server 2005.
Vadim|||Hello Sue:
You wrote in conference
microsoft.public.sqlserver.security,microsoft.public.sqlserver.server on
Tue, 18 Jan 2005 16:11:38 -0700:
SH> Yes...but you still need to check the permissions - the
SH> whole ldb thing. And you need to make sure the permissions
SH> are explicitly set. Logging on and starting access and
SH> opening the database manually is not the same thing.
hmm... if I open the database manually, obviously, Access is creating the
ldb... thus, it can do it... How is it not the same thing?
And it looks like in sql server 2005 it works just fine.
Vadim|||SQL Server does not start up Access and then open up an mdb.
It accesses the mdb.
Just like it's different if you double click a file vs. open
an application and then do a File, Open to open the file.
-Sue
On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
<vr@.myrealbox.nospam.com> wrote:
>Hello Sue:
>You wrote in conference
>microsoft.public.sqlserver.security,microsoft.public.sqlserver.server on
>Tue, 18 Jan 2005 16:11:38 -0700:
> SH> Yes...but you still need to check the permissions - the
> SH> whole ldb thing. And you need to make sure the permissions
> SH> are explicitly set. Logging on and starting access and
> SH> opening the database manually is not the same thing.
>hmm... if I open the database manually, obviously, Access is creating the
>ldb... thus, it can do it... How is it not the same thing?
>And it looks like in sql server 2005 it works just fine.
>Vadim|||Vadim,
That last example wasn't a good one. Nonetheless, SQL Server
doesn't start Access and then open a database.
Other than security issues, combinations of MDAC/Jet drivers
can also cause problems and you may want to check those. If
you feel certain that this is a bug in SQL Server, you can
open a case with product support. You will not be charged
for the incident if it is a bug.
-Sue
On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
<vr@.myrealbox.nospam.com> wrote:
>Hello Sue:
>You wrote in conference
>microsoft.public.sqlserver.security,microsoft.public.sqlserver.server on
>Tue, 18 Jan 2005 16:11:38 -0700:
> SH> Yes...but you still need to check the permissions - the
> SH> whole ldb thing. And you need to make sure the permissions
> SH> are explicitly set. Logging on and starting access and
> SH> opening the database manually is not the same thing.
>hmm... if I open the database manually, obviously, Access is creating the
>ldb... thus, it can do it... How is it not the same thing?
>And it looks like in sql server 2005 it works just fine.
>Vadim|||one thing that worked for me on loading dumps from UNCs is that i had
to use an absolute UNC path and not the share name.
for example:
if i had a share named "share" on folder X on my C drive
rather than going to //myComputer/share
i had to go to //myComputer/C$/X
and everything worked fine...it is worth a shot.
hth,
hans
Sue Hoegemeier wrote:
> Vadim,
> That last example wasn't a good one. Nonetheless, SQL Server
> doesn't start Access and then open a database.
> Other than security issues, combinations of MDAC/Jet drivers
> can also cause problems and you may want to check those. If
> you feel certain that this is a bug in SQL Server, you can
> open a case with product support. You will not be charged
> for the incident if it is a bug.
> -Sue
> On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
> <vr@.myrealbox.nospam.com> wrote:
> >Hello Sue:
> >You wrote in conference
>microsoft.public.sqlserver.security,microsoft.public.sqlserver.server
on
> >Tue, 18 Jan 2005 16:11:38 -0700:
> >
> > SH> Yes...but you still need to check the permissions - the
> > SH> whole ldb thing. And you need to make sure the permissions
> > SH> are explicitly set. Logging on and starting access and
> > SH> opening the database manually is not the same thing.
> >
> >hmm... if I open the database manually, obviously, Access is
creating the
> >ldb... thus, it can do it... How is it not the same thing?
> >
> >And it looks like in sql server 2005 it works just fine.
> >
> >Vadim

Can't query linked Access database specified by UNC

Hello,
I link Access database to sql server 2000 with ole db 4 provider; tell it to
logon with username ADMIN, empty password.
If the database is on a local drive, everything works correctly, I see the
tables of the access database in EM, and I successfully run query like
select * from accessdb...table1
If the database is on a remote drive and is specified by UNC, I still see
the tables in EM when EM runs on the server; but when I run EM on another
machine, focusing the tables under the linked server returns error
0x80004005. Same when I try to run a query (even on the server):
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\server\share\accessdb.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
Sql server is running on domain administrative account. At the same time as
the message is issued, I can log on that account on the server, launch
Access, and successfully open that same remote database using the same UNC
path.
What gives?
thanks,
Vadim Rapp
Polyscience, Inc.
The first is to do is ensure that the database is not being
opened exclusively by other users. If that's all fine then
the error is likely related to permissions.
The account accessing the database needs a minimum of
something similar to Create, Destroy, Read, Write (depending
on the OS) on the folder where the mdb and ldb lives so it
can work with the .ldb file. Those are the minimum
permissions needed in general but it depends upon what
version of Access, what version of MDAC, what OS.
If the permissions are correct, you need to drill down
further to the access control and make sure that the account
has change permissions on the folder where the ldb file
resides. Make sure these are correct by explicitly setting
the permissions for the account.
I've seen several places just use a specific folder for just
the mdb (and consequently the ldb) and give the account full
control over that folder to make things less convoluted in
terms of permissions and the requirement for the ldb file.
-Sue
On Mon, 17 Jan 2005 13:35:38 -0600, "Vadim Rapp"
<vrapp@.nospam.polyscience.com> wrote:

>Hello,
>I link Access database to sql server 2000 with ole db 4 provider; tell it to
>logon with username ADMIN, empty password.
>If the database is on a local drive, everything works correctly, I see the
>tables of the access database in EM, and I successfully run query like
>select * from accessdb...table1
>If the database is on a remote drive and is specified by UNC, I still see
>the tables in EM when EM runs on the server; but when I run EM on another
>machine, focusing the tables under the linked server returns error
>0x80004005. Same when I try to run a query (even on the server):
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\server\share\accessdb.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>Sql server is running on domain administrative account. At the same time as
>the message is issued, I can log on that account on the server, launch
>Access, and successfully open that same remote database using the same UNC
>path.
>What gives?
>
>thanks,
>Vadim Rapp
>Polyscience, Inc.
|||Hello Sue:
You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
SH> The first is to do is ensure that the database is not being
SH> opened exclusively by other users. If that's all fine then
SH> the error is likely related to permissions.
I thought that as well; that's why, as I wrote, I manually logged on the sql
server machine, with the same userid as sqlserver; started Access and opened
the same database successfully.
In other words, I manually did exactly what sql server couldn't do, with the
same login id on the same machine.
Vadim
|||Yes...but you still need to check the permissions - the
whole ldb thing. And you need to make sure the permissions
are explicitly set. Logging on and starting access and
opening the database manually is not the same thing.
-Sue
On Tue, 18 Jan 2005 16:07:49 -0600, "Vadim Rapp"
<vrapp@.nospam.polyscience.com> wrote:

>Hello Sue:
>You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
> SH> The first is to do is ensure that the database is not being
> SH> opened exclusively by other users. If that's all fine then
> SH> the error is likely related to permissions.
>I thought that as well; that's why, as I wrote, I manually logged on the sql
>server machine, with the same userid as sqlserver; started Access and opened
>the same database successfully.
>In other words, I manually did exactly what sql server couldn't do, with the
>same login id on the same machine.
>Vadim
|||Not that it's to much help, but I've seen a similar issue with Excel files.
I never really found a solution other than having the files on the
SQLServer. I've also tried with various accounts that has full admin access
to the server, domain, local machine etc. but to no avail. I'd be happy to
know the solution/reason since it's a bit annoying that I have to put the
files on the SQLServer to make it work.
Regards
Steen
Vadim Rapp wrote:
> Hello Sue:
> You wrote on Tue, 18 Jan 2005 13:23:38 -0700:
>
> I thought that as well; that's why, as I wrote, I manually logged on
> the sql server machine, with the same userid as sqlserver; started
> Access and opened the same database successfully.
> In other words, I manually did exactly what sql server couldn't do,
> with the same login id on the same machine.
> Vadim
|||Hello Steen:
You wrote in conference
microsoft.public.sqlserver.security,microsoft.publ ic.sqlserver.server on
Fri, 21 Jan 2005 13:02:07 +0100:
SP> Not that it's to much help, but I've seen a similar issue with Excel
SP> files. I never really found a solution other than having the files on
SP> the SQLServer. I've also tried with various accounts that has full
SP> admin access to the server, domain, local machine etc. but to no avail.
SP> I'd be happy to know the solution/reason since it's a bit annoying that
SP> I have to put the files on the SQLServer to make it work.
the only good news is that, as I've found, it works correctly with SQL
Server 2005.
Vadim
|||Hello Sue:
You wrote in conference
microsoft.public.sqlserver.security,microsoft.publ ic.sqlserver.server on
Tue, 18 Jan 2005 16:11:38 -0700:
SH> Yes...but you still need to check the permissions - the
SH> whole ldb thing. And you need to make sure the permissions
SH> are explicitly set. Logging on and starting access and
SH> opening the database manually is not the same thing.
hmm... if I open the database manually, obviously, Access is creating the
ldb... thus, it can do it... How is it not the same thing?
And it looks like in sql server 2005 it works just fine.
Vadim
|||SQL Server does not start up Access and then open up an mdb.
It accesses the mdb.
Just like it's different if you double click a file vs. open
an application and then do a File, Open to open the file.
-Sue
On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
<vr@.myrealbox.nospam.com> wrote:

>Hello Sue:
>You wrote in conference
>microsoft.public.sqlserver.security,microsoft.pub lic.sqlserver.server on
>Tue, 18 Jan 2005 16:11:38 -0700:
> SH> Yes...but you still need to check the permissions - the
> SH> whole ldb thing. And you need to make sure the permissions
> SH> are explicitly set. Logging on and starting access and
> SH> opening the database manually is not the same thing.
>hmm... if I open the database manually, obviously, Access is creating the
>ldb... thus, it can do it... How is it not the same thing?
>And it looks like in sql server 2005 it works just fine.
>Vadim
|||Vadim,
That last example wasn't a good one. Nonetheless, SQL Server
doesn't start Access and then open a database.
Other than security issues, combinations of MDAC/Jet drivers
can also cause problems and you may want to check those. If
you feel certain that this is a bug in SQL Server, you can
open a case with product support. You will not be charged
for the incident if it is a bug.
-Sue
On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
<vr@.myrealbox.nospam.com> wrote:

>Hello Sue:
>You wrote in conference
>microsoft.public.sqlserver.security,microsoft.pub lic.sqlserver.server on
>Tue, 18 Jan 2005 16:11:38 -0700:
> SH> Yes...but you still need to check the permissions - the
> SH> whole ldb thing. And you need to make sure the permissions
> SH> are explicitly set. Logging on and starting access and
> SH> opening the database manually is not the same thing.
>hmm... if I open the database manually, obviously, Access is creating the
>ldb... thus, it can do it... How is it not the same thing?
>And it looks like in sql server 2005 it works just fine.
>Vadim
|||one thing that worked for me on loading dumps from UNCs is that i had
to use an absolute UNC path and not the share name.
for example:
if i had a share named "share" on folder X on my C drive
rather than going to //myComputer/share
i had to go to //myComputer/C$/X
and everything worked fine...it is worth a shot.
hth,
hans
Sue Hoegemeier wrote:
> Vadim,
> That last example wasn't a good one. Nonetheless, SQL Server
> doesn't start Access and then open a database.
> Other than security issues, combinations of MDAC/Jet drivers
> can also cause problems and you may want to check those. If
> you feel certain that this is a bug in SQL Server, you can
> open a case with product support. You will not be charged
> for the incident if it is a bug.
> -Sue
> On Sat, 22 Jan 2005 23:24:46 -0600, "Vadim Rapp"
> <vr@.myrealbox.nospam.com> wrote:
>
>microsoft.public.sqlserver.security,microsoft.pub lic.sqlserver.server
on[vbcol=seagreen]
creating the[vbcol=seagreen]