Replication Job Failed. Unable To Determine The Owner
Jun 5, 2007
A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:
SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).
How can I fix this? I looked under the Replication folder but didn't see anything.
View 4 Replies
ADVERTISEMENT
Jun 14, 2007
My compatibility settings are fine. Anyone know how to to this?
View 4 Replies
View Related
Oct 31, 2007
Hi All,
Can someone please advise.
I am trying to change the database owner. I am logged in as sa.
I am using the command sp_changedbowner 'username'
I seem to get the following error message:
Cannot find the principal 'username', because it does not exist or you do not have permission.
I have created the user account. But am still getting the same error.
View 5 Replies
View Related
Jun 19, 2015
I have a periodic backup task, and when I need a development copy on which to test code, I restore my most recent backup to a different name, switch the ODBC link to that name on my development machine and have a current copy of the database to play with.
I've been doing this for years, and it works great. Just now I did it, and suddenly my development machine is unable to run any stored procedures that have the 'Execute as owner' clause in their definition. I'm using domain accounts, my personal account is the owner of the database, and everything works on the production copy, which is in the same instance on the same machine.
The test copy is identical to the production copy, which continues to work fine - it was just created using by restoring the backup of the production copy, but I can't run anything with this clause. As soon as I delete the 'Execute as owner' line, the procedure is suddenly available. If I put it back, I'm locked out again.
The error message is: The server principal “sa” is not able to access the database “WhateverDB” under the current security context
View 5 Replies
View Related
Jul 22, 2015
One of our databases has at some point in its dark past had the owner of the guest schema changed to be a named user, rather than the default guest user. Correcting this feels like it would be easy enough by running the following...
ALTER AUTHORIZATION ON SCHEMA::guest TO guest
but that results in..
Msg 15150, Level 16, State 2, Line 3
Cannot alter the schema 'guest'.
I realise the guest schema is a special one, and cannot be dropped, but I'm not trying to do that. End goal is to export the database to a SQL Azure DB, and this guest schema assignment is blocking that process from completing.
View 4 Replies
View Related
Dec 29, 2014
I'm looking for feedback on a query I've devised to return a numeric value if the 3 most recent executions of a job have failed. The purpose of the query is to server as a custom counter alert for Idera SQL DM, and by definition an SQL Script alert must return a numeric value.
My environment is SQL Server 2008. Note that the job name is hard coded.
;WITH CTE_Restore_JobHistory AS
(SELECT h.[job_id]
,j.[name] as JobName
,h.[message]
,h.[run_status]
[Code] .....
View 2 Replies
View Related
Nov 23, 1999
Ray or Someone please help!
I have not aliased pager as dbo. Are you suggesting to try this? I want the replicated tables to show a db owner of 'pager'. Here is another description of my situation (I think the first one may have been confusing):
I have a Database named Page with 'sa' as the db owner. The objects (tables and sps) of this database have the owner 'pager'. This is the way the database is defined on the Publication and Subscription Servers. But, when the replication process is completed, the replicated tables on the Subscription Server have the owner 'dbo'. I want my replicated tables on my Subscription Server to have the owner 'pager'. So, that the 4 replicated tables will have the same db owner as the existing tables on the Page Database.
Is this happening because I have the NT trusted connection which points to 'sa' on the SQL Server? If so, can I change the trusted connection to point to 'pager'? I am just guessing at this point. I will continue to research this issue. Someone has suggested that I go into EM, Manage Logins, select 'pager', and put 'dbo' in the Alias column for the replicated database (Page Db) row. I will try this.
Thanks in advance, Kevin
-----------
If you alias pager as dbo, the object created by pager will show owner of dbo. This is the way sql6.5 works, but sql7 will show pager as owner.
------------
Kevin G. at 11/22/99 5:14:22 PM
I am in the process of replicating a table within a workgroup setup (not a Domain).
I notice that when the table is created on the Subscription Server the replication process is creating the tables with a db owner of (dbo). I want the tables to be created with 'pager' as the owner. 'pager' is already defined as a db owner in the source and destination database. In the Publication Server Source Database, 'pager' is the owner of the tables selected for replication.
How can I accomplish this? Currently, I am doing the following on both the Publication and Subscriber Servers: logging on NT as 'Administrator' and starting both services (MSSQLServer and SQLExecutive) with the 'sqlnt2' NT Login which is a member of the NT Administrators Group. The NT Administrators Group has been trusted to SQL Server on both machines.
I am using the NT4.0, SP3 and SQL Server 6.5 with SP5a.
Thanks in advance, Kevin
View 1 Replies
View Related
Sep 13, 2007
Hi,I have transactional replication set up on on of our MS SQL 2000 (SP4)Std Edition database serverBecause of an unfortunate scenario, I had to restore one of thepublication databases. I scripted the replication module and droppedthe publication first. Then did a full restore.When I try to set up the replication thru the script, it created thepublication with the following error messageServer: Msg 2714, Level 16, State 5, Procedure SYNC_FCR ToGPRPTS_GL00100, Line 1There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in thedatabase.It seems the previous replication has set up these system viewsSYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replicationmodule again to see if it drops the views but it didn't.The replication fails with some wired error & complains about thisviews when I try to run the synch..I even tried running the sp_removedbreplication to drop thereplication module, but the views do not seem to disappear.My question is how do I remove these system views or how do I make thereplication work without using these views or create new views.. Whyis this creating those system views in the first place?I would appreciate if anyone can help me fix this issue. Please feelfree to let me know if any additional information or scripts needed.Thanks in advance..Regards,Aravin Rajendra.
View 2 Replies
View Related
Sep 28, 2007
We are currently testing a Replication topology as follows:
SQL Server 2005 Developer as publisher and distributor of a push updatable transaction replication
2 SQL Server 2005 Express clients as subscribers.
The replication is working great. If the connection is lost, the subscribers switch from Immediate to Queued Updating, and seem to shift back to Immediate when they regain the connection.
My question is to determine if there is a way that I can ask SQL Express on the client which mode is it currently running, or ask SQL Express if it has a current live connection to the distributor.
I know that they are usually mutliple ways to accomplish tasks, and I would be open any suggestions, preferrable programming in VB (such as with SMO or RMO) or using stored procedures or functions.
I hope this give some people something to chew on during the weekend and thank you to all that have taking the time to read this.
View 5 Replies
View Related
Jun 15, 2007
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
View 3 Replies
View Related
May 12, 2015
i have a sql server job scheduled to run daily twice.the job is running fine , but once or twice a week the job fails saying."Message Unable to connect to SQL Server '(local)'. The step failed." all other times the job runs successfully. it randomly the job is failing. once its failed and if i try to run it manually it runs fine or it will start running fine from next schedule onwards.This job mainly executes a stored procedure.the owner of the job is setup as sa. i don't understand why its fail randomly and all other times(90% of cases) it successful."Unable to connect to SQL Server '(local)'. The step failed."
View 2 Replies
View Related
Feb 22, 2007
Ran the SP2 locally on a Windows Server 2003 SP1 box that had SQL Server 2005 SP1 install on it. Problem was I ran out of C: drive and it failed in the middle of upgrading the server.
I'm unable to start the SQL Server at all now. Is there any way to back this out? Don't think I can reapply any patches since the service is dead.
Eventlog now shows:
One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
The log shows it's unable to start SQL (blames it on permisions but it's because SQL can no longer start)
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmssqlsystemresource1.mdf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
I'm guessing its reinstall time but not sure how the attached databases will like that idea.
Thanks in advance for any ideas.
View 6 Replies
View Related
Aug 25, 2000
My problem is the following: when I try to configure replication between two SQL servers, I get an error message even before I get a chance to configure anything. When I choose "Configuring publishing and subscribers" (in Enterprise Man.) I receive the following error message: "SQL Server Enterprise Manager could not complete the wizard because @@SERVERNAME is for " is NULL. Use sp_addserver to set @@SERVERNAME".
When I try to do this I get the message that the name already exists...
Something is obviously wrong with this server, but I can't pinpoint the problem, much less resolve it - I would very much appreciate any help!!
Regards / Per
View 4 Replies
View Related
Dec 17, 1998
I have 2 machines JAWS (publisher/distributor) and PSG (subscriber) on
trusted domains. MSSQL & SQLExec services of both machines run under the
local NT Administrator account
username: Administrator
password: XXXX
this NT Administrator account has the same username and password on both
machines. Their network protocols are named pipes. After I set up
replication following the sql manual, the LogReader, Distribution and Sync
tasks all report the error "unable to connect to JAWS". I'm wondering what
else I need to do. Any help are greatly appreciated. Thanks,
-Hoang
View 1 Replies
View Related
Aug 22, 2007
Hi,
I created and scheduled a test snapshot publication and a push subscription using the sql server replication wizard. Tested it and it worked all fine as the data was regularly replicated to the destination server correctly.
After I was satisfied with the test I deleted the replication and subscription without any problem. But I noticed that the jobs created by the replication wizard had not been deleted. I was disappointed as I had also expected these to be deleted because there are no more any local publication or replication on the server.
I, then, tried to delete the job by right click - and then delete. But I am unable to delete the pubilcation and subscription jobs at all. When I try to delete the sql server 2005 the following error message appears:
--start--------------------------------------------------------------------
"Attempt to retrieve data failed for object for server <MYSERVER>" (Microsoft.SqlServer.Smo
)
Addional Information
The job <jobname> does not exist on the server. (Microsoft.SqlServer.Smo)
--End--------------------------------------------------------------------
Can anyone help me on how to delete all replication jobs.
View 1 Replies
View Related
May 7, 2015
Recently we rebuilt one of the cluster node (due to some issues with SP), where distribution agent resource or instance was running after rebuilding that node, we failed over distribution resource to that (newly built) node and after that log reader agent jobs were in suspended status. After checking the job history, we got the below error "Unable to start execution of step 2 (reason: The LogReader subsystem failed to load [see the file for details]; The job has been suspended). The step failed."After getting lot of search did not get exact solution which matches to the environment
View 3 Replies
View Related
Nov 13, 2015
I have some issue when replicating a view (transactional replication).I have following objects on publisher:
Table: [Metadataschema].[Entity]
View: [dbo].[EntityLogicalView]
the view definition is:
create view [dbo].[EntityLogicalView] as (SELECT * FROM [Entity] WHERE OverwriteTime = 0)
this is what I get when I run "Script View as Create". The same query is used by the replication.Unfortunately this query fails on the subscriber "Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber". I cannot even runt his query manually on the subscriber, it only works when I change it like this:create view [dbo].[EntityLogicalView] as (SELECT * FROM [Metadataschema].[Entity] WHERE OverwriteTime = 0) Is there any way to get this working? Can I change the creation scripts used by the replication or force publisher to include schema names in all objects?
View 5 Replies
View Related
Sep 7, 2007
We are using SQL Server 2005 64 bit standard edition on both ends (subscriber distributor and publisher ) publisher is its own distributor. Now i want to investigate the replication performance and delayed in replication for this purpose i found that tracer tokens can be settedup but when i open replication monitor but unable to see tracer token tab.
Plz let me know something.why i am unable to see this tab, is there some problem of rights ? , permission, or installtion.
View 2 Replies
View Related
Feb 18, 2006
Hi All
I am getting this error during Merge Replication "Unable to synchronize the row because the row was updated by a different process outside of replication."
I could not reproduce this error in my development enviornment, can anyone tell me what is cause of the above error and how do I reproduce this error in my development machine? I am able to get which is outside process?
The Conflict Type is 10 for above error which is logged into Conflict Table.
Thanks
View 11 Replies
View Related
Nov 27, 2006
Hi,
I`m trying to setup our sql2000 sp3a sql server as a Publisher.When i use the wizard to config Publishing and Distribution wizard. I recieve the following error:
Sql Enterprise manager could not configure server as the distributor. Error 14133 Could not execute instdist.sql. Check instdist.out in the install directory.
I`ve checked the install directory and cannot find the file instdist.out file. I assume that it failed before completeing this stage.
Has anyone come across this error before and any ideas on how to resolve would be appreciated.
Thanks in Advance,
Steve
View 1 Replies
View Related
Apr 1, 2008
we had a failure on our Publishing SQL Server (2000)
now the distribution agents are marked inactive and must be re-initialized. How do I do this?
View 2 Replies
View Related
Nov 10, 1999
Now, I am getting closer and receiving the following message in the Distribution Task (repl_subcriber is the owner, AutoStart is the Frequency):
"37000[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed - User: Reason: Not Associated with a trusted SQL Server connection."
I have 'sqlexecutivent' and 'pswd' defined on the CA (Publisher) and VA (Subscriber) Servers. I have 'sqlexecutivent' defined in the NT Administrator group on both machines. I have trusted the NT Administrator group to SQL Server on both machines (xp_grantlogin 'administrator', 'admin'). I have trusted the NT 'sqlexecutivent' login to SQL Server on both machines (xp_grantlogin 'sqlexecutivent', 'admin'). I have logged-in to both NT machines using the 'sqlexecutivent' login and 'pswd'. I have started the MSSQLServer Service and SQLExecutive Service using 'sqlexecutivent' and 'pswd'. When I set up the Topology, Publication, and Subscription I was registerred in SEM as 'sa'. I do not know if this is needed, but in SQL Server I also created 'sqlexecutive' logins and 'sqlexecutive' database users on both machines.
Please tell me what I am missing. Do I need to do anything with the repl_subscriber and repl_publisher login ids? Do I need to configure a DSN? Do I need to check anything in the registry? Maybe I need to just start over again with a fresh start by uninstalling the Replication Topology, Publishing, etc. Maybe I should try Multi-Protocol.
Again, these are two NT 4.0, SP3 machines running SQL Server 6.5 SP5a. They are set up in the same Workgroup. I can connect to both machines in SEM and by Mapping a Network Drive. The default netlibrary is set to named pipes.
As part of my appreciation for your efforts, I will document this process and mail it to you once it is working.
Thanks, Kevin
View 2 Replies
View Related
Oct 18, 1999
I have been attempting to set up replication between two 6.5 servers in the same domain, and all I get is a login failed error on my replication task. Both servers use standard security and an admin login for the server and exec service, and I am using the default remote server setup as installed with replication. I'm sure it will be something simple, but I can't see it.
Thanks in advance for any help you can offer.
View 2 Replies
View Related
Nov 21, 2006
Hi Guys im newbie but need to learn more of it so please cooperate with me and slolve my problem.
my Sql Server starts merging and it starts dumping the scema and data after some time it the status shows failed, it doesn't give any error message also. please let me know what to check and how to resolve this.
View 4 Replies
View Related
Nov 23, 2005
Hi everybody,
View 1 Replies
View Related
Aug 14, 2007
Hi..
I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.
At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.
I hope some body out there can explain something to me and how to overcome the problem...
View 6 Replies
View Related
Sep 11, 2006
Hi All,
We have a SQL server 2000 merge replication and it has been running for couple of years. We were even fine too at the beginning after upgraded our publisher SQL Server 2000 to SQL Server 2005. Now we are starting have problems. I just found there were two files seem to be too big, MSmerge_genhistory.bcp (1,830,287K) and MSmerge_genhistory90.bcp (1,977,746K). I have no idea why these two files are so big.
My questions are:
1. Why these two files? (we do have a mix of SQL Server 2000 MSDE and SQL Server 2005 Express as the subscribers)
2. Can (Should) I clean the MSmerge_genhistory table? How?(sp_mergemetadataretentioncleanup)
3. What could be the impact to all the existing subscribers if I clean this table?
Thank you for your help.
Yong
View 1 Replies
View Related
Feb 5, 2001
Hi all,
I hope someone who knows how to fix the following problem could shed some light:
I have set up a two-way transactional replication between two SQL 7.0 servers. The updates and inserts on server A is successfully replicated to server B. But when I tried to test if changes on server B is replicated onto server A, I got a 'login failed for user 'sa'' when I modified a user table. It sounds strange because I already logged in using 'sa' and all SQL servers use the same 'sa' login. I wonder if it is a Microsoft bug. The same problem happened on a pair of SQL 2000 Enterprise servers.
Thanks for any input.
Richard
View 1 Replies
View Related
May 11, 2004
Transactional replication running via a pull subscription between a single subscriber and single publisher on Windows 2000 servers (all current service packs and patches) with SQL Server 2000.
Early on Sunday morning, the server hosting the publisher was rebooted...but SQL Server Agent failed to start fully, causing the log reader agent to not start and no alerts to trigger. Still trying to isolate the cause of the problem with SQL Server Agent, as it's been problematic to keep it up and running. For the most part, though, it's coming up properly after restarts of the service or reboots, and starting all agents/functions.
However, the snapshot agent ran a number of times pulling schema and batch copies for the articles in the replicated dataset, and the distribution agent now fails each time it runs with a reference to "not having the initial snapshot for the publication available". SQL Server Agent went down before this could complete, and I left it down until I could ascertain the best route to take...
Any chance I can circumvent having to reapply a initial snapshot of the publication db (this is a large set of data), and just apply transactions from the log since my downtime has only been about 60 hours? Or is there an agent setting, job run to reinitialize, or an inherent quality to SQL Server Agent that will demand a complete reapplication of the snapshots due to the down time?
I'm betting that the distribution agent will start moving data as soon as the snapshot agent finishes up (as I said, it has not completed yet), but I'm praying there's a way to get around this...
Thanks!
View 1 Replies
View Related
Oct 2, 2015
What are the different options for setting up Alerts when Replication stops or errors out?
I ran this code on the publisher:
USE [msdb]
GO
/****** Object: Alert [Replication: agent failure] Script Date: 10/2/2015 11:42:46 AM ******/
EXEC msdb.dbo.sp_add_alert @name=N'Replication: agent failure',
@message_id=14151,
@severity=0,
@enabled=0,
[Code] ....
It already existed.
So I ran it on the Subscriber and it executed.
Are there any third party tools to do this?
View 1 Replies
View Related
Mar 29, 2007
I have two databases A & B which have a merge replication between them. Both are live data. I wanted to alter table in db A, so i deleted subscription and altered the table from db A. After that i rebuilt the replication between A & B with initialization but now my replication fails. Every time i get different error messages..recently i get message of 'Subscriber failed to initialize'. Could anyone suggest how to resolve this? Urgent please.
View 4 Replies
View Related
Sep 6, 2006
I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.
Any suggestions would be greatly appreciated!
Thanks!
View 1 Replies
View Related
