Msg 22026, Level 16, State 1, Line 0
The enlist operation failed (reason: SQLServerAgent Error: The target server cannot establish an encrypted connection to the master server 'MSXSERVERINSTANCE'. Make sure that the MsxEncryptChannelOptions registry subkey is set correctly on the target server.)
I did check the registry key (on all servers) and all of them have MsxEncryptChannelOptions set to the default of 2 (used this link as a guide - http://msdn.microsoft.com/en-us/library/ms365379.aspx).
I have setup the server MYMSXSERVERINSTANCE as the master and currently have 5 targets. This error occurs when I attempt to enlist the 6th server as a target.
TSXSERVERS1-3 are 'nonproduction' level machines used for development and testing of our software. TSXSERVER4-5 are production servers (TSXSERVER5 is actually on an active/passive cluster and is the virtual name). TSXSERVER6 is a server that houses a day old copy of our production data for reporting purposes.
Now, TSXSERVER6 is the odd one here. It's a new server where we are pushing replicated data to for reporting purposes. Aside from the version of SQL Server being for 32-bit and 64-bit the only other difference is the OS:
MSXSERVER - Microsoft(R) Windows(R) Server 2003, Enterprise Edition
TSXSERVER1-3 - Microsoft(R) Windows(R) Server 2003, Standard Edition
TSXSERVER4-5 - Microsoft(R) Windows(R) Server 2003, Enterprise Edition
TSXSERVER6 - Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Has anyone ran into a situation like this? The obvious thing that comes to mind is that I might not be able to have a 64-bit version of SQL Server be a target to a 32-bit version of SQL Server. But I have been unable to locate any documentation stating this either way. Any suggestions on what to look at next... or better yet if you know the answer already let me know! :)
Step 1. First I am filtering the Sales Order information and inserting it in my Sales Orders table. Step 2.Then I am filtering the details from the sales Order and inserting them in the respective table.
My Problem is that the Sales Order File does not contain the Sales Order key (ID), this is generated by the SQL Server. How can get it in order to use it in the second step? I need it because it is a foreign key in the details table.
I'm looking for a way to list the target servers associated with a master server. The reason is that we're moving to another master server, and I'd prefer not to move the targets manually.
I've got most of the T-SQL already (sp_msx_enlist, sp_add_jobserver), but I'd like a scripted solution instead of a wizard.
Sql Server 7 Standard EditionMy Server was renamed and the normal steps of reinstallingand running sp_dropserver and sp_addserver were followed.Everything seems to work fine but jobs from the master server.I did defect the server as a target server since it appeared as offlineanyway.On trying to re establish the status of the server as a target serverFailed to make "serverName" a target serverEnlist into Master Server "MasterServerName" Failed(Error 14262)Your insight is appreciatedVincento
I need to investigate about what happened to our production server at the last weekend.i restored it to another server which is development. I restored it under a name "old_master_2015_07_10".
But if I run a query
SELECT * FROM [old_master_2015_07_10].[sys].[servers]
it actually selects from master.sys.servers, not from my old_master... In order to prove it, I created a linked server in this, development server, and if I run SELECT * FROM [old_master_2015_07_10].[sys].[servers], it selects it. And in database selection drop-down box I also selected old_ master_ 2015_07_10. What I think it apparently recognizes familiar names like sys.servers and redirects the query to the master.
What I can do to select really from old_master_2015_07_10 database? I already thought about renaming sys.servers to something different, but did not do it not to break something in master in case if SQL Server will run it in master as well.
Hi,We are planning to create a prod environment on our Dev server, bycreating a new named instance on DEV. Our prod server is running onsql enterprise edition 64bit and dev on SQl enterprise 32bit.Could we copy all the databases from prod server includingMaster,msdb,model onto our dev server, and bring up all the databases?Does Master store information about the version of SQl server?Thanks for your helpGG
I have never done this in a DR scenario before. What I used to do in SQL Server 2000 was apply the logins to a new installation of SQL 2000 then recover the application databases. I'm using 2005 now and I'm in a different mode where I would like to be able to recover the system (master, model, msdb) to a different server with the same SQL Server 2005 build ---- 9.0.3054. I'm following the procedures from Microsoft where they state to place the instance in single user mode first then invoke SQLCMD then perform the restore. Sounds simple enough. C:> SQLCMD > RESTORE DATABASE MASTER from DISK = 'Z:MINIDRmaster_backup_200804200315.bak'
The console is coming back with a message that the backup set holds a backup other than the existing master database. So I suppose that this cannot be done and is only intended for recovery on the same instance.
So, I'm looking into using an MSX/TSX setup to help manage and monitor jobs, etc.
I took two test boxes and set one up as a Master and one as a Target and got it working...was able to push a job out and it ran and reported back, etc.
So, that's all great, but this was one small limited test. I'm curious to know if there are any gotchas that some of you have experienced that you would be willing to share with me to help prevent me from experiencing the same issues, etc.
I have about 40 instances that I'm considering using this MSX/TSX setup with, the remaining 15 instances would be monitored by something like Quest. Can a single MSX handle jobs on 40 instances? I already have maintenance plans and jobs set up on all the remote servers. Is there a way to transfer their ownership up to the MSX so they can be monitored from there? So far I haven't seen a way to do that.
*ponders*
Actually, one thing I just realized is that I could set up a job that looked for failed jobs. If I pushed that job out to all the TSX servers that could be used to alert me that something failed on a TSX box. That would actually be a great way to do it the more I think about it...Can anyone think of a reason why that is a bad idea?
I have a full backup from ServerA. I then put ServerB in single user mode and try to restore the backup from ServerA. (both are identical servers but have different names)
[*- From command prompt using sqlcmd -*]
USE master GO RESTORE DATABASE master FROM DISK = 'D:BACKUPSserverA.bak' GO
Msg 3154, Level 16, State 4, Server MSSQL1, Line 1 The backup set holds a backup of a database other than the existing 'master' database.
Msg 3013, Level 16, State 1, Server MSSQL1, Line 1 RESTORE DATABASE is terminating abnormally.
Any ideas on forcing the restore through T-SQL? The restore works fine from a master backup from itself (ServerB).
Not sure where to post this. How do I restore the master database to a brand new server that has a different name than the server the master currently resides on? I am using SQL Server 2005.
I've installed SQL Server 2000 and applied SP3a. I see SP4 is available and fixes a lot of things. The only bit I am unsure about is section '5.3.2 Changes to Master/Target Server Configurations' http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_5464_sql_server_agent_enhancements_705 "Before you apply SP4, you must complete several steps to upgrade your SQL Server 2000 master/target server configuration. The changes that are introduced with SP4 are not compatible with SQL Server 7.0 target servers, or with any servers not running SP3 or later. This is a change from the original SQL Server 2000 functionality. " As I'm just starting out I don't even know what 'Master/Target Server' is. I'm only installing to my PC which is XP Pro SP2. Can I ignore this step and apply the patch or do I need to do as it states? Thanks
Here's my situation: I need to move several application db's to a new server. The current server is SQL 7.0 SP2, the new server will be SQL 7.0 SP3.
In order to avoid having the problems of mismatched logins and db user definitions, I'd like to restore the current master over the master that's created at install on the new server.
I was doing some testing of this by trying to restore the 7.0 SP2 master onto a SQL 7.0 DE edition and had some problems. (Obviously, this is not the exact scenario that I need to take place -- I want to restore standard edition to standard edition.)
Is restoring the master db from different service packs under 7.0 going to pose a problem? Is restoring the master db the best way to get around the logins issue when moving db's?
Hi everybody. Job was generated from from master server to run on target server Target server does not exist any more I want to delete this job but geeting error "Error 14247 can't add ,update or delete job that generated from MSX server"
I have a server attached to a SAN, all user db's are on the SAN, master, tempdb, and msdb are on the local machine. We will be replacing the machine (not the SAN) to a newer sql server. Our plan was to create the new server with same name, deattach current user db's,backup master and msdb, then connect new server with same name an IP to SAN. I then wanted to restore the master and msdb db's to the new machine, and attach the user db's. We are running log shipping to a stand-by server in this configuration. I was thinking I could let last tran log backup and copy occur, and then let the last restore happen on the standby. I would then shut down the agent. Should I not be able to restore the MSDB and master to the new server (as long as all file folder locations are the same) and be ready to go? Or are there issues when restoring the Master and MSDB to a new server from a different server.
What considerations do I need to take into account if trying to enlist a server into a master server when (a) both instances are on different physical servers and the SQL Server and SQL Server Agent services run under different domain accounts?
The reason I ask is when attempting to create a master server through the SSMS wizard, I receive these errors:
Enlist TSX Progress
- Create MSXOperator (Success) * Checking for an existing MSXOperator. * Updating existing MSXOperator. * Successfully updated MSXOperator.
- Make sure the Agent service for 'MYMSXINSTANCE' is running (Error) Messages * An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib)
- Ensure the agent startup account for 'MYTSXINSTANCE' has rights to login as a target server (Error) * Checking to see if the starup account for 'MYTSXINSTANCE' already exists. Messages * An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib)
- Enlist 'MYTSXINSTANCE' into 'MYMSXINSTANCE' (Error) * Enlisting target server 'MYTSXINSTANCE' with master server 'MYMSXINSTANCE'. * Using new enlistment method. Messages * MSX enlist failed for JobServer 'MYTSXINSTANCE'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'MYMSXINSTANCE'.) (Microsoft SQL Server, Error: 22026) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Now, the first two errors are what are puzzling me. I'm certain I can address the third and last error by making the accounts the SQL Server Agent services run as the necessary SQL permissions on each instance.
I've tried making NT AuthoritySYSTEM accounts on both servers, no luck. Any suggestions?
Please advise me about restore a master database from production to test server.
The reason to do this because I need to test and evaluate some login in master database.
I tried to restore master database to test server, but I got some errors regarding about user databases are not exists in test server. I don't want to restore user databases, I only need master database for evaluate user login.
I'm new to SQL and need help with a query. Not sure if this is the right place.
I have 2 tables, one MASTER and one DETAIL.
The MASTER table has a masterID, name and the DETAIL table has a detailID, masterID, and value columns.
I want to return a populated MASTER table with entries based on the DETAIL.value.
SELECT MASTER.* FROM MASTER WHERE DETAIL.value > 3
This is a simplified version of my problem. I can't figure out how to set the relationship between MASTER.masterID and DETAIL.masterID. If I do an INNER JOIN, the number of results are based on the number of DETAIL entries. I only want one entry per MASTER entry.
I need information on steps to upgrade my current Master(MSX) server to a new server. My MSX is a SQL 2K and it keep track of jobs in about 70 servers, some 2K and some 2K5.
As part of a project, I'm not allowed to use foreign keys, well can't. But I have a problem with this master detail relationship (and a very simple one too). Tables to begin with: Invoice: invoiceid : bigint indentity autoincrement primarykey Detail: invoiceid: bigint - detailnumber:bigint - desc : char20 Okay - I want to set these two tables up such than when I create a new invoice, and subsequently get the new invoiceid, and I start to add detail records to the detail table, I want the detailnumber to autoincrement when I do an SQL Insert. Right now I have detailnumber as the primary key, so when you view the detail records, it looks like: (invoiceid, detailnumber, desc) 1,1,text - 1,2,text - 1,3,text - 2,4, text on another invoice - 3,5, text I want it to work like: (invoiceid, detailnumber, desc) 1,1,text - 1,2,text - 1,3,text - 2,1, text on another invoice - 3,1, text where the invoiceid and the detail number make up the primary key. I seem to recall you could do this is PHP before it had foreign keys & such, and I'm completely drawing a blank on this. BTW - I'm using enterprise manager to set this up, but I can use QA with a sample script to acheive the same. I realize this may be (and probably is) off-topic here, but I can't figure out where to ask. Thanks in advance.
Wierd issue of a missing master database - wierd because I would have thought this was a newbie topic but I've found nothing for it. I googled and had a 'decent' look through this forum and only found a bunch of topics on 'how to restore master database'.
I wouldn't have thought I need to restore the master database because my SSMS works fine and I can query the master database. I can also see it in the drop down list of available databases in the Query Designer toolbar. The problem is just that I can't see it in the list of databases. I can see all the other databases I've created, and I can see the master database in the DATA folder. But not in the SSMS.
I have restored the master db in single user mode.
Processed 440 pages for database 'master', file 'master' on file 1. Processed 3 pages for database 'master', file 'mastlog' on file 1. The master database has been successfully restored. Shutting down SQL Server. SQL Server is terminating this process.
I removed single user mode parameter(-m;)..When I start SQL Server in configuration manager getting below error .The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details
I have restored the master db in single user mode.
--- Processed 440 pages for database 'master', file 'master' on file 1. Processed 3 pages for database 'master', file 'mastlog' on file 1. The master database has been successfully restored. Shutting down SQL Server. SQL Server is terminating this process. ---
I removed single user mode parameter(-m;)
When I start SQL Server in configuration manager getting below error
--- The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details --
changing master database location in sql server 2000
HELLO PLEASE HELP ME I AM TRYING TO CHANGE THE LOCATION OF MASTER DATABASE ( MDF AND LDF ) AND ERRORLOG FILES I HAVE TRIED EDITING STARTUP PARAMETERS IN ENTERPRISE MANAGER I FAILED ,I TRIED IN COMMAND PROMPT "SQLSERVR.EXE " I SUCCEEDED IN CHANGING THE DATA FILE AND ERROR LOG BUT UNABLE TO CHANGE THE LOG FILE PATH FROM DEFAULT LOCATION C:PROGRAM ............ TO D:DATA PLEASE GIVE ME THE PROCESS TO CHANGE DATA ,LOG AND ERROR LOG FILES of master database thanq in advance
Hi,We have a situation where we want to move our current databaseserver to a different hardware and rename the server.If we change the Physical server name, do we have to go thru the wholeprocess of changing it in sql server by running sp_dropserver,sp_addserver?Can we have an alias for the server name in DNS and can sql serverresolve the server name internally by going thru DNS?For eg: Our current database server name is FFSQL-PRD01. We have itregistered in EM as FFSQL-PRD01. Now we renamed the server toSTLSQL-PRD01, and added an entry in DNS for STLSQL-PRD01 with alias ofFFSQL-PRD01( the same old name as alias). After doing this when I goto EM and click on FFSQL-PRD01 would it give me an error? or can itresolve the server name by going to DNS.When you install SQl server the default instance has to be the physicalserver name, Why? Is the physical server name stored in Masterdatabase( SYSSERVERS table)?Thanks for your help.Geetha
In SQL Server 2005 Express, how do I rebuild the master database?
I am receiving the following error messages.
The log scan number (888:136:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
AND
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
I tried going through Add and Remove Programs. It did not recognize anything wrong. It did nothing.
I tried 'setup' from the install media. It said to go to 'Add and Remove Programs.'
In SQL Server 2005 Express, how do I rebuild the master database?
I just notice that my MASTER database has some user tables and user SP ..and I am thinking to move them to 1 new user database but I am worried it will break something ..
What should I do ?
Moreover I wonder why Transaction log of MASTER can be full ( The recovery model is simple ) It should be fine , isn’t it?
Hi allI have a stored procedure that has the lineEXEC master..xp_cmdshell 'dtsrun /Stestjob1 /N testdts /E'If I run the SP from an access front end as a trusted user or from ascheduled job it runs fine and exectues the dts.If I run the stored procedure using VB6 as a standard connection the dtsjobwont run. I get back Execute permissions denied on xp_cmd.. on databasemasterdb_connect_string = "Provider=SQLOLEDB.1;Persist Security Info=False;UserID=test_connect;PWD=pw1test;Initial Catalog=testdb;Data Source=" &database_name....Set cmd = New ADODB.Commandcmd.ActiveConnection = db_connect_stringcmd.CommandType = adCmdStoredProccmd.CommandText = "testStoredProcedure"cmd.ExecuteDo I need to give test_connect permisions to run the test stored procedure.I hoped that because the VB called a stored procedure and the connection hadpermissions to execute the SP then it would be the SP that called thexp_command....can anyone tell me the accepted way to do thismany thanksAndy
