SQL 2008 - Create failed for Job 'MaintenancePlan.subplan_1'
Hi,
I'm having difficulty with a server set up by a third party. I am unable to save any Maintenance Plans on the server. When I do this I get the error message Create failed for Job 'MaintenancePlan.subplan_1'.
The plan will run happily if I kick it off as a manual operation.
I have tried this from priviledged accounts including (after all else failed) the sa account.
Does anyone know the cause/solution to the bug?
Pete
Hi,
Does the server have SSIS (SQL Server Integration Services) installed? Some versions of SQL require SSIS to be installed for the maintenance plans to work. What service pack and cumulative update do you have?
Thanks to Tibor -
http://sqlblog.com/blogs/tibor_karaszi/archive/2009/08/26/do-maintenance-plans-require-ssis.aspx
Sean Massey | Consultant, iUNITE
Feel free to contact me through
My Blog or
Twitter.
Please click the Mark as Answer button if a post solves your problem!
Similar Messages
-
MS SQL: Mnt Plan creation message: "Create failed for JobStep "Subplan"
Hi, We have installed MS SQL 2005 from the SAP Business One CDs. We have SAP version 2007a installed also. When I use the MS SQL "wizard" ro create a maintenance plan I get the "Create failed for JobStep "Subplan" message ... the detailed message says "The specified " '@subsystem' is invalid
I have sucessfully created maintenanc eplans on similar installations....
Thanks in advance!
SimonYou may check this link:
http://www.developersdex.com/sql/message.asp?p=580&r=6569670
Thanks,
Gordon -
Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
ThanksHi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike -
SCCM Console issue, SQL connectivity login failed for SCCM machine account
Hi ,
As part of resolving the corrupt SCCM 2012 R2 environment, we have uninstalled the site from the Standalone primary site and restored it from the last backup. The database is on remote server on SQL 2012 SP1. Only Site recovery is run.
Post the restoration on unable to launch the SCCM console, Error Could not connect to the site.
When I checked the logs in the log file SmsProv.log in the program filles\Microsoft Configuration manager\logs, the error is as below
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(6260) : SQL Connection attempt timed out~ SQL Error: [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
*~*~SQL Connection attempt timed out [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
<*><*> CANT CONNECT TO SQL, RETURNING ERROR <*><*>
Regards
LeelaDuplicate post.
https://social.technet.microsoft.com/Forums/en-US/6b26502b-ac07-426c-abe4-6cfdaa45b33b/sccm-console-launch-fails-sql-connectivity-issue-with-sccm-machine-account?forum=configmanagergeneral
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
SQl Server Installation failing for Database Engine and Its Services
Hi,
I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
OS is Windows Server 2008
But it fails for Database Engine.
Installation Details are as Below.
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-10-13 18:41:01
End time: 2014-10-13 19:26:32
Requested action: Install
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x476BF04A%400xBB814387
Machine Properties:
Machine name: KVS-IN-WFAN092
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITYLOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLServer
INSTANCENAME: SQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: KRONOSENGsuperuser
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
And Error in log file are maily as below.
2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are
2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
Thanks,
MaheshI have uploaded detail.txt at below url.
http://m.uploadedit.com/b041/1413264342685.txt
Hi Mahesh,
According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
For more details about this error, please review the following similar thread.
http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
Thanks,
Lydia Zhang -
Java.sql.SQLException: Login failed for user 'ccms'.
Windows Server 2003 R2 Enterprise x64 Edition service pack 1
SQL Server 2000 Enterprise edition 32 bit, SP4 : 2000.8.00.2039
jdbc driver: jtds
connection string: jdbc:jtdsqlserver://ZH-DATA-4:1434/[dbname];instance=[instance name]
the connectivity works fine...almost.
I have 2 identical sql servers one of which is linked to the other via a linked server config which for one particular query gives back the error I give in the subject of this thread:
java.sql.SQLException: Could not get the data of the row from the OLE DB provider 'SQLOLEDB'
if I run the exact same sql string in query analyser it runs with no problem.
if have similar queries also running from java which use the linked server and these do not give an error. I am at a loss as to explain why this is happening.
the query in question joins together a number of views which reference the linked server.
I have tried everything I can think of including recreating the views and linked server definition.
If all is OK in query analyser, how can it fail when called over jbdc (especially when all other db requests succeed) ?refer below link
http://blog.soapplied.com/2013/06/websphere-distributed-transactions-with.html -
SQL 2008 grant permissions for a specific user to query a specific DB DMV ?
Hello is there a way to allow a user to query a particular DB's DMVs (DB-level but not on the entire SQL Server-level) ?
Thanks in advance.The last three are catalog views, to which all users have access, but they are only to see information for objects they have permission to.
What you can do is to package a particular query in a stored procedure which you sign with a certificate. Then you create a login from that certificate and you grant that login VIEW SERVER STATE. This article on my web site explains this technique in detail:
http://www.sommarskog.se/grantperm.html
Erland Sommarskog, SQL Server MVP, [email protected] -
SQL connection string failed for $ password
Hi Team,
I am not able to connect to SQL DB when password contains $ symbol. Please help me to open connection for this scenenrio.
$sqlconstr = "Data Source=Server1;Initial Catalog=DB;User ID=User;pwd='$$XXXXX0';"
$sqlconn = New-Object system.Data.SqlClient.SqlConnection
$sqlconn.connectionstring = $sqlconstr
$sqlconn.open()Thanks I tried below string & it worked
$sqlconstr = 'Data Source=Server1;Initial Catalog=DB;User ID=User;pwd=$$XXXXX0;' -
Create Attachments for Job in PP01 (Mass Upload)
Dear Experts,
I have a requirement to attach documents to jobs in PP01.
I need to do it through program since it is mass upload.
Could you please suggest me any FMs.
What will be the object type of Job.
Regards,
SrilekhaHi Srilekha,
Maybe bit too late..but can you check this...
Massive GOS Upload
Hope this helps.
Kumarpal -
ColdFusion 9 Fails after SQL 2008 Cluster Failover
All,
I have a ColdFusion 9 app server that seems to be failing when my SQL 2008 cluster fails over to the passive node. By failing, my IIS server does not respond to any .cfm requests about 4-5 minutes after the failover. It serves out static and .asp pages just fine. Restarting ColdFusion server service and rebooting the server itself does not fix the problem. The only fix is to fail the SQL cluster back to the original node.
Specs are as follows:
SQL - SQL 2008 SP1 64-bit active/passive cluster VM
CF - CF9 running on Windows 2008 SP2 64-bit VM
ErickProblem solved. We had a linked server defined in SQL that pointed to an Oracle instance. We could successfully run the "Test Connection" in SQL Management Studio for the linked server when our SQL 2008 cluster was on node 1. However, we got an "OraOLEDBpus10.dll: The specified module could not be found" error message when trying to test the connection when the cluster was on node 2. The fix was to add the Oracle folder path to the Windows PATH environment variable on node 2. The Oracle installer is supposed to do this automatically, so we don't know why it was missing.
The reason CF would become unresponsive was that we had a template with a query that used the linked server. The purpose of this template was to monitor the status of the linked server. Using CF Server Monitor, we were able to see active requests to that template which would keep running and not terminate even though we set a timeout value in CF Admin.
Erick -
I am having trouble installing SQL 2008 Small Business Edition on top of MS 2008 std from the SBS premium suite. I recieve the SQL Server 2008 R2 setup log error stateing "Operating system supported for edition "Failed". The specific error is "EditionRequirementCheck
Failed" This SQL server edition is not supported on this operating system.
The SQL 2008 server is a valid SBS domain member server and sees the SBS domain just fine. I have tried re-installing the OS. Not selecting any options except the SQL engine, verbose logging as per How to diagnose "Operating system supported for edition"
pre-requisite errors while installing SQL 2008 Standard Edition for Small Business with no success. (no log.txt generated), enabled browsing, and other items with no luck.
I got the software from MVLS under the specific SBS 2011 premium section. It doesnt seem right or sees something to keep it from installing. The SBS AD box is clean with all FSMO and root functions assigned to it. There are no trust relationships or
child domains. I have licenses for 75 users. Of course there is no tool, log or utility to find what the actual issue the SQL installation is seeing. SOS! Help!!!I meet all prerequisites that can be verified.
I am installing it on the SBS Premium Server 2008 R2 OS from MVLS with the ISO file ending in 29732.
I am on a valid SBS 2011 domain.
The new SQL box is joined to the domain as a member server.
THe SBS server contains alll FSMO roles and is the root of the AD.
There are no trust relationships or child domains.
There is NO way that I can find to determine the number of user and device licenses that it "senses" on the domain. I dont know which ones to count. I am licensed for 75 users and have less than that useing the network. There is no licensing monitor or meathod
I can find to actually verify what the SQL install sees.
I am doing all this logged in as the domain admin.
The troubleshooting steps at the bottom of the post refrenced do not work or I am doing them wrong. I cannot find an output file when I enable verbose logging for the SQL install. I believe if I figure out how it may point the way to the block. Thanks -
Critical SMS_Executive SQL Login failed for user 'NT AUTHORITY\SYSTEM'.
I am getting sql login errors on my sms executive log that i believe is stopping me from pxe booting. I have tried finding where to enter the credentials but i cannot find it.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Starting SMS_EXECUTIVE... SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Microsoft System Center 2012 Configuration Manager v5.00 (Build 7958)
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Copyright (C) 2011 Microsoft Corp. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Running as a Win32 service. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Process ID: 2368 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Worker thread ID: 2412 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Certificate (0x610450) is Exportable SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Initialize COM Security. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
InitializeCOMSecurity: RegOpenKeyEx for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryInfoKey for appid key Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: RegQueryValueEx for AccessPermission Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: IsValidSecurityDescriptor() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: MakeAbsoluteSD() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity: CoInitializeEx() Succeeded.
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
InitializeCOMSecurity() Succeeded. SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Installation directory: E:\Program Files\Microsoft Configuration Manager
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
This server: E076SCCM SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site server: sccmserver.org SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site code: 076 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
Site type: 1 SMS_EXECUTIVE
4/10/2014 3:13:12 PM 2412 (0x096C)
CSMSExecService::RegisterDBConnection: Register a DB connection...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
Initializing the status message reporting system...
SMS_EXECUTIVE 4/10/2014 3:13:12 PM
2412 (0x096C)
The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".
SMS_EXECUTIVE 4/10/2014 3:13:13 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:14 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:19 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:24 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_076" requested by the login. The login failed.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
CSiteControlEx::GetMasterSCF:Failed to read site information from database, retry in 5 seconds ...
SMS_EXECUTIVE 4/10/2014 3:13:31 PM
2412 (0x096C)
SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Server" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Client" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Registered this process as a source of "SMS Provider" events.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Status message reporting system initialized successfully.
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_EXECUTIVE" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:47.950 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:47 PM
2412 (0x096C)
Certificate maintenance interval is every 1800 seconds
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_FOREST_DISCOVERY_MANAGER initialized, DLL = "\bin\x64\ADForestDisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Sun Apr 13 00:00:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_FOREST_DISCOVERY_MANAGER" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.119 2014 ISTR0="2014 04 0 13 04 00 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsgdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern
Daylight Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.120 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_SYSTEM_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adsysdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_SYSTEM_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.157 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AD_USER_DISCOVERY_AGENT initialized, DLL = "\bin\x64\adusrdis.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", next start time = "Thu Apr 10 15:15:00 2014 Eastern Daylight
Time". SMS_EXECUTIVE
4/10/2014 3:13:48 PM 2412 (0x096C)
STATMSG: ID=1105 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_USER_DISCOVERY_AGENT" SYS=sccmserver.org SITE=076 PID=2368 TID=2412 GMTDATE=Thu Apr 10 19:13:48.158 2014 ISTR0="2014 04 4 10 19 15 00 000" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AI_KB_MANAGER initialized, DLL = "\bin\x64\aikbmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ALERT_NOTIFICATION initialized, DLL = "\bin\x64\NotiCtrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_AMT_PROXY_COMPONENT initialized, DLL = "\bin\x64\amtproxymgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CERTIFICATE_MANAGER initialized, DLL = "\bin\x64\CertMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_CONFIG_MANAGER initialized, DLL = "\bin\x64\ccm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLIENT_HEALTH initialized, DLL = "\bin\x64\chmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_CLOUD_SERVICES_MANAGER initialized, DLL = "\bin\x64\CloudMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COLLECTION_EVALUATOR initialized, DLL = "\bin\x64\colleval.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_MONITOR initialized, DLL = "\bin\x64\compmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_COMPONENT_STATUS_SUMMARIZER initialized, DLL = "\bin\x64\compsumm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DATABASE_NOTIFICATION_MONITOR initialized, DLL = "\bin\x64\smsdbmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DESPOOLER initialized, DLL = "\bin\x64\despool.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISCOVERY_DATA_MANAGER initialized, DLL = "\bin\x64\ddm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_DISTRIBUTION_MANAGER initialized, DLL = "\bin\x64\distmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER initialized, DLL = "\bin\x64\EPCtrlMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_ENDPOINT_PROTECTION_MANAGER initialized, DLL = "\bin\x64\EPMgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_EN_ADSERVICE_MONITOR initialized, DLL = "\bin\x64\adctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_FALLBACK_STATUS_POINT initialized, DLL = "\bin\x64\fspmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_HIERARCHY_MANAGER initialized, DLL = "\bin\x64\hman.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MANAGER initialized, DLL = "\bin\x64\inboxmgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INBOX_MONITOR initialized, DLL = "\bin\x64\inboxmon.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_DATA_LOADER initialized, DLL = "\bin\x64\dataldr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_INVENTORY_PROCESSOR initialized, DLL = "\bin\x64\invproc.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LAN_SENDER initialized, DLL = "\bin\x64\sender.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_LICENSE_MANAGER initialized, DLL = "\bin\x64\licensemgr.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MIGRATION_MANAGER initialized, DLL = "\bin\x64\migmctrl.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_CONTROL_MANAGER initialized, DLL = "\bin\x64\mpcontrol.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_MP_FILE_DISPATCH_MANAGER initialized, DLL = "\bin\x64\mpfdm.dll", startup type = "Automatic", current state = "Starting", requested operation = "Start".
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
SMS_NETWORK_DISCOVERY initialized, DLL = "\bin\x64\netdisc.dll", startup type = "Scheduled", current state = "Stopped", requested operation = "None", not scheduled to start again.
SMS_EXECUTIVE 4/10/2014 3:13:48 PM
2412 (0x096C)
STATMSG: ID=1106 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_NETWORK_DISCOVERY" SYS=sccmserver.org SITE=076 PFirst, if your site server is having problems logging into the DB, which it clearly is, you've got bigger issues than just PXE.
Have you verified the permissions in your SQL Server instance for the local System account (I'm assuming at this point that it is local to the site server)?
Jason | http://blog.configmgrftw.com -
Copy Database Wizard error: Enumerate subsystems failed for JobServer
Hi, non-SQL person looking for some guidance. I'm trying to copy databases with permissions from a Win2008 server with SQL2008R2 to a Win2012 server with SQL2012. I'm running SSMS on the 2012 instance, and intiating the Copy Wizard from there. I'm getting
the following error. Thanks.
TITLE: Copy Database Wizard
Enumerate subsystems failed for JobServer 'Win2012serverSQL2012'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3401.0+((SQL11_SP1_QFE-CU).140109-1303+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Enumerate+subsystems+JobServer&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The EXECUTE permission was denied on the object 'sp_enum_sqlagent_subsystems', database 'msdb', schema 'dbo'. (Microsoft SQL Server, Error: 229)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3401&EvtSrc=MSSQLServer&EvtID=229&LinkId=20476TITLE: Copy Database Wizard
Create failed for JobStep 'NAME_CDW_2008ServerName_Win2012serverSQL2012'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.4000.0+((KJ_PCU_Main).120628-0827+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The @flags parameter is not valid for a job step of type 'SSIS'. (Microsoft SQL Server, Error: 14545)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.00.3401&EvtSrc=MSSQLServer&EvtID=14545&LinkId=20476
BUTTONS:
OK
Hi scogordo,
From your description, are you using SSMS 2008 R2 to perform the copy action? I make a test on my computer, and get the same error as yours. To work around this issue, please use SSMS 2012 to copy database from SQL Server 2008 R2 to SQL Server 2012.
There is a feedback to Microsoft about the issue for your reference.
https://connect.microsoft.com/SQLServer/feedback/details/810037/copy-database-fails-when-copying-database-from-sql-server-2008-r2-sp2-to-sql-server-2012-sp1
Thanks,
Lydia Zhang -
Reports successfully execute but generate a login failed for user 'sa' err
I am running Crystal Reports Server XI R2. Classic ASP is used to generate embedded reports within our application. The crystal reports use ODBC to connect to a SQL Server 2005 database. The reports successfully generate in our Classic ASP application. However in SQL Server 2005, the following error messages are being generated each time a crystal report is ran:
- Login failed for user 'sa'.
- Error: 18456, Severity: 14, State: 8.
We know that we are passing the correct username/password to the crystal reports, becuase they execute successfully.
It appears that when the report is called, Crystal Reports appears to conect to SQL Server using a username/password that we didn't provide it at execution time, this fails and the SQL Server 'login failed for user' is generated. Then it runs the report using the username/password we provide and it successfully generates a report.
I have ran Profiler against the SQL Server Database and the 'Login failed for user 'sa' ' errors have a ApplicationName of either 'Seagate Crystal Reports' or 'Crystal Reports'. Therefore I know it is Crystal Reports generating these errors in SQL Server.
Does anyone have any ideas on how to stop these SQL Server 'Login failed for user 'sa' ' errors being generated?What happens if you use Profiler when running the report using Crystal Report Designer?
If the report is ran through Crystal Report Designer, NO 'Login failed for user' error messages appear in profiler. Everything looks ok when ran in Designer.
Also, need to know what patch level you are on?
We are running Crystal Reports Server XI Release 2, Version: 11.5.8.8265
No additional patchs have been applied since Crystal Reports Server was installed.
We may try the SA account if one of the connections fail to log on with the credentials you provided. Verify the user you logged on with has rights to all tables.
The reports were running through our application using the SA account. The SA account has permissions to these tables. The reports do generate results and appear perfectly fine in the application. The issue is that when our application requests the report from Crystal Reports Server. Crystal Reports Server delivers the correct report to our application. However during the process to generate the report, 'login failed for user 'sa' ' errors are being generated in SQL Server 2005.
Also, I have tried creating a completely new SQL user called 'crystaluser'. I ran the report using Crystal Report Designer and used the crystaluser logon and saved the report. Then I ran the same report through our application. SQL Profiler will then display 'login failed for user 'crystaluser''.
Its seems as though Crystal Reports Server is first executing the report using the default SQL user saved with the report, but is either sending a blank password or no password at all. This generates the 'login failed for user' in SQL Server 2005. But it then uses the SQL username/password my application gives it and successfully generates the report. Of course this is only speculation. -
Hi.
We have an sbs2011 std server.
We are looking at a new accounts package that requires SQL 2008 r2 (not express).
Our first thought was to purchase the premium add on but we can not find a single stockist in the UK that has one left for sale.
So is the only option to purchase another server with server OS and SQL 2008r2 STD on it if so this would be very very expensive.
We have also been made aware of SQL 2008 r2 for SBS, if this is OK to run the new accounts with then can this version of SQL be installed on SBS 2011 as we have found an copy that is for 1 server 5 cals for £600 (not sure how we buy more cals though as we
would need 6 users)
I would appreciate any advice on this situation.
Many thanks for you timeHi:
It has been awhile since I have thought about this, but looking up the requirements for SQL 2008 for SBS I find this:
http://blogs.technet.com/b/sbs/archive/2009/03/23/requirements-for-installing-sql-2008-standard-edition-for-small-business.aspx
It appears it would work, and iirc the PAO was added for SBS 2011 because of the need to add a second server for SQL because Exchange 2010 uses so many resources on SBS 2011.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.
Maybe you are looking for
-
Issues with Microsoft Word for mac closing when I try to open old or newly downloaded documents
When I download a document from my professor, or try to open an older document, my word automatically quits. If it's already closed and I try to open a document, it will show the dot at the bottom of the icon that it's loading to open but it quickly
-
When add a people picker (user column) in Word document (un the document Template) and try to add a name it stuck! Is it a known issue? keren tsur
-
TIME CAPSULE backups DISAPPEARED
I did my first complete back-up (using ethernet) 4-5 days ago. After that the backup went wireless. Perfect. Today I received notice saying my latest back-up had failed. When I entered the Timer Machine I was shocked to see I had NO PREVIOUS BACKUPS.
-
IPhone 4s Data hungry. Has anyone got a solution
Hi. I updated my iPhone 4S, to ios 6.1.3. And now I can use over 1GB of my BT 10GB allowance in one day. First I thought it was someone hacking into my home wi fi, but after changing the password on that, I am still hemeraging data, unless I turn off
-
Downloaded audio not visible in Music app on iPad 2?
Hello, Has anyone had this issue reported from students using iPads to access iTunes U material? If so, what did you do about it? A student reported not being able to find downloaded lecture audio files from our private iTunes U site. When he goes to