Had an issue where on some server clicking a shortcut to cmd did not open to a path specified in “Start in:” parameter. Work around was to add parameter to command line.
cmd /K “cd /d d:scripts”
AD User executing agent job needs to have SQLAgeUserRole in msdb and be owner of job.
https://technet.microsoft.com/en-US/library/ms188283(v=SQL.110).aspx
Symptom: The transaction manager has disabled its support for remote/network transactions
Issue: Need to enable inbound/outbound transaction manager communication
Solution:
1. Open Component Services Snap-in (dcomcnfg)
2. Browse to Console->Component Services->Computers->My Computer->Distributed Transaction Coordinator
3. Right Click Local DTC and select properties
4. Select Securty tab
5. Check Network OTC Access, Check Allow Inbound, Check Allow Outbound
6. Click OK
7. DTC services should restart and then can give it a test
Additional info:
http://sysadminwebsite.wordpress.com/2012/05/29/9/
http://msdn.microsoft.com/en-us/library/aa561924.aspx
REM Run as administrator
“C:\Program Files\Quest Software\pa_agent\3566\agents\bin\quest_launcher.exe” 3566 “+C:\Program Files\Quest Software\pa_agent\3566\agents” -unregister
https://support.software.dell.com/performance-analysis-for-oracle/kb/44712
fsutil file createnew 2gb.txt 2147483648
copy 2gb.txt 2gb-2.txt
del 2gb*.txt
Error message: 03/03/2015 12:43:09,spid28s,Unknown,An exception occurred while enqueueing a message in the target queue. Error: 15404 State: 19. Could not obtain information about Windows NT group/user 'domainsvc_name' error code 0x5. 03/03/2015 12:43:09,spid28s,Unknown,Error: 28005 Severity: 16 State: 2. Diagnosis: Can confirm this by executing the following SQL: xp_logininfo 'domainsvc_name' Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 62 Could not obtain information about Windows NT group/user 'domainsvc_name', error code 0x5. Resolution: A: Give the “Authenticated Users” “Read Permissions” on the ADFS service account. -or- B: Add the SQL Server service account or "Authenticated Users" to the "BULTIINWindows Authorization Access Group" in AD for the domain -or- C: Add the SQL Server service account or "Authenticated Users" to the "BULTIINPre-Windows 2000 Compatible Access" in AD for the domain References: http://setspn.blogspot.com/2012/05/service-accounts-active-directory_6635.html http://setspn.blogspot.com/2012/05/service-accounts-active-directory_4905.html http://blog.matticus.net/2009/08/windows-2008-and-xplogininfo.html
--To see if default trace is enabled SELECT* FROM sys.configurations WHERE configuration_id = 1568 --To enable default trace sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'default trace enabled', 1; GO RECONFIGURE; GO --To query contents of default trace file SELECT TE.* , T.* FROM sys.fn_trace_gettable(CONVERT(VARCHAR(150)
, ( SELECT TOP 1 f.[value] FROM sys.fn_trace_getinfo(NULL) f WHERE f.property = 2)), DEFAULT) T JOIN sys.trace_events TE ON T.EventClass = TE.trace_event_id
More info:
http://www.databasejournal.com/features/mssql/a-few-cool-things-you-can-identify-using-the-default-trace.html
https://www.simple-talk.com/sql/performance/the-default-trace-in-sql-server---the-power-of-performance-and-security-auditing/
Setting up an instance of SQL Server 2008 R2 64bit Standard, got this error when trying to connect from off the server.
Still working to determine the cause, in the meantime was able to temporarily remedy by disabling names pipes and setting service account to “LocalSystem”.
.instance
(local)instance
127.0.0.1instance – loopback
servernameinstance
ipinstance
ip,port
tcp:servernameinstance – tcp/ip
lpc:servernameinstance – shared memory
np:servernameinstance – named pipes