Hello,
I am having trouble with creating a linked server (as simple as it should
be).
My Setup:
Server A: runs under a specific account, the account can be delegated, I
have used setspn on this machine (as per BOL), I have also created a linked
server to Server B (mapping each user context as they connect)
Server B: runs under the same account (which can be delegated), I have not
used setspn as I only want people to connect remotely from Server A.
If I log onto Server A, run a query like select * from
serverb.database.owner.table everything runs fine, I can connect remotely,
now, here is the hitch:
I work on Client machine C, when I try and run the same query that worked on
server A, I get:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
What am I doing wrong?
Appreciate any insight into this
Malcolm.Mapping each user context to what? Sounds like the users are
authenticated using their Windows credentials and mapping is
set to their credentials so for their AD accounts, the
setting for:
Account is sensitive and cannot be delegated
needs to be turned off or deselected.
The server also needs to be trusted for delegation.
You also need to check your protocols and listening ports.
The books online article:
Security Account Delegation
has all of the requirements. If you are running on SP3 or
higher, make sure you are referencing the updated help
topic. You can also find it here:
http://msdn.microsoft.com/library/d...>
ity_2gmm.asp
-Sue
On Tue, 8 Nov 2005 12:21:17 -0500, "Malcolm Klotz"
<nonesuch23@.online.nospam> wrote:
>Hello,
>I am having trouble with creating a linked server (as simple as it should
>be).
>My Setup:
>Server A: runs under a specific account, the account can be delegated, I
>have used setspn on this machine (as per BOL), I have also created a linked
>server to Server B (mapping each user context as they connect)
>Server B: runs under the same account (which can be delegated), I have not
>used setspn as I only want people to connect remotely from Server A.
>If I log onto Server A, run a query like select * from
>serverb.database.owner.table everything runs fine, I can connect remotely,
>now, here is the hitch:
>I work on Client machine C, when I try and run the same query that worked o
n
>server A, I get:
>Msg 18452, Level 14, State 1, Line 1
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>What am I doing wrong?
>Appreciate any insight into this
>Malcolm.
>|||Hello,
To narrow down the issue, I suggest that you perform the following steps:
1. I assume both servers are SQL server 2000. If not, please provide more
detailed information about the linked server.
2. Set boh SQL server startup accounts to be a Domain account. Use SA to
connect to the SQL server A from the client, then check the issue again.
If it works fine, the cause is related to Security Account Delegation. If
so, please continue with the following steps:
3. Follow the steps on the following web site to set Delegation
Security Account Delegation
<http://msdn.microsoft.com/library/d...n-us/adminsql/a
d_security_2gmm.asp>
Run the "setspn -l" to verify it. For example, if you create an SPN for SQL
Server:
setspn -A MSSQLSvc/w2k3sqlsp4.test.com:1433
test\administrator
You can verify it by running
setspn -l test\administrator
It will return:
Registered ServicePrincipalNames for
CN= administrator, CN=users, DC=test, DC=com:
MSSQLSvc/envm-w2k3entsp1.test.com:1061
MSSQLSvc/w2k3sqlsp4:1433
MSSQLSvc/w2k3sqlsp4.test.com:1433
Please post here how you create the SPN for SQL Server and the results of
the "setspn -l".
4. Refer to the following article to troublshoot the issue:
http://support.microsoft.com/?id=319723#1
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you, this worked, I had used the wrong port for one of my instances.
Much appreciated.
Malcolm
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:O4UWYKR5FHA.1240@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> To narrow down the issue, I suggest that you perform the following steps:
> 1. I assume both servers are SQL server 2000. If not, please provide more
> detailed information about the linked server.
> 2. Set boh SQL server startup accounts to be a Domain account. Use SA to
> connect to the SQL server A from the client, then check the issue again.
> If it works fine, the cause is related to Security Account Delegation. If
> so, please continue with the following steps:
> 3. Follow the steps on the following web site to set Delegation
> Security Account Delegation
> <[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a[/ur
l]
> d_security_2gmm.asp>
> Run the "setspn -l" to verify it. For example, if you create an SPN for
> SQL
> Server:
> setspn -A MSSQLSvc/w2k3sqlsp4.test.com:1433
> test\administrator
> You can verify it by running
> setspn -l test\administrator
> It will return:
> Registered ServicePrincipalNames for
> CN= administrator, CN=users, DC=test, DC=com:
> MSSQLSvc/envm-w2k3entsp1.test.com:1061
> MSSQLSvc/w2k3sqlsp4:1433
> MSSQLSvc/w2k3sqlsp4.test.com:1433
> Please post here how you create the SPN for SQL Server and the results of
> the "setspn -l".
> 4. Refer to the following article to troublshoot the issue:
> http://support.microsoft.com/?id=319723#1
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Monday, March 19, 2012
Friday, March 9, 2012
server Yields Inconsistent results
On SQL Server 2000 we are connecting to many AS/400 tables using Linked
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?I'm still looking for assistance on this issue. I thought as a Universal
Subscriber that Managed newsgroup submissions received a timely response.
Any support would be greatly appreciated. Thanks
"LisaConsult" wrote:
> On SQL Server 2000 we are connecting to many AS/400 tables using Linked
> Servers. We are developing a process which runs solely on SQL using Store
d
> Procedures. We are finding inconsistent results in the return of a query
> utilizing a linked table. The query:
> Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
> RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
> SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
> dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
> CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
> ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
> end,
> f.RVOPT, p.PSDESC, p.PFORMN
> FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
> on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
> c.BasePlanCode
> WHERE c.RecordStatus = 5
> And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
> On a given record, the join may result in 5 records, but if you run the sa
me
> query without any data changes or SP changes may result in 3 records. Nex
t
> time 5, etc. We did a test of pulling the AS/400 tables down to SQL Serve
r
> and began getting consistent results everytime. We see no error messages
in
> SQL Server logs. Any thoughts?
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?I'm still looking for assistance on this issue. I thought as a Universal
Subscriber that Managed newsgroup submissions received a timely response.
Any support would be greatly appreciated. Thanks
"LisaConsult" wrote:
> On SQL Server 2000 we are connecting to many AS/400 tables using Linked
> Servers. We are developing a process which runs solely on SQL using Store
d
> Procedures. We are finding inconsistent results in the return of a query
> utilizing a linked table. The query:
> Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
> RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
> SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
> dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
> CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
> ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
> end,
> f.RVOPT, p.PSDESC, p.PFORMN
> FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
> on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
> c.BasePlanCode
> WHERE c.RecordStatus = 5
> And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
> On a given record, the join may result in 5 records, but if you run the sa
me
> query without any data changes or SP changes may result in 3 records. Nex
t
> time 5, etc. We did a test of pulling the AS/400 tables down to SQL Serve
r
> and began getting consistent results everytime. We see no error messages
in
> SQL Server logs. Any thoughts?
server Yields inconsistent results
On SQL Server 2000 we are connecting to many AS/400 tables using Linked
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?Are you using sp_executesql with any params?
I noticed in-correct results when doing this from MSSQL to AS400.
Tim S|||We are in Query Analyzer, executing a storedprocedure which contains this
query. Any clues or resolutions would be appreciated.
"Tim" wrote:
> Are you using sp_executesql with any params?
> I noticed in-correct results when doing this from MSSQL to AS400.
> Tim S
>|||Hi Lisa,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your results from Linked Server is
less than you expected randomly. If I have misunderstood your concern,
please feel free to point it out.
First of all, please double confirm that records are the same in original
database,I mean nobody else is updating the records. If so, It is really
strange when the result will be 3 records and then 5 records in the next
one.
Secondly, would you please help me collect more detailed scenario
information by answering the questions below?
- What's your database in AS/400? Is it IBM DB2?
- Does your network or AS/400 endure a high workload?
- Does the database in AS/400 is case sensitive?
- What is the OLE DB driver you are using?
Thirdly, please perform the steps below and let me know whether it will
make any contribution to your issue
1) Have you upgraded to the latest SQL Server 2000 service pack? We have
released SQL Server 2000 SP4 recently and you could download it here
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
2) Please try using OPENQUERY instead of SELECT it from four part name
direcly
3) Please ensure the query will get the correct information while execute
in database of AS/400 directly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:1F4Tyu3VFHA.3052@.TK2MSFTNGXA01.phx.gbl...
> 1) Have you upgraded to the latest SQL Server 2000 service pack? We have
> released SQL Server 2000 SP4 recently and you could download it here
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
How about "next to latest SQL Server 2000 service pack"? SP 4 has an
outstanding issue or two that might affect you. SP 3a might be your best
bet in a production environment.|||Hi Michael,
Thanks for your post.
Yes my fault, I should have mentioned SP4 has an known issue now with AWE
for more than 2 GB memory, you may have noticed that we have such note in
the download page
Important Note: Microsoft has found an issue with the final build of SP4
that impacts customers who run SQL Server with Address Windowing Extensions
(AWE) support enabled. This issue only impacts computers with more than two
gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
have this configuration, you should not install SP4. Microsoft is currently
working on the problem and will issue an update soon.
Our SQL Development is working on a public hotfix package for this fix.
This will take longer to have the right tests done and get this properly
released with the hotfix installer. As stated in KB below this problem is
specific to customers that use AWE. The problem limits the amount of
physical memory that SQL Server can use for data cache. The bug only allows
SQL Server to use at maximum 50% of the physical memory in the server. You
can observe this behavior by looking at various perfmon counters including
SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
this value can be up to the amount of physical memory on the computer, but
with SP4 it will never be more than 50% of physical RAM.
Refer the Knowledge Base article for more detailed information
BUG: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/kb/899761
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I've read that the hotfix will be available in approximately 7 days (I read
this on 5/16). Is there any update if it will be released soon?
Thanks
"Michael Cheng [MSFT]" wrote:
> Hi Michael,
> Thanks for your post.
> Yes my fault, I should have mentioned SP4 has an known issue now with AWE
> for more than 2 GB memory, you may have noticed that we have such note in
> the download page
> Important Note: Microsoft has found an issue with the final build of SP4
> that impacts customers who run SQL Server with Address Windowing Extension
s
> (AWE) support enabled. This issue only impacts computers with more than tw
o
> gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
> have this configuration, you should not install SP4. Microsoft is currentl
y
> working on the problem and will issue an update soon.
> Our SQL Development is working on a public hotfix package for this fix.
> This will take longer to have the right tests done and get this properly
> released with the hotfix installer. As stated in KB below this problem is
> specific to customers that use AWE. The problem limits the amount of
> physical memory that SQL Server can use for data cache. The bug only allow
s
> SQL Server to use at maximum 50% of the physical memory in the server. You
> can observe this behavior by looking at various perfmon counters including
> SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
> this value can be up to the amount of physical memory on the computer, but
> with SP4 it will never be more than 50% of physical RAM.
> Refer the Knowledge Base article for more detailed information
> BUG: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/kb/899761
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi,
Thanks for your question.
Unfortunately, I am afraid here is no hotfix available now. If it is ready,
we will find the hotfix in RESOLUTION section in KB article 899761.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Servers. We are developing a process which runs solely on SQL using Stored
Procedures. We are finding inconsistent results in the return of a query
utilizing a linked table. The query:
Insert into #tmpTableData(ControlID, ApplicationID, RVTBL, RVCNY, RVSTA,
RVPLN, PlanEffDt,PlanEndDt, RVOPT, PSDESC, PFORMN)
SELECT c.ControlID, c.ApplicationID, f.Field1, f.RVCNY, f.RVSTA, f.RVPLN,
dbo.udf_DTStr_FromDecimalMMDDYYYY (f.RVEFMM,f.RVEFDD,f.RVEFYY),
CASE When LEN(RTRIM(p.PLUSR6)) <> 0 Then cast(p.PLUSR6 as varchar(8))
ELSE Replace(convert(char(10) ,getdate() ,102) , '.' , '')
end,
f.RVOPT, p.PSDESC, p.PFORMN
FROM ( [Prod].LSPFCT.ABCTABLE f inner join [Prod].LSPFCT.PDFTABLE p
on f.RVPLN = p.PPLAN) inner join tblControlData c on f.FIELD1 =
c.BasePlanCode
WHERE c.RecordStatus = 5
And (f.RVSTA = '**' or f.RVSTA = c.IssueState)
On a given record, the join may result in 5 records, but if you run the same
query without any data changes or SP changes may result in 3 records. Next
time 5, etc. We did a test of pulling the AS/400 tables down to SQL Server
and began getting consistent results everytime. We see no error messages in
SQL Server logs. Any thoughts?Are you using sp_executesql with any params?
I noticed in-correct results when doing this from MSSQL to AS400.
Tim S|||We are in Query Analyzer, executing a storedprocedure which contains this
query. Any clues or resolutions would be appreciated.
"Tim" wrote:
> Are you using sp_executesql with any params?
> I noticed in-correct results when doing this from MSSQL to AS400.
> Tim S
>|||Hi Lisa,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood your results from Linked Server is
less than you expected randomly. If I have misunderstood your concern,
please feel free to point it out.
First of all, please double confirm that records are the same in original
database,I mean nobody else is updating the records. If so, It is really
strange when the result will be 3 records and then 5 records in the next
one.
Secondly, would you please help me collect more detailed scenario
information by answering the questions below?
- What's your database in AS/400? Is it IBM DB2?
- Does your network or AS/400 endure a high workload?
- Does the database in AS/400 is case sensitive?
- What is the OLE DB driver you are using?
Thirdly, please perform the steps below and let me know whether it will
make any contribution to your issue
1) Have you upgraded to the latest SQL Server 2000 service pack? We have
released SQL Server 2000 SP4 recently and you could download it here
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
2) Please try using OPENQUERY instead of SELECT it from four part name
direcly
3) Please ensure the query will get the correct information while execute
in database of AS/400 directly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:1F4Tyu3VFHA.3052@.TK2MSFTNGXA01.phx.gbl...
> 1) Have you upgraded to the latest SQL Server 2000 service pack? We have
> released SQL Server 2000 SP4 recently and you could download it here
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
How about "next to latest SQL Server 2000 service pack"? SP 4 has an
outstanding issue or two that might affect you. SP 3a might be your best
bet in a production environment.|||Hi Michael,
Thanks for your post.
Yes my fault, I should have mentioned SP4 has an known issue now with AWE
for more than 2 GB memory, you may have noticed that we have such note in
the download page
Important Note: Microsoft has found an issue with the final build of SP4
that impacts customers who run SQL Server with Address Windowing Extensions
(AWE) support enabled. This issue only impacts computers with more than two
gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
have this configuration, you should not install SP4. Microsoft is currently
working on the problem and will issue an update soon.
Our SQL Development is working on a public hotfix package for this fix.
This will take longer to have the right tests done and get this properly
released with the hotfix installer. As stated in KB below this problem is
specific to customers that use AWE. The problem limits the amount of
physical memory that SQL Server can use for data cache. The bug only allows
SQL Server to use at maximum 50% of the physical memory in the server. You
can observe this behavior by looking at various perfmon counters including
SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
this value can be up to the amount of physical memory on the computer, but
with SP4 it will never be more than 50% of physical RAM.
Refer the Knowledge Base article for more detailed information
BUG: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/kb/899761
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I've read that the hotfix will be available in approximately 7 days (I read
this on 5/16). Is there any update if it will be released soon?
Thanks
"Michael Cheng [MSFT]" wrote:
> Hi Michael,
> Thanks for your post.
> Yes my fault, I should have mentioned SP4 has an known issue now with AWE
> for more than 2 GB memory, you may have noticed that we have such note in
> the download page
> Important Note: Microsoft has found an issue with the final build of SP4
> that impacts customers who run SQL Server with Address Windowing Extension
s
> (AWE) support enabled. This issue only impacts computers with more than tw
o
> gigabytes (2 GB) of memory where AWE has been explicitly enabled. If you
> have this configuration, you should not install SP4. Microsoft is currentl
y
> working on the problem and will issue an update soon.
> Our SQL Development is working on a public hotfix package for this fix.
> This will take longer to have the right tests done and get this properly
> released with the hotfix installer. As stated in KB below this problem is
> specific to customers that use AWE. The problem limits the amount of
> physical memory that SQL Server can use for data cache. The bug only allow
s
> SQL Server to use at maximum 50% of the physical memory in the server. You
> can observe this behavior by looking at various perfmon counters including
> SQL Server:Memory Manager/Total Server Memory (KB). On an SP3 SQL Server
> this value can be up to the amount of physical memory on the computer, but
> with SP4 it will never be more than 50% of physical RAM.
> Refer the Knowledge Base article for more detailed information
> BUG: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/kb/899761
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi,
Thanks for your question.
Unfortunately, I am afraid here is no hotfix available now. If it is ready,
we will find the hotfix in RESOLUTION section in KB article 899761.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
server VFPOLEDB gives Access Denied error
When I login to the windows server as administrator, the query runs. When I
login as anyone else (incl a user with as many admin rights as I can give
him), I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "VFPOLEDB" for linked server "A" reported an error.
Access denied.
Msg 7301, Level 16, State 2, Line 1
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
provider "VFPOLEDB" for linked server "A".
Any help would be appreciated."Ashley Brewerton" <AshleyBrewerton@.discussions.microsoft.com> wrote in
message news:800A97D6-2A65-4A2C-A746-56A4D4931C2A@.microsoft.com...
Hi Ashley,
Be sure you have the latest FoxPro and Visual FoxPro OLE DB data provider,
downloadable from msdn.microsoft.com/vfoxpro/downloads/updates .
Here's what works for me to set up the Linked Server in SQL 2005 using the
Linked Server dialog:
Providers list: VFPOLEDB shows as an entry
Linked Servers > New Linked Server ...
Linked Server: MyLinkedServer
Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
Product name: Visual FoxPro (I think this is optional)
Data source: "C:\Program Files\Microsoft Visual
FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
spaces in the string.)
Provider string: VFPOLEDB.1
Location: (blank)
Catalog: (blank)
Security page and Server Options page take defaults.
> When I login to the windows server as administrator, the query runs. When
> I
> login as anyone else (incl a user with as many admin rights as I can give
> him), I get the following error:
What permissions does the SQL Server local system account have?
I'm ok on my laptop with the SQL Server started with "local
system account" and my Windows login being MachineName\Cindy. When I tried
against my SQL Express instance which was started using the "NT
AUTHORITY\NetworkService" I had the same errors you report.
> Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
> provider "VFPOLEDB" for linked server "A".
How are you executing your query? With the four-part naming or using
OpenQuery()?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com|||Hi Cindy
Yes, I saw your previous post and have already tried the setup you
indicated. I run the query using the standard select syntax::
select * from AURORA...CMaster
"Cindy Winegarden" wrote:
> "Ashley Brewerton" <AshleyBrewerton@.discussions.microsoft.com> wrote in
> message news:800A97D6-2A65-4A2C-A746-56A4D4931C2A@.microsoft.com...
> Hi Ashley,
> Be sure you have the latest FoxPro and Visual FoxPro OLE DB data provider,
> downloadable from msdn.microsoft.com/vfoxpro/downloads/updates .
> Here's what works for me to set up the Linked Server in SQL 2005 using the
> Linked Server dialog:
> Providers list: VFPOLEDB shows as an entry
> Linked Servers > New Linked Server ...
> Linked Server: MyLinkedServer
> Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
> Product name: Visual FoxPro (I think this is optional)
> Data source: "C:\Program Files\Microsoft Visual
> FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
> spaces in the string.)
> Provider string: VFPOLEDB.1
> Location: (blank)
> Catalog: (blank)
> Security page and Server Options page take defaults.
> > When I login to the windows server as administrator, the query runs. When
> > I
> > login as anyone else (incl a user with as many admin rights as I can give
> > him), I get the following error:
> What permissions does the SQL Server local system account have?
> I'm ok on my laptop with the SQL Server started with "local
> system account" and my Windows login being MachineName\Cindy. When I tried
> against my SQL Express instance which was started using the "NT
> AUTHORITY\NetworkService" I had the same errors you report.
> > Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
> > provider "VFPOLEDB" for linked server "A".
> How are you executing your query? With the four-part naming or using
> OpenQuery()?
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy_winegarden@.msn.com www.cindywinegarden.com
>
>
login as anyone else (incl a user with as many admin rights as I can give
him), I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "VFPOLEDB" for linked server "A" reported an error.
Access denied.
Msg 7301, Level 16, State 2, Line 1
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
provider "VFPOLEDB" for linked server "A".
Any help would be appreciated."Ashley Brewerton" <AshleyBrewerton@.discussions.microsoft.com> wrote in
message news:800A97D6-2A65-4A2C-A746-56A4D4931C2A@.microsoft.com...
Hi Ashley,
Be sure you have the latest FoxPro and Visual FoxPro OLE DB data provider,
downloadable from msdn.microsoft.com/vfoxpro/downloads/updates .
Here's what works for me to set up the Linked Server in SQL 2005 using the
Linked Server dialog:
Providers list: VFPOLEDB shows as an entry
Linked Servers > New Linked Server ...
Linked Server: MyLinkedServer
Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
Product name: Visual FoxPro (I think this is optional)
Data source: "C:\Program Files\Microsoft Visual
FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
spaces in the string.)
Provider string: VFPOLEDB.1
Location: (blank)
Catalog: (blank)
Security page and Server Options page take defaults.
> When I login to the windows server as administrator, the query runs. When
> I
> login as anyone else (incl a user with as many admin rights as I can give
> him), I get the following error:
What permissions does the SQL Server local system account have?
I'm ok on my laptop with the SQL Server started with "local
system account" and my Windows login being MachineName\Cindy. When I tried
against my SQL Express instance which was started using the "NT
AUTHORITY\NetworkService" I had the same errors you report.
> Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
> provider "VFPOLEDB" for linked server "A".
How are you executing your query? With the four-part naming or using
OpenQuery()?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com|||Hi Cindy
Yes, I saw your previous post and have already tried the setup you
indicated. I run the query using the standard select syntax::
select * from AURORA...CMaster
"Cindy Winegarden" wrote:
> "Ashley Brewerton" <AshleyBrewerton@.discussions.microsoft.com> wrote in
> message news:800A97D6-2A65-4A2C-A746-56A4D4931C2A@.microsoft.com...
> Hi Ashley,
> Be sure you have the latest FoxPro and Visual FoxPro OLE DB data provider,
> downloadable from msdn.microsoft.com/vfoxpro/downloads/updates .
> Here's what works for me to set up the Linked Server in SQL 2005 using the
> Linked Server dialog:
> Providers list: VFPOLEDB shows as an entry
> Linked Servers > New Linked Server ...
> Linked Server: MyLinkedServer
> Provider: Choose "Microsoft OLE DB Provider for Visual FoxPro
> Product name: Visual FoxPro (I think this is optional)
> Data source: "C:\Program Files\Microsoft Visual
> FoxPro9\Samples\Northwind\Northwind.dbc" (Include quotes since there's
> spaces in the string.)
> Provider string: VFPOLEDB.1
> Location: (blank)
> Catalog: (blank)
> Security page and Server Options page take defaults.
> > When I login to the windows server as administrator, the query runs. When
> > I
> > login as anyone else (incl a user with as many admin rights as I can give
> > him), I get the following error:
> What permissions does the SQL Server local system account have?
> I'm ok on my laptop with the SQL Server started with "local
> system account" and my Windows login being MachineName\Cindy. When I tried
> against my SQL Express instance which was started using the "NT
> AUTHORITY\NetworkService" I had the same errors you report.
> > Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB
> > provider "VFPOLEDB" for linked server "A".
> How are you executing your query? With the four-part naming or using
> OpenQuery()?
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy_winegarden@.msn.com www.cindywinegarden.com
>
>
Subscribe to:
Posts (Atom)