Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC call
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.
This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error 15633

Hi
I get this error on my Full-Text population job
Full-text auto propagation is currently enabled for
table '[dbo].[tablename]'. [SQLSTATE 42000] (Error 15633
Does anyone have any idea on this ?
There is not information on Net on this, so your input
will be highly appreciated.
Thanks
Thyagu
Thyagu,
Can I assume you are using SQL Server 2000? Could you post the full output
of SELECT @.@.version -- as this can be very helpful in understanding SQL
FTS issues.
For your table "tablename", is Change Tracking enabled?
Regards,
John
"thaygu" <pgthyagu@.hotmail.com> wrote in message
news:b45801c4374c$120ed2a0$a501280a@.phx.gbl...
> Hi
> I get this error on my Full-Text population job
> Full-text auto propagation is currently enabled for
> table '[dbo].[tablename]'. [SQLSTATE 42000] (Error 15633
> Does anyone have any idea on this ?
> There is not information on Net on this, so your input
> will be highly appreciated.
> Thanks
> Thyagu

Error 11 in Agent Job

We're getting an error message ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11). The step failed.
when running an agent job which updates from one Database to another but still on the same server. If we run the job from T-SQL it works fine. Eventually though the service degenerates and we can't run the job as either an agent or a T-SQL script and we h
ave to re-build the server.
Any ideas what would cause this problem and how we can rectify it?
Please check your Server network utilities. Make sure that TCP/IP and Named
pipes values are not blank by clicking on the Properties.
thanks.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||We have extensively tested the server and found the problem to be with a third party piece of software, Backup EXEC. Once this is removed the agent job fires fine.
"akcsl" wrote:

> We're getting an error message ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11). The step failed.
> when running an agent job which updates from one Database to another but still on the same server. If we run the job from T-SQL it works fine. Eventually though the service degenerates and we can't run the job as either an agent or a T-SQL script and we
have to re-build the server.
> Any ideas what would cause this problem and how we can rectify it?
>

Error 11 in Agent Job

We're getting an error message ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11). The step failed.
when running an agent job which updates from one Database to another but still on the same server. If we run the job from T-SQL it works fine. Eventually though the service degenerates and we can't run the job as either an agent or a T-SQL script and we have to re-build the server.
Any ideas what would cause this problem and how we can rectify it?Please check your Server network utilities. Make sure that TCP/IP and Named
pipes values are not blank by clicking on the Properties.
thanks.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

error : 'QUOTED_IDENTIFIER, ARITHABORT'

I have an error like this :
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed
because the following SET options have incorrect
settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Can anyone explain to me ? what does it means ?
How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
ThanksI assume this is from a maint plan job?
You have computed columns or views with indexes on them, and you are trying to reorganize the data.
Unfortunately the main wiz doesn't execute the correct SET command for its connection, meaning that
it can't rebuild using DBCC DBREINDEX. You can create a TSQL job yourself from where you specify the
appropriate SET commands and then execute DBCC DBREINDEx (or DBCC INDEXDEFRAG).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Kresna Rudy K" <kresnark@.yahoo.com> wrote in message
news:1ad0401c387e3$55b5a740$a601280a@.phx.gbl...
> I have an error like this :
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed
> because the following SET options have incorrect
> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> Can anyone explain to me ? what does it means ?
> How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
> Thanks|||It's true , this error came from maintainence plan job,
but I still don't understand because I don't use view or
computed column with indexes, I use standart version of
sql 2000, this version doesnot support index view.
Please explain to me,
Thx Tibor.
>--Original Message--
>I assume this is from a maint plan job?
>You have computed columns or views with indexes on them,
and you are trying to reorganize the data.
>Unfortunately the main wiz doesn't execute the correct
SET command for its connection, meaning that
>it can't rebuild using DBCC DBREINDEX. You can create a
TSQL job yourself from where you specify the
>appropriate SET commands and then execute DBCC DBREINDEx
(or DBCC INDEXDEFRAG).
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Kresna Rudy K" <kresnark@.yahoo.com> wrote in message
>news:1ad0401c387e3$55b5a740$a601280a@.phx.gbl...
>> I have an error like this :
>> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
>> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
failed
>> because the following SET options have incorrect
>> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>> Can anyone explain to me ? what does it means ?
>> How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
>> Thanks
>
>.
>|||Nothing stop you from creating an index on a computed column or a view in standard edition. Try and
you will see:
USE pubs
GO
CREATE view v with schemabinding
as select au_id, au_lname from dbo.authors
GO
create unique clustered index ix on v(au_id)
You can try below to see if you have indexes in view. Run in each database:
select * from sysobjects where type = 'V'
and objectproperty(id, 'IsIndexed') = 1
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"kresna rudy k" <kresnark@.yahoo.com> wrote in message
news:1aeb201c387f2$0aed5ff0$a601280a@.phx.gbl...
> It's true , this error came from maintainence plan job,
> but I still don't understand because I don't use view or
> computed column with indexes, I use standart version of
> sql 2000, this version doesnot support index view.
> Please explain to me,
> Thx Tibor.
>
> >--Original Message--
> >I assume this is from a maint plan job?
> >
> >You have computed columns or views with indexes on them,
> and you are trying to reorganize the data.
> >Unfortunately the main wiz doesn't execute the correct
> SET command for its connection, meaning that
> >it can't rebuild using DBCC DBREINDEX. You can create a
> TSQL job yourself from where you specify the
> >appropriate SET commands and then execute DBCC DBREINDEx
> (or DBCC INDEXDEFRAG).
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
> >
> >"Kresna Rudy K" <kresnark@.yahoo.com> wrote in message
> >news:1ad0401c387e3$55b5a740$a601280a@.phx.gbl...
> >> I have an error like this :
> >>
> >> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934:
> >> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> failed
> >> because the following SET options have incorrect
> >> settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
> >>
> >> Can anyone explain to me ? what does it means ?
> >>
> >> How to setting 'QUOTED_IDENTIFIER, ARITHABORT'
> >>
> >> Thanks
> >
> >
> >.
> >

Error

receiving error during backup.

Microsoft SQL-DMO (ODBC SQLState: 42000)

The media set for database '%' has 2 family members but only 3 are provided. All members must be provided. BACKUP DATABASE is terminating abnormally.

You might want to check your backup device definition. Remember that you can't mix a multi-file device with a single file device.