July 18, 2012 at 11:14 am
i guys,
A scheduled job is failing continuously with this error
Executed as user: BLAH\admin. Failed to execute get connection string command. Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "DBShadow" Procedure: "sp_syscollector_get_warehouse_connection_string" Line#: 16 Error Number: 14686 Error State: 1 Error Severity: 16 Error Message: "The MDWInstance and MDWDatabase parameters of the configuration store cannot be null." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Process Exit Code 1. The step failed.
Even if I change the user, it still doesn't work.
This is what the job is doing:
Step 1:
Type: Operating System (CmdExec)
dcexec -c -s 1 -i "$(ESCAPE_DQUOTE(MACH))\$(ESCAPE_DQUOTE(INST))" -m 1
Step 2:
Type: TSQL
EXEC [dbo].[sp_syscollector_purge_collection_logs]
Step 3:
Type: Operating System (CmdExec)
dcexec -u -s 1 -i "$(ESCAPE_DQUOTE(MACH))\$(ESCAPE_DQUOTE(INST))"
There are few different teams at play here. Not sure where to start looking at first. Can you please let me know where should I start here and where could be the problem?
Thanks a lot.
July 18, 2012 at 8:11 pm
Maybe, the spp causes this error. You can excute the spp in your database directly. I saw that error message here: parameters is not null.
July 19, 2012 at 2:03 am
This is data collector and the management data warehouse.
I would first start by checking the configuration, under management - data collection - (right click) management data warehouse.
July 19, 2012 at 10:01 am
Thanks guys. I will give these a whirl..
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply