XML Data archiving service - XML DAS

Hello,
does anybody know differences and dis/advantages between the archive solution in the ABAP stack and the simple archiving function in RWB for archive XI messages and the XML DAS (ABAP & JAVA)?
Is there something in XML_DAS which gives advantages in archiving belonging to XI?
Best regards
Dirk

Hi,
chk out this link for implementation details
http://help.sap.com/saphelp_nw04/helpdata/en/cf/b2fc3f48ecc742e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b7/d5d63f93cb0c65e10000000a114b1d/content.htm
regards
jithesh

Similar Messages

Data Archiving - Service Master

Hi experts,
Hope all have good day........
Can plz send me the archiving procedure for Service master.
The Archiving Object is MM_ASMD.
Thanks & Regards
Ganesh Reddy

Hi,
Go through these steps.
1. Go to tcode SARA.
2. Type Archiving obj name --> MM_ASMD
3. Click on Customizing
   Check cross arc. obj->data archieve monitor
                                 ->For files in file system
4. Max size 25mb (ask u r client)
5. Test mode variant. (Do not choose production mode unless you are quite sure as data cannot be
     retrieved at all. Ask u r client before u choose this.)
6. Start automatically
    (starts submit program, write program, store program and delete program)
7. Content repository is 'LT'. (Again ask your client). Check start automatically.
8. Choose Store before deleting.
9. Once the jobs are scheduled and finished successfully check the spool created by Write and Delete jobs (ARV_MM_ASMD_SUB/WRI/DEL* ) with information of number of Records per update.
10. Go to tcode SARI for viewing archieved data
Note: Errors if any, has to be addressed.
Thanks and Regards,
Guru

Accessing Informatica File Archive Service using its native JDBC driver

Good morning,
Using the Informatica ILM suite, we've retired a number of database applications (which ran on Oracle) into the so-called Optimized File Archive, or OFA.
The information stored in there can be accessed using their File Archive Service, or FAS.
To allow access for certain tools, they've also got an ODBC and JDBC driver (from the original company that created the archive bit, RainStor), to be able to get to tables in archives.
I've been able to set it up for Aquafold's Aqua Data Studio (ADS), but given that that is shareware I've only got an evaluation version, expiring in 2 weeks.
Since SQLdeveloper, like ADS, is a Java-based tool, and it also allows for third party JDBC drivers, I'm inclined to think that somehow SQLdeveloper should also be able to connect to those archives. Unfortunately, I always get an error message: "Invalid connection information specified. Verify the URL format for the specified driver"
There are some slight differences between ADS and SQLdev in setting up such a JDBC connection.
In ADS, apart from providing user/pw, I have to specify following:
- name of the JDBC driver ("com.simba.client.core.SimbaJDBCDriver")
- location of the JDBC driver (e.g. "C:\Ora\RainStorJDBC-3.0.1.2.jar")
- JDBC URL of format "jdbc:simba://<host>:<port>;Archive=<archive>;ConnectionTimeout=3600;Parser=ORACLE"
In SQLdev I can import the JDBC driver (menu > Tools > Preferences, then under Database > Third Party JDBC Drivers), and in the Database Connection Screen create a new connection, provide the user/pw of the so-called Service Manager (from FAS), and choose Connection Type "Advanced" to then specify the "Custom JDBC URL", which would have to be the same as above. If I test the connection, I get an instant error:
"Status: Failure -Test failed: Invalid connection information specified. Verify the URL format for the specified driver".
Informatica's Global Customer Support are saying that SQLdev can't do it, but I'm just wondering whether some really bright lights in the Oracle community have found an alternative route to be able to connect to such FAS/OFA archives. Given the similarities between ADS and SQLdev, to me it seems it - somehow - has to be possible as well...
Thanks in advance for thinking about this problem/challenge.
Cheers!
Edited by: exapat on Dec 7, 2012 10:43 AM
Did some further investigations, on other third party drivers. Those ones (e.g. for SQL Server) - when loaded - create an extra tab in the connection screen.
The RainStor JDBC driver does not do that, and I can imagine that that's where it falls short.
If indeed the case, what could be done to overcome this?

Hi,
Did some further investigations, on other third party drivers ... If indeed the case, what could be done to overcome this?That is the case. Currently browsing and migration support for third-party databases is limited to the following:
http://www.oracle.com/technetwork/developer-tools/sql-developer/supportedmigplatforms-086703.html
See section 1.1 for currently supported databases and section 1.3 for those planned for a future release.
To see an example of some (all?) of the extra bits needed to support browsing of a third-party database, find the extensions directory in your SQL Developer installation, look for
oracle.sqldeveloper.thirdparty.browsers.jarthen browse it to see the various class, properties, and xml files necessary for supporting connections to databases like mysql or sybase. You may conclude adding browsing support is not all that complicated. Migration support is an entirely different matter, however. Oracle is the thirdparty.browsers extension owner. Support for more third-party databases would normally be added by the SQL Developer group based on a database's general popularity or a feature request on the SQL Developer Exchange -- obviously a long-term proposition.
If you look at the [Extensions Exchange|http://www.oracle.com/technetwork/developer-tools/sql-developer/extensions-083825.html] maybe you can get some ideas how best to proceed if you have the resources to build your own extension to support RainStor.
Regards,
Gary
SQL Developer Team

The Data Access Service is either not running or not initialized.

When I try to access the OPSMGR 2012 R2 console I get the error:
Failed to connect to server "SCOM01.THG.local"
The Data Access Service is either not running or not initialized.
Date: 3/4/2014 8:41:07 AM
Application: Operations Manager
Application Version: 7.1.10226.0
Severity: Error
Message: Failed to connect to server 'SCOM01.THG.local'
Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. ---> System.ServiceModel.EndpointNotFoundException: Could not connect to
net.tcp://scom01.thg.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0045038. TCP error code 10061: No connection could be made because the target machine actively refused it 10.192.1.27:5724. ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 10.192.1.27:5724
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
   at Microsoft.EnterpriseManagement.Monitoring.Console.Internal.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://scom01.thg.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0045038. TCP error code 10061: No connection could be made because the target machine
actively refused it 10.192.1.27:5724. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.192.1.27:5724
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.192.1.27:5724
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
System Logs:
The System Center Data Access Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
The System Center Data Access Service service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
The System Center Data Access Service service entered the running state.
Application Logs
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: microsoft.mom.sdk.servicehost
P2: 7.5.3070.0
P3: 520d7e93
P4: System.Data
P5: 4.0.30319.18408
P6: 52310bef
P7: 2622
P8: 297
P9: 2V4KQ41FR0ZKJA4HMDJUZUWAZMPSCBGF
P10:
Attached files:
C:\Users\svc_scomdas\AppData\Local\Temp\WERB021.tmp.appcompat.txt
C:\Users\svc_scomdas\AppData\Local\Temp\WERB0DD.tmp.WERInternalMetadata.xml
C:\Users\svc_scomdas\AppData\Local\Temp\WERB0DE.tmp.hdmp
C:\Users\svc_scomdas\AppData\Local\Temp\WERC65B.tmp.dmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_microsoft.mom.sd_bd8814a66c4798fbd871834494e962595894932_cab_0837c781
Analysis symbol:
Rechecking for solution: 0
Report Id: 55e1dff8-a3a4-11e3-9412-00155d01fa02
Report Status: 0
Hashed bucket:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: microsoft.mom.sdk.servicehost
P2: 7.5.3070.0
P3: 520d7e93
P4: System.Data
P5: 4.0.30319.18408
P6: 52310bef
P7: 2622
P8: 297
P9: 2V4KQ41FR0ZKJA4HMDJUZUWAZMPSCBGF
P10:
Attached files:
C:\Users\svc_scomdas\AppData\Local\Temp\WERB021.tmp.appcompat.txt
C:\Users\svc_scomdas\AppData\Local\Temp\WERB0DD.tmp.WERInternalMetadata.xml
C:\Users\svc_scomdas\AppData\Local\Temp\WERB0DE.tmp.hdmp
C:\Users\svc_scomdas\AppData\Local\Temp\WERC65B.tmp.dmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_microsoft.mom.sd_bd8814a66c4798fbd871834494e962595894932_cab_0837c781
Analysis symbol:
Rechecking for solution: 0
Report Id: 55e1dff8-a3a4-11e3-9412-00155d01fa02
Report Status: 4
Hashed bucket:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Application: Microsoft.Mom.Sdk.ServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.EnterpriseManagement.ConfigurationReaderException
Stack:
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(Microsoft.EnterpriseManagement.InProcEnterpriseManagementConnectionSettings)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)

can you please check the following -
1) SQL services are running.
2) Data access service is running. you can try restarting the service too.
3) check that the OpsMgr database is not full.
4) start the 'SQL Vss writer" service.
5) check the sql server error logs.
6) Check your SQL accounts too.
7) Try this too -
To create this registry entry, follow these steps:
Click Start, click Run, type regedit, and then click
OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Right-click Control, point to New, and then click
DWORD Value.
In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
Right-click ServicesPipeTimeout, and then click Modify.
Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click
OK.
For example, to wait 60 seconds before the service times out, type 60000.
Quit Registry Editor, and then restart the computer.
Thanks, S K Agrawal

Data Transformation Services Execution Utility stopped working and was closed

Hi,
I had the SSIS packages (ETL job) working fine for a long time and then we moved the server/machine and ETL job keeps failing.
The ETL job run number of packages. The ETL job fails for the first run then I set the retires and it works in 2nd or 3rd try on the ETL job but it fails daily for the first run where DTexec.exe crash (log pasted below)
Server: Windows 2008 R2
SQL Server: SQL Server 2008 R2
RAM 64 GB
CPU cores 8
we had the similar specs on previous machine and ETL job worked fine. Only difference is we have 2 SQL server instances now on same machine.
I am suspecting it's an issue with ETL packages but why it was working fine before for a long time and after machine move it keeps failing.
Any thoughts?
Version=1
EventType=APPCRASH
EventTime=130432662277734721
ReportType=2
Consent=1
ReportIdentifier=f2ff88b6-cfc3-11e3-babd-005056997b14
IntegratorReportIdentifier=f2ff88b5-cfc3-11e3-babd-005056997b14
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=DTExec.exe
Sig[1].Name=Application Version
Sig[1].Value=2009.100.4263.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5036ba73
Sig[3].Name=Fault Module Name
Sig[3].Value=DTSPipeline.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=2009.100.4263.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5036ba53
Sig[6].Name=Exception Code
Sig[6].Value=40000015
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000a33c5
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=7c29
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=7c290b53eb7940378e43b699d1de1f07
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=199e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=199e6470d3145d6303fbe30033cf7038
UI[2]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Data Transformation Services Execution Utility stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\MSVCR80.dll
LoadedModule[9]=C:\Windows\system32\USER32.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\LPK.dll
LoadedModule[12]=C:\Windows\system32\USP10.dll
LoadedModule[13]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[14]=C:\Windows\system32\ole32.dll
LoadedModule[15]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEParse.dll
LoadedModule[16]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\MSVCP80.dll
LoadedModule[17]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEPkg.dll
LoadedModule[18]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_8a1dd9552ed7f8d8\ATL80.DLL
LoadedModule[19]=C:\Windows\system32\PSAPI.DLL
LoadedModule[20]=C:\Windows\system32\VERSION.dll
LoadedModule[21]=C:\Windows\system32\IMM32.DLL
LoadedModule[22]=C:\Windows\system32\MSCTF.dll
LoadedModule[23]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[24]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[25]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTS.dll
LoadedModule[26]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[27]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\dtsmsg100.dll
LoadedModule[28]=C:\Windows\system32\CRYPT32.dll
LoadedModule[29]=C:\Windows\system32\MSASN1.dll
LoadedModule[30]=C:\Windows\system32\SXS.DLL
LoadedModule[31]=C:\Windows\System32\msxml6.dll
LoadedModule[32]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[33]=C:\Windows\system32\rsaenh.dll
LoadedModule[34]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[35]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DtsConn.dll
LoadedModule[36]=C:\Windows\system32\SHELL32.dll
LoadedModule[37]=C:\Windows\system32\mscoree.dll
LoadedModule[38]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[39]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[40]=C:\Windows\system32\profapi.dll
LoadedModule[41]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\88744044294787b99dd4a8704ab75a79\mscorlib.ni.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\af0a0b96a02f9925eb84392ee65a5cfa\System.ni.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\40937910f60adedfb214d89b989f929d\Microsoft.SqlServer.ManagedDTS.ni.dll
LoadedModule[44]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\f82fe091649105fb4de1195cb9da7438\Microsoft.SqlServer.DTSRuntimeWrap.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\77e0f983055ea695867ca69afaecda79\Microsoft.SqlServer.SQLTask.ni.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\3975acf49313ceea1280da91f0383480\System.Xml.ni.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\80c6801f36d7c3e891323f6b53dccbcc\Microsoft.SqlServer.Msxml6_interop.ni.dll
LoadedModule[48]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\ExecPackageTask.dll
LoadedModule[49]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\Resources\1033\dtsmsg100.rll
LoadedModule[50]=C:\Windows\system32\urlmon.dll
LoadedModule[51]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[52]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[53]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[54]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[55]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[56]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[57]=C:\Windows\system32\normaliz.DLL
LoadedModule[58]=C:\Windows\system32\iertutil.dll
LoadedModule[59]=C:\Windows\system32\WININET.dll
LoadedModule[60]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[61]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTSComExprEval.dll
LoadedModule[62]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
LoadedModule[63]=C:\Program Files\Microsoft SQL Server\100\Shared\SQLBoot.dll
LoadedModule[64]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\c9743c9d2ac43664c43d9a0b3fbb5548\Microsoft.SqlServer.DtsMsg.ni.dll
LoadedModule[65]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\5ef353725aeb5af35fb49c3f300c38b3\Microsoft.SqlServer.SQLTaskConnectionsWrap.ni.dll
LoadedModule[66]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\52f53ccfcc9570f1fd13f63d0a640e81\Microsoft.SqlServer.BatchParser.ni.dll
LoadedModule[67]=C:\Windows\assembly\GAC_64\Microsoft.SqlServer.BatchParser\10.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.BatchParser.dll
LoadedModule[68]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\msvcm80.dll
LoadedModule[69]=C:\Program Files\Common Files\System\Ole DB\oledb32.dll
LoadedModule[70]=C:\Windows\system32\MSDART.DLL
LoadedModule[71]=C:\Windows\system32\bcrypt.dll
LoadedModule[72]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[73]=C:\Program Files\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[74]=C:\Windows\system32\comsvcs.dll
LoadedModule[75]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
LoadedModule[79]=C:\Windows\system32\NETAPI32.dll
LoadedModule[80]=C:\Windows\system32\netutils.dll
LoadedModule[81]=C:\Windows\system32\srvcli.dll
LoadedModule[82]=C:\Windows\system32\wkscli.dll
LoadedModule[83]=C:\Windows\system32\WS2_32.dll
LoadedModule[84]=C:\Windows\system32\NSI.dll
LoadedModule[85]=C:\Windows\system32\1033\SQLNCLIR10.RLL
LoadedModule[86]=C:\Windows\system32\secur32.dll
LoadedModule[87]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[88]=C:\Windows\system32\credssp.dll
LoadedModule[89]=C:\Windows\system32\kerberos.DLL
LoadedModule[90]=C:\Windows\system32\cryptdll.dll
LoadedModule[91]=C:\Windows\system32\msv1_0.DLL
LoadedModule[92]=C:\Windows\system32\ntdsapi.dll
LoadedModule[93]=C:\Windows\system32\LOGONCLI.DLL
LoadedModule[94]=C:\Windows\system32\security.dll
LoadedModule[95]=C:\Windows\system32\schannel.DLL
LoadedModule[96]=C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll
LoadedModule[97]=C:\Windows\system32\mswsock.dll
LoadedModule[98]=C:\Windows\System32\wshtcpip.dll
LoadedModule[99]=C:\Windows\System32\wship6.dll
LoadedModule[100]=C:\Windows\system32\DNSAPI.dll
LoadedModule[101]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[102]=C:\Windows\system32\WINNSI.DLL
LoadedModule[103]=C:\Windows\system32\rasadhlp.dll
LoadedModule[104]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[105]=C:\Windows\system32\ncrypt.dll
LoadedModule[106]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\SQLTaskConnections.dll
LoadedModule[107]=C:\Windows\system32\ODBC32.dll
LoadedModule[108]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\BatchParser.dll
LoadedModule[109]=C:\Windows\system32\odbcint.dll
LoadedModule[110]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[111]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Data\5e957216f11830cbc49b4b30314e0e10\System.Data.ni.dll
LoadedModule[112]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[113]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.AddIn\b3b4d44d80055c9e96909f153ff92fbc\System.AddIn.ni.dll
LoadedModule[114]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\5388ebc8e600ad2542d8afbef9559944\Microsoft.SqlServer.ScriptTask.ni.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\492ba64d2cb55aa910114c85c2327821\Microsoft.SqlServer.VSTAScriptingLib.ni.dll
LoadedModule[116]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.VisualStu#\f3ab3bf00723d757396110ac3dc57a6d\Microsoft.VisualStudio.Tools.Applications.DesignTime.v9.0.ni.dll
LoadedModule[117]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTSPipeline.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\06aaaec444077ab8248b28b0bdf2c3b2\Microsoft.SqlServer.PipelineXML.ni.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\3dce1dfa4ea9d165471de3b83b82893c\Microsoft.SqlServer.SqlTDiagM.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\4f58550979ad960c616b557266fbc5d0\Microsoft.SqlServer.Diagnostics.STrace.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\fed86e49fe95761085bf287f901f5b53\System.Configuration.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\6f12b249b9bd278ddc1a5ea48fb1221e\Microsoft.SqlServer.DTSPipelineWrap.ni.dll
LoadedModule[123]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\OleDbSrc.dll
LoadedModule[124]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\OleDbDest.dll
LoadedModule[125]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxDerived.dll
LoadedModule[126]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxRowCount.dll
LoadedModule[127]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\CommandDest.dll
LoadedModule[128]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxSplit.dll
LoadedModule[129]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxMergeJoin.dll
LoadedModule[130]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxSort.dll
LoadedModule[131]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxDataConvert.dll
LoadedModule[132]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\78f11d2ba751edf529c28ca8b012d697\Microsoft.SqlServer.PipelineHost.ni.dll
LoadedModule[133]=C:\Windows\assembly\GAC_MSIL\KimballMethodSCD100\1.0.0.0__8b0551303405e96c\KimballMethodSCD100.dll
LoadedModule[134]=C:\Windows\assembly\GAC_MSIL\SSISComponentUtilities\1.0.0.0__8b0551303405e96c\SSISComponentUtilities.dll
LoadedModule[135]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\868d117286ad259249f31d3fe813d39a\System.Drawing.ni.dll
LoadedModule[136]=C:\Windows\assembly\NativeImages_v2.0.50727_64\CustomMarshalers\98e9b163a01ce659f1bb3d7ee15be7bf\CustomMarshalers.ni.dll
LoadedModule[137]=C:\Windows\assembly\GAC_64\CustomMarshalers\2.0.0.0__b03f5f7f11d50a3a\CustomMarshalers.dll
LoadedModule[138]=C:\Windows\system32\apphelp.dll
LoadedModule[139]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxLookup.dll
LoadedModule[140]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxUnionAll.dll
LoadedModule[141]=C:\Windows\assembly\NativeImages_v2.0.50727_64\EnvDTE\4a689bff8b507e736eea8e5b2b21d42a\EnvDTE.ni.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Data Transformation Services Execution Utility
AppPath=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe

Hi Arthur,
Yes both instances are same.
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4263.0 (X64) Aug 23 2012 15:56:56 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I have run the Main package using the using SQL Agent, main package calls the child packages.
The error message shown on SQL agent job is:
R6025 - pure virtual function call. The return value was unknown. The process exit code was 255.
or sometimes
The step did not generate any output. The return value was unknown. The process exit code was -532459699.
in the even log it says:
Error Level:
Event ID 1000
Faulting application name: DTExec.exe, version: 2009.100.4263.0, time stamp: 0x5036ba73
Faulting module name: DTSPipeline.dll, version: 2009.100.4263.0, time stamp: 0x5036ba53
Exception code: 0x40000015
Fault offset: 0x00000000000a33c5
Faulting process id: 0x98c
Faulting application start time: 0x01cf64ba9b72b27c
Faulting application path: C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
Faulting module path: C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTSPipeline.dll
Report Id: e8eb9b4f-d0ad-11e3-babd-005056997b14
Information Level:
Windows error reporting Event ID 1001
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: DTExec.exe
P2: 2009.100.4263.0
P3: 5036ba73
P4: DTSPipeline.dll
P5: 2009.100.4263.0
P6: 5036ba53
P7: 40000015
P8: 00000000000a33c5
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_DTExec.exe_ccc7a4e176faafbea69955957371ea96e175b_44c41e3e
Analysis symbol:
Rechecking for solution: 0
Report Id: e8eb9b4f-d0ad-11e3-babd-005056997b14
Report Status: 4

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

HR PA Data Archiving

Hi,
We are undergoing the archiving project for HR module. For PD data, we can use object BC_HROBJ, for PCL4 data, we can use PA_LDOC. What about 2000 series infotypes data, such as PA2001, PA2002, PA2003, etc.? Because all changes to these infotypes are stored in PCL4 cluster LA, we only need to purge the data from these tables. What is the best way to purge PA2xxx data? We cannot use transaction PA30/PA61 to delete records because user exit edits prevent any action against old data beyond certain time frame.
Thanks very much,
Li

This is not directly related to SAP NetWeaver MDM. You may find more information about data archiving on SAP Service Marketplace at http://www.service.sap.com/data-archiving or http://www.service.sap.com/slo.
Regards,
Markus

"unable to connect to the data access service" installing report server

Trying to do a 2 server SCOM 2012 R2 install on Server 2012 w/SQL 2012. Management server and operations console on one, and SQL, web console, and reporting server on the other. When I get to the web console and reporting server install, and
the "Specify Management Server" screen, I input the 1st management server name and it gives me a red X with the message:
"Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version."
Here is the setup log error:
"Info: :Could not connect to Management Server: scom-app with exception: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or
too long."
I don't see the "Data Access" service in services on either server. I followed all of the setup prereqs in SCOM 2012 unleashed book, and also referenced this article for setup advice:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
Everything seems to be working until I get to this point.
Thank you for any help you can provide,
Dan

Hi Tom,
1. Did the setup complete successfully on the MS and Console server?
>>>Yes, without issue
2. You do not see the service "System Center Data Access Service"
>>>I do indeed see it on the MS and Console server, it is set to Auto and running. (I also tried rebooting this server and retried, no help)
3. Is the Windows Firewall enabled?
>>>It has symantec endpoint protection. I disabled symantec completely on both servers and retried, no help.
Thx,
Dan

Field catalog issue in Data archiving

Hi Experts,
We are facing issue in SAP CRM Data Archiving info structure. I have created the fieldcatlog for the service Ticket( CRM_SERORD archive object) and Act On ( CRM_ACT_ON archive Object).
in our scenario, multiple Business partner(Consumer, orgnisational and employee) are attached to each Service ticket, in my ZARxx tables are storing the one entry means one service ticket and one Business partner.
My requirment is it should show all the business partners for each service ticket.
Could you please help me on this.
Regards,
Srini

Hi Srini,
We have the same problem for our project. Did you find a solution for this problem ?
Best regards,
Nevets

SCOm data access service not started

Hi all
my SCOM server was down and i checked once it is up and found Data access service is stopped, when i tried to start the service i am getting following error, Please help.
The System center Data Access service on local computer started and the stopped , Some services stopped automatically if they are not in use by other services or programs.

Please post the error on eventviewer related to this issue.
Check userlogon on this services take db_owner permission on SQL to can run services
Also you can refer below link for this issue
http://scug.be/dieter/2014/01/16/scom-system-center-data-access-service-stops-event-26380-33333/
http://blogs.technet.com/b/servicemanager/archive/2011/10/04/system-center-data-access-service-start-up-failure-due-to-sql-configuration-change.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Error when click Manage in Business Data Connectivity Service Sharepoint 2013

Dear all,
In Sharepoint central administration, I click manage service applications. Then, I click New > Business Data Connectivity Service. After create new Business Data Connectivity Service, when I click Manage to manage this new Business Data Connectivity Service,
there is error "Cannot complete this action as the Business Data Connectivity Shared Service is not responding. Please contact your administrator." In event viewer, there is error ""The BDC Service application is not accessible. The full
exception text is : The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'NTLM'.
I have tried to delete and create the BDC Service application, but it still did not work. I have tried to restart BDC Service and do iisreset, but it still did not work.
Please help. Thank you.
Best regards,
Johanna

Hi,
According to your post, my understanding is that you get an issue about the Business Data Connectivity Service.
To quickly and accurately find the issue, I recommend you can check the event log and ULS log to see if anything unexpected occurred.
For SharePoint 2013, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
You can check the ULS log by the methods here:
http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
http://msdn.microsoft.com/en-us/library/gg193966(v=office.14).aspx
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

Dear All,
I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
Please let me know if you have any ideas on the above questions.
Thanks & Regards
Ravikiran

Hi,
I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
Thanks
Sunny

SCOM 2012 Data Access Service could not start

Hello,
I have 3 SCOM 2012 servers. I got the error that the All Managament Server Pool is not available. Google search give me a lot of posts to add folder PoolManager at HKLM\System\CurrontControlSet\services\HealthService\Parameters with the DWORD keys PoolLeaseRequestPeriodSeconds
600 and PoolNetworkLatencySeconds 120. After restarting last SCOM server the Data Access Service could not run "Windows could not start the System Center Data Access Service. Error 1053: The service did not respond to the start or control request in a
timely fashion"
At Operations Manager Eventlog I see an error: "OpsMgr Management Configuration Service failed to communicate with System Center Data Access Service due the following exception: System.Runtime.Remoting.RemotingException: Unable to get ISdkService interface.
Please make sure local Sdk Service is running."
At System Eventlog I see an error: "A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect."
Why did it run on the both other servers and failes on the third one? What can I check?
Regards, Doreen

Hi,
According to my understanding, after editing the registry key value, two of three management servers work fine now, and the issue only occur to the third one. Whether all those servers are running with Windows server 2012?
I would like to suggest you re-check the service account for the data access service, maybe we can re-enter the account credential. Those three servers may use the same account for the service, make sure the account is not disabled and you enter in the right
password for it.
Here is a similar thread, please go through it for more details:
http://social.technet.microsoft.com/Forums/en-US/f2281934-513d-4b60-bb4b-34ae8a892ace/failed-to-open-the-console-and-system-center-data-access-service-wont-start-scom-2012?forum=operationsmanagergeneral
In addition, please also restart the third server and check the result, and I know that there is a similar error message in SCOM 2007:
http://blogs.technet.com/b/csstwplatform/archive/2012/01/02/scom-2007-r2-unable-to-open-the-scom-console-after-server-reboot-the-sdk-service-is-stopped.aspx
Regards,
Yan Li
Regards, Yan Li

Data Access Service SPN Not Registered alert in SCOM, while i have registered the SPN on the service account

Hi Guys,
I get an SPN error for the Data Access Service. But i have registered the SPN's to the account.
Why does Opsmgr still gives this Alert:
Kind regards,
André

This is because by default Domain User accounts don’t have the ability to update their own SPNs.
To set your SPN correctly use the following commands with a user who has Domain Admin privileges:-
setspn –A MSOMSdkSvc/SERVERNAME DOMAIN\USERNAME
setspn –A MSOMSdkSvc/SERVERNAME.fqdn.name DOMAIN\USERNAME
If you wish to check that SPN registration has been set up correctly use:-
setspn -L DOMAIN\USERNAME
Also you can refer below link
http://www.systemcentercentral.com/forums-archive/topic/scom2012-spn-registration-error/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

CS-MARS, data archiving issue.

Hello at all.
I'm using CS-MARS-20.
Reimaged, restored and upgraded to software version 6.1.8, I'm not able to start data archiving successfully.
I have configured data archiving using a remote SFTP server, click Apply, Start and Activate: data archiving status is running, service is enabled and remote server is available.
But MARS doesn't archive nothing!
Using another SFTP remote client with the same account used from appliance, I can create folders, files and remove.
Any ideas?
Thanks.
Regards.
Andrea

Now we are moving to a NFS solution.
Data archiving status is running, archiving service is enabled and remote server is available but events, incidents and configuration are not exported.
I can use CLI (pnexp command) to export configuration successfully.
Any ideas?
Why data archiving doesn't work?
Thanks.
Andrea

XML Data archiving service - XML DAS

Similar Messages

Maybe you are looking for