Error 7410 when doing a SELECT from a Link table in xp_sendmail

Really would appreciate some advice on this problem. I have a cluster, CORPUSGA and a stand alone server CORPUSAPP22. CORPUSAPP22 has a linked server set up to CORPUSGA using 'sa' as the security context. Within a stored procedure I am running a SELECT to CORPUSGA.msdb.dbo.sysjobs.

When this is run from Query Analyzer it is fine and runs under the 'dbo' security context, but when is is run under xp_sendmail that uses the SQL Agent's security context (a domain account called
IntServiceGA) it fails with this message:

ODBC error 7410 (42000) Remote access not allowed for Windows NT user activated by SETUSER.

For the following command:

exec master.dbo.xp_sendmail
@.recipients = 'stelzner_eve@.emc.com;dabas_ravi@.emc.com;bergin_gi llian@.emc.com;lynch_eoin@.e
mc.com;sherman_ nancy@.emc.com',
@.message = @.email,
@.query = @.query_text,
@.no_header = 'true',
@.width=80,
@.subject = 'Job Failed on CORPUSGA ',
@.attach_results = 'true',
@.set_user = 'dbo'

Where @.query_text is something like "select * from CORPUSGA.msdb.dbo.sysjobs"

The IntServiceGA account is identical on both servers and is in the local administrators group on both servers and is in the system administrators role within SQL Server, has access to the database and sysjobs has granted permissions to IntServiceGA (SELECT, INSERT,UPDATE,DELETE).

When I run profiler against this, it tries to execute under IntServiceGA (an Windows authentication account) and then tries to SETUSER to sa . This is what it objects to the switching. I have tried to set up the IntServiceGA as the security context for the linked server too and this does not work, same error.

Any help would be great,
Thanks,
EveWhy do you need @.set_user if SQLAgent service account is already in sysadmin server role?|||I have another stored procedure that uses this and it works with the
@.set_user on this one. However, whether I leave it in or take out the
@.set_user parameter it still fails. Any ideas?

Thanks,
Eve|||Try to run your xp_sendmail after doing SETUSER 'DOMAIN_NAME\IntServiceGA' and see what you get.|||no go, using the SETUSER prior to the xp_sendmail still netted the
same results? Do you know what generates this message- NT or SQL?|||It's NT. It just proved that your SQLAgent account is lacking some rights. Was mail profile setup using SQLAgent service account?|||Yes, the profile was set up on both servers from the
corp\IntServiceGA account that is a local admin on
the both servers. Are there additional policies that need
to be put on for this account that are not in the default?

Error 7399 When trying to link an Access database to SqlServer 2K

Hi,
I'm trying to add an Access Database as a linked server to an SqlServer 2000
SP4. Both the server and the access database run on the same PC. The Access
database is protected by a Database password. It is no workgroup password
involved.
After a lot of testing with Visual Basic 6 ADO connection strings I reach to
the following string that is able to open the password protected database by
using VB:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
But when using this string in the definition of the linked server in the
Enterprise Manager I get the following error when trying to browser the
tables of the linked server:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
I tryed both running the SqlServer as local system account and as a Windows
domain account with domain admin priviledges.
I found also the article http://support.microsoft.com/kb/814398 that
describes a similar problem but that solution did not worked for me.
Any hint is welcomed
Thanks in advance
SammyHi Sammy
You may want to check through http://ask.support.microsoft.com/kb/306518/
Have you checked if the dropping the password from the database works?
You may want to see if moving the database and the security database to a
different directory helps.
John
"SammyBar" wrote:

> Hi,
> I'm trying to add an Access Database as a linked server to an SqlServer 20
00
> SP4. Both the server and the access database run on the same PC. The Acces
s
> database is protected by a Database password. It is no workgroup password
> involved.
> After a lot of testing with Visual Basic 6 ADO connection strings I reach
to
> the following string that is able to open the password protected database
by
> using VB:
> "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
> But when using this string in the definition of the linked server in the
> Enterprise Manager I get the following error when trying to browser the
> tables of the linked server:
> Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> I tryed both running the SqlServer as local system account and as a Window
s
> domain account with domain admin priviledges.
> I found also the article http://support.microsoft.com/kb/814398 that
> describes a similar problem but that solution did not worked for me.
> Any hint is welcomed
> Thanks in advance
> Sammy
>
>

Error 7399 When trying to link an Access database to SqlServer 2K

Hi,
I'm trying to add an Access Database as a linked server to an SqlServer 2000
SP4. Both the server and the access database run on the same PC. The Access
database is protected by a Database password. It is no workgroup password
involved.
After a lot of testing with Visual Basic 6 ADO connection strings I reach to
the following string that is able to open the password protected database by
using VB:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
But when using this string in the definition of the linked server in the
Enterprise Manager I get the following error when trying to browser the
tables of the linked server:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
I tryed both running the SqlServer as local system account and as a Windows
domain account with domain admin priviledges.
I found also the article http://support.microsoft.com/kb/814398 that
describes a similar problem but that solution did not worked for me.
Any hint is welcomed
Thanks in advance
Sammy
Hi Sammy
You may want to check through http://ask.support.microsoft.com/kb/306518/
Have you checked if the dropping the password from the database works?
You may want to see if moving the database and the security database to a
different directory helps.
John
"SammyBar" wrote:

> Hi,
> I'm trying to add an Access Database as a linked server to an SqlServer 2000
> SP4. Both the server and the access database run on the same PC. The Access
> database is protected by a Database password. It is no workgroup password
> involved.
> After a lot of testing with Visual Basic 6 ADO connection strings I reach to
> the following string that is able to open the password protected database by
> using VB:
> "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
> But when using this string in the definition of the linked server in the
> Enterprise Manager I get the following error when trying to browser the
> tables of the linked server:
> Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> I tryed both running the SqlServer as local system account and as a Windows
> domain account with domain admin priviledges.
> I found also the article http://support.microsoft.com/kb/814398 that
> describes a similar problem but that solution did not worked for me.
> Any hint is welcomed
> Thanks in advance
> Sammy
>
>

Error 7399 When trying to link an Access database to SqlServer 2K

Hi,
I'm trying to add an Access Database as a linked server to an SqlServer 2000
SP4. Both the server and the access database run on the same PC. The Access
database is protected by a Database password. It is no workgroup password
involved.
After a lot of testing with Visual Basic 6 ADO connection strings I reach to
the following string that is able to open the password protected database by
using VB:
"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
But when using this string in the definition of the linked server in the
Enterprise Manager I get the following error when trying to browser the
tables of the linked server:
Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
I tryed both running the SqlServer as local system account and as a Windows
domain account with domain admin priviledges.
I found also the article http://support.microsoft.com/kb/814398 that
describes a similar problem but that solution did not worked for me.
Any hint is welcomed
Thanks in advance
SammyHi Sammy
You may want to check through http://ask.support.microsoft.com/kb/306518/
Have you checked if the dropping the password from the database works?
You may want to see if moving the database and the security database to a
different directory helps.
John
"SammyBar" wrote:
> Hi,
> I'm trying to add an Access Database as a linked server to an SqlServer 2000
> SP4. Both the server and the access database run on the same PC. The Access
> database is protected by a Database password. It is no workgroup password
> involved.
> After a lot of testing with Visual Basic 6 ADO connection strings I reach to
> the following string that is able to open the password protected database by
> using VB:
> "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program
> Files\AccessDB\mydatabase.mdb;Jet OLEDB:Database Password=xxxx"
> But when using this string in the definition of the linked server in the
> Enterprise Manager I get the following error when trying to browser the
> tables of the linked server:
> Error 7399: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> I tryed both running the SqlServer as local system account and as a Windows
> domain account with domain admin priviledges.
> I found also the article http://support.microsoft.com/kb/814398 that
> describes a similar problem but that solution did not worked for me.
> Any hint is welcomed
> Thanks in advance
> Sammy
>
>

Error 7347

We are getting Error 7347 error while querying via link server to Sybase. No
w this error is produced only in case of few tables. Query for other tables
is fine. There is another link server to the same sybase server but to a dif
ferent database and that it
fine.
Any help is appreciated
Here is the complete error message
****************************************
Server: Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'Sybase.ASEOLEDBProvider' returned an unexpected data length
for the fixed-length column '[pds].[pds].[dbo].[product].cu
stodian_code'. The expected data length is 15, while the returned data lengt
h is 4.
OLE DB error trace [Non-interface error: Unexpected data length returne
d for the column: ProviderName='Sybase.ASEOLEDBProvider', TableName='[p
ds].[pds].[dbo].[product]', ColumnName='custodian_code', Expecte
dLength='15', ReturnedLength='4'].Hi,
////
The IDENTITY function should be used only when the SELECT statement has an
INTO clause.
Explanation:
Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
////
The sybase manual gives this explanation for the Error number 7347.I dont
know what query u are firing onto the server but just check if u are missing
something specified in the explanation
regards
Dilish
"Nishu" <anonymous@.discussions.microsoft.com> wrote in message
news:A98F91AB-9EFB-4F31-9281-2407BB0D2BE7@.microsoft.com...
> We are getting Error 7347 error while querying via link server to Sybase.
Now this error is produced only in case of few tables. Query for other
tables is fine. There is another link server to the same sybase server but
to a different database and that it fine.
> Any help is appreciated
>
> Here is the complete error message
> ****************************************
> Server: Msg 7347, Level 16, State 1, Line 1
> OLE DB provider 'Sybase.ASEOLEDBProvider' returned an unexpected data
length for the fixed-length column
'[pds].[pds].[dbo].[product].custodian_code'. The expected d
ata length is
15, while the returned data length is 4.
> OLE DB error trace [Non-interface error: Unexpected data length returned[/col
or]
for the column: ProviderName='Sybase.ASEOLEDBProvider',
TableName='[pds].[pds].[dbo].[product]', ColumnName='custodi
an_code',
ExpectedLength='15', ReturnedLength='4'].

Error 7303 Could not initialize data source object of OLE DB provi

I am trying to link to an AS400 server. When I set up the link I am getting
Error 7303 Could not initialize data source object of OLE DB provider.
I know that there are problably parameters that I need to add to the
connection but am not sure where to start. Can someone help me troubleshoot
this issue?
Install Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to the AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Fri, 14 Oct 2005 08:22:11 -0700, Linda Ibarra
<LindaIbarra@.discussions.microsoft.com> wrote:

>I am trying to link to an AS400 server. When I set up the link I am getting
>Error 7303 Could not initialize data source object of OLE DB provider.
>I know that there are problably parameters that I need to add to the
>connection but am not sure where to start. Can someone help me troubleshoot
>this issue?

Error 7303 Could not initialize data source object of OLE DB provi

I am trying to link to an AS400 server. When I set up the link I am getting
Error 7303 Could not initialize data source object of OLE DB provider.
I know that there are problably parameters that I need to add to the
connection but am not sure where to start. Can someone help me troubleshoot
this issue?Install Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to the AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Fri, 14 Oct 2005 08:22:11 -0700, Linda Ibarra
<LindaIbarra@.discussions.microsoft.com> wrote:

>I am trying to link to an AS400 server. When I set up the link I am getting
>Error 7303 Could not initialize data source object of OLE DB provider.
>I know that there are problably parameters that I need to add to the
>connection but am not sure where to start. Can someone help me troubleshoot
>this issue?

Error 3409 when trying to link to SQL Server table

Hi,
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09=A0pm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns fro=m
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to thi=s
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We ha=ve
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote:
> > Hi,
> >
> > We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> >
> > Recently we made database changes where we deleted a number of columns from
> > the highest level table in our database hierarchy (every other table is
> > either a child or grandchild of this table).
> >
> > Since we did that we can no linker establish links from Access 2003 to this
> > table. When we try, we get the following error message:
> >
> > Invalid field definition <STAMP1> in definition of index or relationship.
> > (Error 3409)
> >
> > STAMP1 is our Primary Key field.
> >
> > None of the fields we deleted were index fields, and none were keys. We have
> > been racking our brains trying to find the issue but to no avail. Please
> > help. Thank you.

Error 3409 when trying to link to SQL Server table

Hi,
We are using SQL Server 2000 (latest SP) on Windows Server 2003.
Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).
Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:
Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)
STAMP1 is our Primary Key field.
None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.
A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.
Let me know what you find out.
-Sean
On Feb 29, 1:09Xpm, Berean <Ber...@.discussions.microsoft.com> wrote:
> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||Hi Sean,
The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.
We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.
"Berean" wrote:

> Hi,
> We are using SQL Server 2000 (latest SP) on Windows Server 2003.
> Recently we made database changes where we deleted a number of columns from
> the highest level table in our database hierarchy (every other table is
> either a child or grandchild of this table).
> Since we did that we can no linker establish links from Access 2003 to this
> table. When we try, we get the following error message:
> Invalid field definition <STAMP1> in definition of index or relationship.
> (Error 3409)
> STAMP1 is our Primary Key field.
> None of the fields we deleted were index fields, and none were keys. We have
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
|||We recently tried rebuilding and renaming all indexes, and are receiving the
same error.
To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.
"Berean" wrote:
[vbcol=seagreen]
> Hi Sean,
> The effect is happening when anyone tries to link to the SQL Server table,
> whether the link was preexisting or not. Even new link attempts generate the
> same error.
> We have tried rebuilding the indexes on SQL Server and even tried making a
> dummy table with the data but no indexes. We could link to the dummy but not
> to the one with indexes.
> "Berean" wrote: