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!
Simon

You may check this link:
http://www.developersdex.com/sql/message.asp?p=580&r=6569670
Thanks,
Gordon

Similar Messages

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!

Cannot connect to newly created SQL 2008 R2 instance. Login failed for user...

I'm not a SQL guy, just figuring my way around here...
I just created a new instance on an existing SQL server. The original instance works fine. On
Database Engine Configuration > Account Provisioning
I selected Windows authentication mode and added several users, myself among them.
Tried to log in with one my account and getting:
TITLE: Connect to Server
Cannot connect to SERVERNAME\INSTANCE.
ADDITIONAL INFORMATION:
Login failed for user 'domain\myusername'. (Microsoft SQL Server, Error: 18456)
Guidance/suggestions?
Thanks,
Scott

http://sqlserver-help.com/2014/07/08/help-how-to-find-cause-of-login-failed-for-user-error/
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Receiving error message "Login failed for user 'NT AUTHORITY\SYSTEM'" every minute on server which is the mirror

Hello,
I have 2 SQL Server 2008 R2 machines that are configured with database mirroring (using certificates as authentication), there is no witness configured. My issue is that the mirror server is receiving at least one of the below pared messages every
second and filling up my sql error log quickly.
SYSTEM is the service account user for the MSSQLSERVER service.
[298] SQLServer Error: 4060, Cannot open database "<databasename>" requested by the login. The login failed. [SQLSTATE 42000]
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\SYSTEM'. [SQLSTATE 28000]
The database has a status of: Affected database state is: Mirror, Synchronized/Restoring...
When I checking the database mirror monitor, it shows that its mirroring ok and everything has green checkboxes.
Is there a way to stop all these errors being logged, I'm assuming this isn't normal.
Marcus

Yes i have faced the same issues and tried everything and nothing was using this account, system was ended up with creating few GB's sql error log files everday.. and finally i had two options, 1 -- Rebuild the instance completely 2. Change the SQL Server
Audit settings to Only successful logins and restart the instance.. ( May be your current sql server level Audit setting is set to Failed & Successful logins..
Remeber my server was a DR so I have changed the SQL Server Audit settings to only Successful logins.. but production servers we will monitor both... :)
Raju Rasagounder Sr MSSQL DBA

NI Installer Update message "Update Failed" for Labview 7.1.1

Hi, We finally decided to open our LV 7 box, yes I know that version 8
is already out. After I download the version 7.1.1 upgrade and
try to install I get the following message Update failed There
was an error while attempting to verify the product(s) for the :abVIEW
7.1.1 update. Please repair or reinstall the product(s) before
running this application.
Before I reinstall I wanted to post this message so I don't waste my
time with the reinstall. Labview 7.0 works on my computer and I
am not sure where to go from here. Other than trying to resinstall V7
Any ideas
Thanks.

Hello Tim,
I think you have downloaded an update for LV7.1 and such an update does not work with LV7.0.
Because you have LV7.0 it is only possible to update to LV7.0.x and not 7.1.1.
From 7.0 to 7.1 you had have to by the newer version.
Regards ThomasD

Console Message: EV_DELETE failed for file watcher

Hi all,
MBP 2.5GHz/4GB RAM/250GB HD/10.6.4 with all updates.
I get the following Console message 8 times, in less than 2 seconds, each time I log out, restart, shut down, start up, log in:
com.apple.notifyd 12 EV_DELETE failed for file watcher
Any thoughts on cause or solution?
Thanks!

William Boyd, Jr. wrote:
If you search these discussion groups for "EV_DELETE" (without the quotes), you'll see several threads about it. Unfortunately, there doesn't seem to be a lot of reliable advice about how to prevent it. One thread elsewhere suggested that it can be caused by a hardware problem.
I've read a lot of them, tried some things, but no luck yet. I'm doubting that it's a hardware issue, based on my previous post, but who knows.
I tried this
this error comes from the file_watcher module from notifyd when some permissions are buggy (unknown)
So check that / and the first level files and folder under / are not unknown. (use 'ls -l / 'command in terminal to check them)
If they are with bad owner and/or group 'unknown' (or some of them),
use chown root:wheel my_file to correct them (where myfile is a file with weird owner/group)
then execute the following in a Terminal window:
sudo chown root:admin /
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches
and while "ls -l /" did find some things, the sudo commands did nothing.
I also ran across this
One thing, if you do man kextcache, it says instead of running kextcache you should "run touch(1) on the /System/Library/Extensions/ directory of the installation target volume" which I did instead of running kextcache.
but I have no idea what this person is trying to say (I'm way out of my league running Terminal commands. All I do is copy and paste what I consider to be promising commands from seemingly knowledgeable and helpful people; sure hoping to run across one or more of them here! ).
Message was edited by: tjk

SQL 2012 Always On Availability Create Key for Dynamics CRM syntax

Hi I am trying to follow this terribly written article to setup CRM to be part of a SQL alwayson availability group.
The part that is pissing me off is the create SQL logins. http://technet.microsoft.com/en-us/library/jj822357.aspx#BKMK_always_updateorg
So many errors with this post causing so much frustration. What is the actual correct Syntax for creating the key?
Obviously you have to use a UNC path to the CRM front end server. SQL doesnt like UNC and I think an earlier guy said it doesnt like double quotes. Here is what I have and it does not like it. Its hard to see but right before end I have two
single quotes to close it. It's complaining about the \\ in the UNC path.
IF NOT EXISTS (SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey') BEGIN EXECUTE ('CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE ='\\CRM2013\C$\Program Files\Microsoft Dynamics CRM\tools\Microsoft.Crm.SqlClr.Helper.dll'')END

I finally got it working not by using the syntax in that article though. First I did the select all from to see if the key existed by itself
SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey'
NO key was there so then I did
CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE ='C:\Program Files\Microsoft Dynamics CRM\tools\Microsoft.Crm.SqlClr.Helper.dll'

Creation of Chart failed for the Query

I am trying to run a report in SAP CLM in Reports Section and it shows the following error message as attached. The same query is working fine in Query Definition level. Another report which is a duplicate of the previous report (different Filter) is working fine and showing Chart.

Hello Ram,
I feel something is wrong with the Chart definition tab. Please provide the screenshot of chart definition tab of your query.
Regards,
Vignesh

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=20476

TITLE: 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

SQL Error Log: Login Failed for User ''

Hi B1 experts,
currently i have a little problem with our SAP System or better SQL Server. Everytime when a SAP client is started, the SQL Server get the following warning message:
Login failed for user ''. Fehler bei der Anmeldung mit der SQL Authentifizierung. Der Server ist nur für die Windows-Authentifizierung konfiguriert. Client: IP
Fehler 18456, Schweregrad 14, Status 58.
The same message occurs when i log into sap. The funktionality of SAP is not impaired.
I have checked the server authentification mode and the sql server is SQL and Windows Authentification configured.
SQL Server: 2008 R2
SAP System: SAP B1 8.8 PL19
Client System: Windows 7
Someone any ideas?
Regards,
Sabine

Hi Rahul, Hi Julie,
thanks for your replys
@Rahul:
all named pipes are aktiv. the services are all on automatic mode
@Julie
Our Server is running with SQL authentication. We do not use trusted connection generally - security risk.
Further i have disables all Addon. the error occurs again.
We do not use the SBO Mailer, he isn't installed.
Regards,
Sabine

SQL Server Log: Login failed for user ''

We've found in SQL Server Log many records:
Date
3/22/2013 11:13:03 AM
Log
Windows NT (Application)
Source
MSSQLSERVER
Category
Logon
Event
3221243928
Computer
SBO05
Message
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
The server autentification is set to "SQL Server and Windows Autentification mode". But when we open SAP, before entering login/password, we see this message in log. But we still could work in SAP.
How could we solve this?
Kind regards,
Anna Shevchenko

Hi Joseph,
It doesn't help. The same things i've already done.
But when I change Mixed Autentification to Windows, i see another error:
Date
3/22/2013 11:04:26 AM
Log
SQL Server (Current - 3/22/2013 12:33:00 PM)
Source
Logon
Message
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.145]
Do you know why?
Kind regards,
Anna Shevchenko

Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

category-database
event id-3351
source-sharepoint foundation
SQL database login for 'DB_Config' on instance 'DB\instance' failed. Additional error information from SQL Server is included below:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I have been getting this error every hour on only 1 application server of the 2.
My farm consists of 2 app servers, 2 wfes & 2 sql nodes.
My public site is working fine. Authentication is NTLM.
SharePoint VSS Writer is disabled.None of my appPool accounts are running under local system.
I have read many forums/blogs, but couldnt find a solution for this.
Any help would be appreciated!

Hi,
As I understand, you found event id 3351 in event log. Please collect more information as below：
Check if the error also occurs on other servers in your farm.
Check if backup job is scheduled at the time when the event id occurs.
Please run Config Wizard or psconfig.exe -cmd secureresources on all servers and test the issue again.
Regards,
Rebecca Tu
TechNet Community Support

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.

Minor_init failed for module... & unable to configure nics

Hello,
following the instructions of: "Sun Two-Node Cluster How to Guide"
I successfully installed the "Sun Cluster 3.1U4" on my sun ultra 5 workstations (on the two nodes and on the administrative console), which are all running solaris 10 1/06.
During the installation process I choose the option "configure later" as suggested by the guide.
Before configuring the nodes and proceeding with the steps, I wanted to check the correct installation of the nics. I have three nics plugged in the two nodes and two in the administrative console. One per computer is integrated, the others are three pci 10/100 Ark and two Intel nics.
The fact is that the output of dladm show-link is just hme0 for all the computers, none of the other nics seems to be recognized.
in the output of prtconf I see
pci instance 1 ethernet (drive not attached) ethernet (driver not attached)
instead with prtconf -D
pci instance 1 ethernet ethernet (driver simba)
this is the output of one of my nodes that has two Ark nics.
I tried with devfsadm -v (as I read in a post) and the output is
minor_init failed for module /usr/lib/devfsadm/linkmod/SUNW_scmd_link.so
this string also appears at every boot (also when I boot -r)
This last thing I found treated as a problem in "sun java enterprise administration guide":
this is like my situation, but of course I am not running solaris on an x86 system, and I also do not receive "NOTICE NO PCI PROB"
x86 machines running Solaris 10 fail to come up in cluster mode due to changes made for the Solaris boot architecture project. The following error messages are displayed when the machine boots up:
NOTICE: Can�t open /etc/cluster/nodeid
NOTICE: BOOTING IN NON CLUSTER MODE
NOTICE: NO PCI PROP
NOTICE: NO PCI PROP
Configuring devices.
Hostname: pvyom1
devfsadm: minor_init failed for module /usr/lib/devfsadm/linkmod/SUNW_scmd_link.so
Loading smf(5) service descriptions: 24/24
/usr/cluster/bin/scdidadm: Could not load DID instance list.
Cannot open /etc/cluster/ccr/did_instances.
Not booting as part of a cluster
/usr/cluster/bin/scdidadm: Could not load DID instance list.
Cannot open /etc/cluster/ccr/did_instances.
Note: path_to_inst might not be updated. Please �boot -r� as needed to update.
Solution Perform these steps:
1. Add etc/cluster/nodeid to /boot/solaris/filelist.ramdisk.
2. Enter these commands:
# bootadm update-archive
# reboot -- -r
I did not perform the steps indicated as the "solution" for this.
I wait because maybe the scinstall configuration can fix this, doesn't it?
I just want to end my two node cluster config happily and begin to work with it.
Thanks in advantage,
Francesco

The primary problem you seem to have is that your network adapters are not recognized. So this is not a Cluster problem. You talk about "three pco 10/100 Ark and two intel nics". The question is, if those cards have a corresponding solaris driver. Since you seem to indicate that prtdiag does report that there is no driver attached, you may be out of luck for the drivers coming with Soalris 10 01/06 you use. Maybe the vendor of those cards offers drivers that need to get installed?
Otherwise I guess you are out of luck using them, without finding a usabel kernel driver.
For the message
minor_init failed for module /usr/lib/devfsadm/linkmod/SUNW_scmd_link.so
you see, this is harmless and not your problem. You can ignore it.
This error happens when the scmd_link devfsadm link module is attempted to be
loaded before clustering has started. It is a harmless situation.
Greets
Thorsten

Order Import Failed in OM : Log Validation failed for the field - Ship To

Problem in Order Management
When i tried to do Order import in Source Org logfiles shows the Message :Validation failed for the field - Ship To, Please if anyone have a solution of this.
Thanks in advance.
Regards,
Rajesh Verma
Senior Consultant- Oracle Apps.
COLT

perhaps you might want to try populating customer_id instead of name to make sure that there is no error on typing customer name.
primary ship-to and bill-to must exist under this customer. During order import, if ship-to is not specified then import will fetch primary ST of customer.
This is what we use to populate interface table -with mininum of data.
INSERT INTO oe_headers_iface_all
(orig_sys_document_ref,order_source_id,org_id
,order_type_id,payment_term_id, shipping_method_code, freight_terms_code
,customer_po_number,salesrep_id
,sold_to_org_id, ship_to_org_id,invoice_to_org_id,sold_to_contact_id
,booked_flag
,created_by, creation_date, last_updated_by, last_update_date,last_update_login
,operation_code, order_category
,attribute5,tp_attribute4,xml_message_id,xml_transaction_type_code
,request_id, error_flag)
INSERT INTO oe_lines_iface_all
(order_source_id, orig_sys_document_ref, orig_sys_line_ref,orig_sys_shipment_ref
,inventory_item,item_type_code,line_type_id
,top_model_line_ref,link_to_line_ref,component_sequence_id,component_code,option_flag
,ordered_quantity
,order_quantity_uom,salesrep_id
,created_by, creation_date, last_updated_by, last_update_date,last_update_login
,operation_code,cust_model_serial_number,line_category_code
,context,attribute6
,reference_type, reference_line_id, reference_header_id
,return_context, return_attribute1, return_attribute2
,return_reason_code
,tp_attribute1,tp_attribute2,tp_attribute3,tp_attribute4,tp_attribute5
,request_id,error_flag)

MS SQL: Mnt Plan creation message: "Create failed for JobStep "Subplan"

Similar Messages

Maybe you are looking for