Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Wednesday, March 21, 2012

Error 80004005 on launching DTS

Hi all. I have just migrated our DWH environment from one server to another, from a named instance to another one. When I run the DTS it works fine, but when I launch it by using a job (running dtsrun) it fails with the following error:

DTSRun: Loading... Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.

What can be the cause of this? thanks a lot.Do you mean a real job within sql server or are you using dtsrun as a command-line utility ?|||Originally posted by rnealejr
Do you mean a real job within sql server or are you using dtsrun as a command-line utility ?

I have a job with several steps. Each step is a call to DTSRUN, specifying user, password and DTS name. I have tried to run other DTSs: they work fine, but if I try to launch the job from any step it fails. My SQLAgent service is logged by using a domain admin user.|||Who is the owner of the job and what access does this user have within sql server ? Your connection object in the dts package - what are you using for the server name and type of authentification ?|||Originally posted by rnealejr
Who is the owner of the job and what access does this user have within sql server ? Your connection object in the dts package - what are you using for the server name and type of authentification ?

The job is owned by SA, and the connection object uses OLEDB Provider for SQL Server. The server name is "COLBTADWH02\DWH_DESA", given it is a named instance.|||Authentication is by SQL Server, using SA.|||Was this job/package part of the migration as well ?|||Originally posted by rnealejr
Was this job/package part of the migration as well ?

Yes, the job and the package existed in the original environment. It was migrated via GenerateScript, and then the script was edited to change the <server\instance> name.|||What happens if you create a new job for the same package ? What is the access level of the account that is running agent - also, have you tried to use sa instead of the domain account ?|||Originally posted by rnealejr
What happens if you create a new job for the same package ? What is the access level of the account that is running agent - also, have you tried to use sa instead of the domain account ?

I have already tried entire job deletion and recreation. Just moments ago, another scheduled job (created by scheduling a DTS) was launched and it worked fine. The agent-running account is a domain admin, and also a local admin.|||I just tried the following: scheduled the first step of the job (a call to DTSRUN) , which created a job. I launched this new job and it worked well. What can be different so a DTS-created job works and a manually created job does not?|||I finally solved the problem by installing SQL SP2, but I still would like to know what caused the error. I think it is not safe to fix this kind of problems only by updating/reinstalling software.

Sunday, March 11, 2012

Error 62 When connecting with SSMS to a SQL Server 2000 named instance

Hello,

I get error 62 when trying to connect to a SQL Server 2000 named instance from SQL Server Management Studio. I can register and connect to other SQL Server 2000 instances

I've tried all the usual stuff, including enabling all the protocols from SQL Server configuration Manager.

Any thoughts. Your help is very appreciated.

Thanks

Kevin Lobo

Can you post the whole error msg? Is this a local or remote connection? What's the Service Pack of your SQL Server 2000? Make sure sql browser is on if you can. Also make sure sql browser and/or udp port 1434 is in exception list if you firewall is on.

Thanks,
Xinwei

So, actually error 26, not 62.

|||

Hello Xinwei,

Thanks. It is working now. The Browser was running but the firewall setting was on with 'Don't allow exceptions' checked. I unchecked it and its ok now.

many thanks.

Jut FYI, here is the entire error message:

An error has occured while establishing a connection to the server. When connecting to SQL Server
2005, the failure may be casued by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error 26 - Error locating Server/Instance
Specified) (Microsoft SQL Server)

Sunday, February 26, 2012

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/
Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in t
he
> \LOG folder. Plenty of space on the backup drive, running out on the T-Lo
g
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
>> Got a weird one...
>> I have 20 databases on one SQL 2000 sp4, .2187 instance.
>> I also have a backup database and backup log script that I run, which
>> enumerates the datbase list and runs a backup for each one.
>> One specific database errors, while the ones before and after it succeed.
>> It used to work just fine, no changes (especially since I can pinpoint
>> the failure time to 5:50am, and I know nobody was fooling with the server
>> at that time).
>> The error is 3013 - "Backup terminating abnormally" (not the verbatim
>> error). Error happens for full backup and t-log.
>> I cannot backup manually through QA or Enterprise manger either. Nor can
>> I backup to a different location one the same or different drives...
>> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
>> the \LOG folder. Plenty of space on the backup drive, running out on the
>> T-Log drive...
>> Help?
>> Thanks,
>> Kevin Hill
>> 3NF Consulting
>> http://kevinbhill.powweb.com/NewsGroups.htm
>> My random SQL Server encounters:
>> http://kevin3nf.blogspot.com/
>>
>>
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Everything else has failed, so we aer using DTS to send everything to a new
database...
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Friday, February 24, 2012

Error 2812 Could not Find Stored Procedure msdb.dbo.sp_add_jobstep_internal

Getting this error when trying to create an instance as a Publisher.
SQL Server 2000 SP4
reinstalled SP4 and that doesn't help
Error 2812 Could not Find Stored Procedure
msdb.dbo.sp_add_jobstep_internalProbably the easiest solution is to reinstall sp4 (on distributor, publisher
then subscriber). It might be possible to selectively install the
replication scripts but we don't know what else didn't install correctly
(possibly some info in the sp install log file for this) so I'd simply
reinstall sp4 as the simplest way out.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Error 2812 Could not Find Stored Procedure msdb.dbo.sp_add_jobstep_internal

Getting this error when trying to create an instance as a Publisher.
SQL Server 2000 SP4
reinstalled SP4 and that doesn't help
Error 2812 Could not Find Stored Procedure
msdb.dbo.sp_add_jobstep_internal
Probably the easiest solution is to reinstall sp4 (on distributor, publisher
then subscriber). It might be possible to selectively install the
replication scripts but we don't know what else didn't install correctly
(possibly some info in the sp install log file for this) so I'd simply
reinstall sp4 as the simplest way out.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Error 2812 Could not Find Stored Procedure msdb.dbo.sp_add_jobstep_internal

Getting this error when trying to create an instance as a Publisher.
SQL Server 2000 SP4
reinstalled SP4 and that doesn't help
Error 2812 Could not Find Stored Procedure
msdb.dbo.sp_add_jobstep_internalProbably the easiest solution is to reinstall sp4 (on distributor, publisher
then subscriber). It might be possible to selectively install the
replication scripts but we don't know what else didn't install correctly
(possibly some info in the sp install log file for this) so I'd simply
reinstall sp4 as the simplest way out.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Error 26 on a local machine

I am getting the "Error Locating Server/Instance Specified" message. The part I find most confusing is that I am connecting to my database locally. I have read the recommendations on the blog posted here:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx


and implemented them to no avail. The confusing part is that I only have this problem on one particular application, which I am not the original author of. When I build my connection to the very same server (different database) using the Data Source configuration wizard, it works just fine. Any help would be greatly appreciated.

I have the same error and did the same thing according to your link. Thx.

|||

You said everything is fine except one application which you don't originally own. Can you post the connection string used by the application? Are you able to connect to the same server using SQL Management Studio? Are you app using .Net, SNAC(sqlncli), or MDAC? Thanks.

|||

I must ask your forgiveness. I realize now that I there were two connection strings. One for regular database usage, the other for Session state, it seems. After changing the other I am able to connect to my local one. Thank you for your reply.

Error 26 on a local machine

I am getting the "Error Locating Server/Instance Specified" message. The part I find most confusing is that I am connecting to my database locally. I have read the recommendations on the blog posted here:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx


and implemented them to no avail. The confusing part is that I only have this problem on one particular application, which I am not the original author of. When I build my connection to the very same server (different database) using the Data Source configuration wizard, it works just fine. Any help would be greatly appreciated.

I have the same error and did the same thing according to your link. Thx.

|||

You said everything is fine except one application which you don't originally own. Can you post the connection string used by the application? Are you able to connect to the same server using SQL Management Studio? Are you app using .Net, SNAC(sqlncli), or MDAC? Thanks.

|||

I must ask your forgiveness. I realize now that I there were two connection strings. One for regular database usage, the other for Session state, it seems. After changing the other I am able to connect to my local one. Thank you for your reply.

Wednesday, February 15, 2012

Error 21002 : User already exists

Running SQL Server 2000 Enterprise SP3a ( Windows Server 2003 )
I restored several databases from one instance ( on another box ) to another
. Now I am trying to add the users
to the second box ( to duplicate those on the first ) where I restored the d
ata and I am getting this error when
trying to add the database permissions for the user.
I tried working with sp_change_users, but the report shows nothing ( no rows
returned ) .
I tried deleting user using sp_droplogin, it dropped the user, but same thin
g happened again
once I readded him. I also tried the sp_change_users_login ( autofix) to no
avail ( nothing happened )
Any help would be appreciated.
ThanksRun select * from sysusers in the database that you are trying to add the
user. If the user does exist then run the sp_granddbaccess procedure to
grant access to the user. You may then need to run sp_change_users_login
again after verifying that the login exists for this user.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||That response should hav been sp_grantdbaccess.
Rand
This posting is provided "as is" with no warranties and confers no rights.