DCOM issue

I am connecting to a National Instruments OPC server. My simple test app uses one indicator with its DataSocket property hard-coded to a tag on the OPC server.
This app will work on some machines and on others the DataSocket will never connect.
I believe it is DCOM issues. I have been comparing every aspect of a working and non-working machine and I have found one major difference.
Under the dcomcnfg, in the DCOM Config section, a working machine has an entry for "National Instruments Variable Engine". The non-working machines do not.
I do not know how I got this component installed on some machines and not others. If anyone could let me know how to get it installed or added to my build package I'd appreciate it.
Thanks,
Dave
Solved!
Go to Solution.

I have resolved the issue.
I was publishing the software just by building an exe.
When I build an entire Installer I was able to add the DataSockets component to the install package.

Similar Messages

Windows DCOM fix

For the DSC users out there. I received a letter today about a Microsoft fix for a DCOM issue when using OPC servers
http://support.microsoft.com/kb/924432

Thanks for sharing!
Simon H
Applications Engineer
National Instruments
http://www.ni.com/support/

DistributedCOM Event ID 10010 on Windows 2008 R2

Hi,
I'm getting following error on one of my Virtual Windows 2008 R2 server and have tried lots of solutions but still this event logging on my server.
The GUID mentioned in the event is related to Virtual Disk Service and I have verified all security permission related setting in component services as well as in Windows Registry but no luck yet.
Please help to resolve this issue.
Following are the event details:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 19/04/2013 9:02:54 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ExchangeSVR.Gen3Com.local
Description:
The server {7D1933CB-86F6-4A98-8628-01BE94C9A575} did not register with DCOM within the required timeout.
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-19T11:02:54.000000000Z" />
<EventRecordID>133132</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>ExchangeSVR.Gen3Com.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">{7D1933CB-86F6-4A98-8628-01BE94C9A575}</Data>
</EventData>
</Event>
Thanks,

Hi Thakur,
I believe, this thread may help to fix DCOM issue.
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/8c292062-64f2-4c1a-8c50-13ababb67738/
Regards, Ravikumar P

Cannot Open HFM Application in Workspace. "The RPC server is unavailable.

Hi All,
I cannot open HFM Application from Workspace. Planning works fine.
Restarted the HFM services and tried but no use.
Error shows "The RPC Server is Unavailable. Error code:- 2147023174
Details shows following.
Trace: Error Reference Number: {2498F82B-1C14-4704-B34A-BA7145D27450}<BR>Num: 0x800706ba;Type: 0;DTime: 10/8/2012 7:57:19 PM;Svr: SERVER NAME;File: CHITRegistryWrapper.cpp;Line: 1108;Ver: 11.1.2.0.0.2762;<BR>Num: 0x800706ba;Type: 0;DTime: 10/8/2012 7:57:19 PM;Svr: SERVER NAME;File: CHFMwHITRegistry.cpp;Line: 1083;Ver: 11.1.2.0.0.2762;
Thanks.

It may be worth having a read of the following doc in Oracle support as it sounds like it could be DCOM related - "Identifying and Troubleshooting DCOM Issues Affecting Hyperion Financial Management (HFM) [ID 1419144.1]"
Cheers
John
http://john-goodwin.blogspot.com/

_Application::GetWorkbooks() intermittently throws exception scode RPC_E_SYS_CALL_FAILED

The frequency of this error ranges from about 1 out of 10,000 calls on some computers and is not observable on other computers running the same code.
The error occurs while making a call from Excel VB to our COM object when our program tries to call back to Excel to get the excel worksheet object to transfer worksheet cell values back and forth. This transfer always starts with a call to _Application::GetWorkbooks()
to find the correct workbook. Occasionally _Application::GetWorkbooks() throws an exception and the SCODE returned by COleException::Process() is RPC_E_SYS_CALL_FAILED(0x80010100).
Retrying the function call after waiting for some period of time always fails unless the debugging break dialog in Excel appears(after some timeout). If the debugging dialog timeout is disabled by setting Application.DisplayAlerts to false, then
retrying the call will never succeed. If the debugging dialog appears and the user continues execution the program can be continued, and _Application::GetWorkbooks() will succeed. However this requires human intervention and is not a valid workaround.
The calling order between Excel and our program is like the following.
1. Excel VB code creates and instance of our program then calls our Calculate() function.
2. Our Calculate() function, using an existing dispatch pointer to the Excel _Application object calls _Application::GetWorkbooks(), then digs out the correct workbook, worksheet, cell, etc....
What are some things to check or workarounds to try?

Hi chemdev_neil,
>> The frequency of this error ranges from about 1 out of 10,000 calls on some computers and is not observable on other computers running the same code.
I’m not able to reproduce this issue base on the current description. But according to my experience, the error RPC_E_SYS_CALL_FAILED was usually caused by calling the object model when the Office UI was blocked by the previous operation. In this case, the
previous operation may be Calculate function. For example, if the calculation was very complex, and we tried to call the object model before the resource was released, it may throw this exception.
As a quick workaround, I think you could use try-catch statement to catch this exception and try to call the object model later.
Single-Threaded Apartments
Troubleshooting a DCOM issue: Case Study
Hope it will help.
Regards,
Jeffrey
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Switching Kepware servers in PCO

Hi Experts,
We have Kepware on a different machine and PCO on another machine. To connect the Kepware server we installed 'OPCCoreComponentsRedistributable(x86)' on the machine where PCO is installed. we were able to create a source system using the details of the kepware server. For some testing we are trying to re-point the PCO to another Kepware server. For configuring the other Kepware server, we made the changes to the 'opc_remote' file to specify the details of the other kepware server. After making the changes to the file, we re-started the server on which PCO is installed. After re-starting when i am trying to create a source system using the details of the new kepware server, i get message 'No OPC servers found on the specified machine'.
If i specify the other Kepware server that was provided earlier, i am still able to create the source system.
I know that we can connect to only one Kepware server from PCO, but is it that we cannot switch from one Kepware server to another.
We are on PCO 2.3 SP04 P7 and Kepware server is V4.190.341 - U.
Regards,
Darshan Sheth

Darshan,
For DCOM to work with PCo and Kepware, you have 2 options to configure the user access:
1. Allow full DCOM access for domain users that are members of the server Administrators group, EVERYONE, SYSTEM and NETWORK, and allow PCo and Kepware services to run under LocalSystem account (some network admins will not allow this as it opens potential network security holes)
2. Define named users or named Domain Group permissions for DCOM.
2.1. Use the named user or users that are members of the named Domain Group for the following:
    - named user for Kepware server_runtime service
    - named user for PCo Agent Instances
    - administrative user to log into to PCo remote Desktop
Avoid hosting PCo and remote OPC Servers on different Domains or on Workgroups -- should always be in the same Domain.
I strongly recommend that you migrate to Kepware V5 and investigate using the Kepware OPC UA interface along with PCo OPC UA Agent where you are going to have remote OPC Server requirements, and avoid the DCOM issues altogether.
Installing Kepware on PCo server, or PCo on the Kepware server will remove any DCOM configuration requirements.
Regards, Steve

Sharing a shared network variable between two PC's connected to a network

Sharing a shared network variable between two PC's connected to a network
Surely this shouldn’t be so difficult! I have a little LabVIEW program running in the background of PC1. The exe’s task is to collect and send OPC variables held on a SCADA system and convert them to shared network variables (as I thought that they would be easy to share over a network, easier than the nasty OPC and DCOM issues). I have PC2 which runs measurement studio and I have created a nice test VB program which either writes or reads the network variables which are on PC1. The PC1 collection software is working perfectly and when I change the values on the SCADA system I can see the network variable change on ‘NI Distributed System Manager’. I When I look at ‘NI Distributed System Manager’ on PC2 I can’t see PC1 on the list and when I use the basic measurement studio code below to read the network variable it times out at the TestVariable.connect() line.
Ok so what do I need to do to read a shared network variable sat on PC1 from PC2 on the network
Public Class Form1
Private WithEvents TestVariable As NetworkVariableSubscriber(Of Double)
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
TestVariable = New NetworkVariableSubscriber(Of Double)("\\192.168.58.139\Test\TestVariable")
TestVariable.Connect()
End Sub
Private Sub TestVariable_Data_Updated(ByVal sender As System.Object, ByVal e As NationalInstruments.NetworkVariable.DataUpdatedEventArgs(Of Double)) Handles TestVariable.DataUpdated
TextBox1.Text = e.Data.GetValue
End Sub
End Class

Sorry lost all the formatting
Surely this shouldn’t be so difficult! I have a little
LabVIEW program running in the background of PC1. The exe’s task is to collect
and send OPC variables held on a SCADA system and convert them to shared
network variables (as I thought that they would be easy to share over a
network, easier than the nasty OPC and DCOM issues). I have PC2 which runs
measurement studio and I have created a nice test VB program which either
writes or reads the network variables which are on PC1. The PC1 collection
software is working perfectly and when I change the values on the SCADA system
I can see the network variable change on ‘NI Distributed System Manager’. I
When I look at ‘NI Distributed System Manager’ on PC2 I can’t see PC1 on the
list and when I use the basic measurement studio code below to read the network
variable it times out at the TestVariable.connect() line.
Ok so what do I need to do to read a shared network variable
sat on PC1 from PC2 on the network
Public Class Form1
Private
WithEvents TestVariable As NetworkVariableSubscriber(Of Double)
Private Sub Form1_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
TestVariable = New NetworkVariableSubscriber(Of
Double)("\\192.168.58.139\Test\TestVariable")
TestVariable.Connect()
End Sub
Private Sub TestVariable_Data_Updated(ByVal sender As
System.Object, ByVal e As
NationalInstruments.NetworkVariable.DataUpdatedEventArgs(Of Double)) Handles
TestVariable.DataUpdated
TextBox1.Text = e.Data.GetValue
End Sub
End Class

Outlook 2010 attachment previewer problem

Dear All,
I recently upgraded to the office 2010 beta, and have been quite pleased with the new system, until i tried to view an image that was attached to an email. I keep getting on any type of image or pdf that the previewer is not available ad to double click to open the file. I then get photo viewer telling me it can't open the file. So i saved the file to my desktop and try to open the jpg in any program such a photshop, illustrator or fireworks and it tells me there is an unknown or invalid JPEG marker type is found."
I can't open any files that are attached to emails, which is getting really annoying now. I have tried everything i can think of, running outlook as an admin, turning off image previewers, checking image previewers are enabled, i've tried the protection settings, and disabling it for Outlook.
Nothing will work. I've searched google and found a few solutions where they say this is caused by google desktop search causing problems and that uninstalling it solves the issue, however I don't have google desktop search installed, just google toolbar.
Its starting to drive me round the bend, i've even ran and repaired the pst file which didn't make any difference either.
Have reported it as a frown but not holding my breath for a response.
System:
Windows 7 64 bit
Office 2010 32 bit beta version
The laptop is 2 weeks old from Dell and all updates are applied.
Can anyone shed any light?
Thanks
Tom

I am having a problem which is a variation on the same theme. What is even more odd is that I have a laptop and desktop which I installed Outlook 2010 on and they behave very differently. On my laptop, I can easily view all doc and docx
attachments, while on my desktop, these very same attachments are not recognized or are considered as corrupt documents. I have been fiddling around with trusted locations on my desktop (e.g., trusting my server folders etc.) but so far no success -
even after reinstallation of 2010 on the desktop. My laptop's Outlook works fine without having to trust any particular location. I installed Outlook on my desktop after doing a fresh install of the XP OS while the Outlook installation was an upgrade
of Office 2007 with a fairly weather beaten XP registry. So currently, I see no rhyme or reason except that it appears that the 2010 installation is highly highly sensitive. Hopefully there is a quick fix to this or I might also have to roll back
to an earlier version of Outlook.
Had the same issue.
Here is the fix
Hello,
I finally found out what the issue is with this. It actually isn't a "Protected view" issue, but a DCOM issue.
Somehow the DCOM permission got changed, so it wouldn't allow certain applications access to simple things like Preview mode on Outlook 2010 / 2007, or opening up attachments without it saying file corrupt. I also was having an issue with Pop ups in
IE8, where javascript messages about security tokens were not authenticated.
The solution is as follows, and then you can turn on your protected mode back on in word, excel, and your "Preview mode" in outlook will start working again.
Go to start, then run. Type dcomcnfg and push o.k. Component Services should come up.
Expand Component Services, click on Computers, then "Right click" on My Computer and go to "properties".
Click on Default Properties tab, and make sure the following is set:
Default Authentication Level: Should say Connect, not "None"
And Default Impersonation Level: SHould say Identify.
When those are set properly, hit o.k and turn on your protected mode back on your Office applications. Everything works as expected :)
Cheers :)

MII WinCC integration

Dear all,
We want to get current and historical data from WinCC.
We have MII server.
We have also WinCC server. WinCC OPC server is installed on WinCC servers.
There is firewall between WinCC and MII servers.
We installed UDS on MII server.
Questions:
1) Shoul we install UDS on MII server or WinCC server? If both is possible, which one is effective?
2) Can we read real time and historical data by only using OPC server adn UDS, without installing 'WinCC connectivity pack".
Why should I use this connectivity pack, if they use OPC standarts?
Kind regards,
Hamza.

Hamza,
1. It is always better if you can to install the UDS on the same machine as the OPC Server you are connecting to. This is more efficent as it will cause less traffic over http. Also sometimes problem occur with DCOM issues and since this would be a local install, this would be alleviated. But if not allowed then it can be installed with the MII server or even on a seperate Windows box. Note the UDS is Windows based so it must be installed on a Windows OS.
2. I am not familiar with this and would have to test in order to see if it is needed. Unfortunately we do not have a WinCC system to test this against. From reading some of the documentation it seems like this may be needed to get the OPC HDA access if needed.

Postion of UDS relative to Firewall

Hi All,
We have an requirement that all the systems communicating to DCS and QCS should be through the firewall.
where to install UDS( which commnicates to DCS and QCS)so that firewall should not affect the communication between xMII server and UDS?
few things that in place are
1. xMII server
2. OPC server( on this i belive that UDS and firewall layer will be there)
3. Various DCS systems which communicates to OPC server?
Kindly Suggest
Regards
Rupesh Bajaj

For performance and technical issue avoidance the UDS should be installed as close to the datasource as possible and therefore behind the firewall.
Communication between the UDS instance(s) and the xMII server are simply on a TCP/IP port of your choice, so configuring the firewall to allow this port level communication should be easy to do. With the undlying data source particular API's, potential for DCOM issues, etc., having this behind the firewall will be to your advantage.
Regards,
Jeremy

Remote server cannont connect to this machine

I'm using datasockets in Labview 8.5 (Evaluation copy) to develop an OPC client application
to connect with a remote OPC server running Kepware. I've tried a number of different
ways with no luck. When I try to connect using front panel connections, I get the remote server
error cannot connect to this machine (check local permissions), but in the event log, the logon
audit is a success. So I'm not sure what permissions need to be changed. So far I have changed
DCOM security settings to allow Network user, the name of the OPC server, anonymous, everyone, access
permission for both local and remote and the same in launch and activation permissions.
I've tried using the NI OPC Client example and I just get an error 42, generic error. I have spent my wheels
with this one and no prevail. I downloaded the OPC Quick Client from Kepware, which I can use to connect
to the OPC server, but I do get a Failed to connect to 2.0 data access for group ...., but it still displays the
values once the items are selected. NI Server Explorer works just fine and Iconics also. Has anyone run
into this problem before and how did you fix.
Thanks,
Jay

Typically if the Kepware OPc Quick Client cannot connect to the Kepware OPC Server there are possibly more than DCOM issues involved. The first thing that comes to mind is that the OPCproxy.dll and OPCcomn_PS.dll on the 2 PC's are out of Sequence. You can easily verify the versions on each PC.This files should be located in the system32 folder.
The next thing we usually check is that Ole32.dll and OleAut32.dll are properly registered on both PC's.
To do this, go to the command prompt.
Tyep regsvr32 ole32.dll
A dialog box should appear saying: DllRegisterServer in ole32.dll succeeded.
Click OK.
Now type regsvr32 oleaut32.dll
A dialog box should appear saying: DllRegisterServer in oleaut32.dll succeeded.
Click OK and type exit to close the command prompt window.
Reboot and try to connect to the server again.
Remember these files need to be properly registerd on both PC's.
If that does not work then you can always go the rout of opening DCOM as wide as possible. Things to consider are as follows.
COM/DCOM, which is what OPC uses as a core technology, does not work well, and usually not at all, across multiple domains.
It is intended for use in Domains which have a central Access Control List. If you are using a WG(WorkGroup) or WG to Domain or Domain WG you need to make sure the OPC users in the Domain are built into the local security account of the WG PC(s).
To open security wide, which should only be done on a secure network, You need to have System and Everyone with Launch and access permissions on all PC's involved in the OPC connection. You should set this at the computer level and not the application level.
We have found that for reasons only known to Microsoft we sometimes need to set Local Securty Policies. Specifically we see a need to sometimes Enable "Network Access: Let everyone permissions apply to anonymous users" and set "Network Access: Sharing and Security Model for local accounts" to "classic - local users authenticate as themselves".
With recent Microsoft security patches we have seen in some cases a need to add Network Users for Access and Launch Permissions.
If you have a secure network you can also add Domain Admins and Domain users.
Once you have achieved an OPC connection and transfer of data between KepserverEx and you OPC clients you can then start to restrict DCOM permissions again.
If you have any further questions about using KepserverEx with OPC Clients you can contact [email protected]
Fred Loveless
Support Manager
Kepware Technologies
http://www.kepware.com
Fred Loveless
Kepware Technologies
http://www.kepware.com

Error Event id 7031 and 10016 occurring again and again in w2k8 r2

Hi,
Error Event id 7031 and 10016 occurring again and again in w2k8 r2.
I have tried to rejoin the domain, gpupdate but nothing resolve these two error event ids from VM. Can anyone help me out on this.
**___ Event id 10016**____
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{24FF4FDC-1D9F-4195-8C79-0DA39248FF48}
and APPID
{B292921D-AF50-400C-9B75-0C57A7F29BA1}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event id 7031 -->
The SMS Agent Host service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.
Inder Johar

Hi,
Do you install Antivirus Symantec on your server? If so, uninstalled the Antivirus Symantec and rebooted the server to see if the issue still exists.
You could refer to the thread below to changed permissions registry HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{B292921D-AF50-400c-9B75-0C57A7F29BA1} to check the result:
Windows Server 2008, SCCM 2007 DCOM Issue
http://social.technet.microsoft.com/Forums/systemcenter/en-US/5bf4a668-fe71-4f23-8932-dd727a1bcfa3/windows-server-2008-sccm-2007-dcom-issue?forum=configmgrgeneral
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DCOM 10009 error after renaming local computer name. (No network computers involved in this issue)

The DCOM 10009 error generated references the previous name of the computer. Here is the scenario:
These aren't the real names of the computer). The computer was named
computerX-NEW and was renamed to computerX during deployment setup. The DCOM error states "DCOM was unable to communicate with the computer
computerX-NEW using any of the configured protocols." When I look at the error details, a PID is referenced which turns out to be the RPCSS process/service. I suspected a piece of software that was installed on the computer until I performed
a Clean Boot with all startup programs disabled and all non-Microsoft services disabled. The error still occured. Also the error is occuring about 5 or 6 times per minute. The only thing I can start doing at this point is disabling MS services at boot to find
the culprit, but I'd like a less brutal approach to correct the issue. Any suggestions?

Hi,
The following are possible causes of this error:
1. Name resolution errors are occurring.
2. All TCP ports on the server are being used.
3. TCP port collisions are occurring.
4. The network connections may not be configured properly.
To troubleshoot DCOM 10009 errors, use the following methods.
Method 1: Verify that name resolution is working correctly
The activation page for a COM+ proxy application contains a Remote Server Name (RSN) property. The RSN property can be an IP address, a Fully Qualified Domain Name (FQDN), or a NetBIOS name. To troubleshoot this issue, use the ping command to test connectivity
to the remote server by using the IP address, the FQDN, and the NetBIOS name.
Method 2: Verify TCP port usage
When a client makes DCOM calls to a COM+ server application, each connection may use a different TCP port. Therefore, all TCP ports on the server may be used. When this condition occurs, the server cannot accept additional connections.
Method 3: Verify basic network connectivity to troubleshoot TCP collision issues
Method 4: Check the network connections. Check the Registry under HKEY Local Machine/Software/Microsoft/RPC/DCOM Protocols for the list of RPC protocol sequences.
For further troubleshooting information, please also refer to the following Microsoft article:
Known post installation event errors in SBS 2008 (and how to resolve them)
http://blogs.technet.com/b/sbs/archive/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them.aspx
Hope it helps.
Regards,
Blair Deng
Blair Deng
TechNet Community Support

2008 R2: OS(systemState/C: Drive) backup issues with VSS - 0x80042316 & 0x81080101 & 0x80080005 & 2155348001

Hi-
Looked thru the thread related to my questions and found nothing that applies yet.
Example:
http://social.technet.microsoft.com/Forums/en-US/4e4472b9-8e6f-4fdc-a287-1cc8c0f6de09/windows-2008-r2-backup-fails-with-event-521-error-code-2155348001?forum=windowsbackup
http://social.technet.microsoft.com/Forums/en-US/e8c910f7-f0dd-4613-beae-b98894fb6f23/windows-server-2008-std-backup-fails-constantly-with-error-code-2155348001?forum=windowsbackup
Here are details of the issues....
Backup - OS error - system image:
External disk - USB
Mon - Fri @ 6PM.
Windows SystemState
OS(C:)
Last backup failure...
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
[Critical error WINIMAGE_UNABLE_VSS] Unable to create VSS snapshot
- Additional information: Refer to the log for more details
- Troubleshooting link:
http://kb.backupassist.com/errormap.php?BA2512
The backup operation stopped before completing.
Detailed error: ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-12-08-2014_04-41-00.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-12-08-2014_04-41-00.log
NOTE:
The errors logs are not there?
Windows Backup timed-out before the shared protection point was created.
ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Event Viewer Log:
Sequence of Events...
1.
The Block Level Backup Engine service has successfully started.
2.
Backup operation that started...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 4:51:06 AM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The backup operation that started at '?2014?-?08?-?12T09:41:00.492000000Z' has failed because the
Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed
with following error code '2155348001'.
Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
--> Suggestion are to check Virus scanner or consult DPM forum...
3.
OS Job failed with errors...( Backup Assist is 3rd party backup - wrapper round Wbadmin/Win Backup)
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:51:51 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job OS backup failed with errors.
Critical error: Unable to create VSS snapshot
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
4.
Backup Assist reports via Win backup - Snapshot in progress
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:52:20 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job Data backup failed with errors.
Ultra critical error: Volume Shadow Copy Error 0x80042316 - snapshot set in progress
Destination: Local directory
Start time: 8/12/2014 4:52:10 AM
End time: 8/12/2014 4:52:12 AM
Duration: 00:00:02.7300000
5.
The Block Level Backup Engine service has stopped.
6.
Later...we tried manually stopping VSS and SWPRV services - only VSS had the issue.
WBengine was not running...
C:\>sc stop swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query wbengine
SERVICE_NAME: wbengine
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query vss
SERVICE_NAME: vss
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc stop vss
[SC] ControlService FAILED 1061:
The service cannot accept control messages at this time.
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:20:33 AM
Event ID:      8225
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The VSS service is shutting down due to shutdown event from the Service Control Manager.
7.
VSS still having issues here...not stopping!
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service information:
The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started.
Most likely the CPU is under heavy load. [0x80080005, Server execution failed]
8.
Not sure why this is started again?
Plus a DCOM timeout...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:31:13 AM
Event ID:      753
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has successfully started.
Event Xml:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          8/12/2014 9:31:43 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The server {E579AB5F-1CC4-44B4-BED9-DE0991FF0623} did not register with DCOM within the required timeout.
9.
Lots more errors about VSS...repeating Event ID's 11 and 8193...
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
hr = 0x80080005, Server execution failed
. Operation:
   Instantiating VSS server
10.
Then, finally stopping again...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:51:13 AM
Event ID:      754
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has stopped.
11.
And still repeating 11 & 8193 at this point...as we write up this post.
12.
This was suggested by the Backup Assist - software vendor....
A.)
...for 0x81080101:
"ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try again this operation."
If you receive the above error in your report, we have recently found a registry key which
contains the timeout value set by Microsoft for VSS and found that you can edit this to extend it.
To get to the registry key, open Regedit (Start > Run > Regedit) and browse to:
"HKLM\Software\\Microsoft\\Windows NT\\CurrentVersion\\SPP\\CreateTimeout".
Change value to 1200000 (2*10*60*1000 = 20 mins).
The default for the timeout period is 10 mins so hopefully doubling this will give enough time to
complete the snapshot.
If this isn't present, you'll need to manually enter the registry key. It's a DWORD 32-bit key.
--> NOTE: HAve not done this yet.
B.)
And for 0x80080005...
http://support.microsoft.com/kb/870655/en-gb
Our server does have high CPU load at times...
13.
Another post from technet mentions system volume size - here is our layout below:
A.)
OS/system Disk...
DISKPART> list disk
Disk ### Status         Size     Free     Dyn Gpt
Disk 0    Online          278 GB      0 B    (System Vol = C: Drive - OS w/ Programs and batch jobs)
Disk 1    Online         2791 GB      0 B        *    (Data drive - DFS, rsync,etc. run on D: Drive)
Disk 2    Online         1863 GB      0 B    (USB 2/3.0 - Enclosure w/ SATA disk = 2GB formatted w/ NTFS.)
DISKPART> detail disk
DELL PERC H710P SCSI Disk Device
Disk ID: CA0DEEA5
Type   : RAID
Status : Online
Path   : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0100)#PCI(0000)#RAID(P01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 1         RECOVERY     NTFS   Partition   3072 MB Healthy    System
Volume 2     C   OS           NTFS   Partition    275 GB Healthy    Boot
B.)
Backup disk...
ST320006 41AS USB Device
Disk ID: 801AF48C
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 4     F   BACKUPS      NTFS   Partition   1863 GB Healthy
C.)
NOTE:
Also on disk 0(system Disk) - we have a small OEM partition = 39MB and a Recovery Partition = 3GB.
D.)
Issues with WBAdmin now...
C:\>wbadmin get disks
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x80042302)
A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
14.
Ran "Check-Disk" -no errors...
C:\>chkdsk
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
116224 file records processed.
File verification completed.
654 large file records processed.
0 bad file records processed.
0 EA records processed.
76 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
156676 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
116224 file SDs/SIDs processed.
Security descriptor verification completed.
20227 data files processed.
CHKDSK is verifying Usn Journal...
35628352 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
289233919 KB total disk space.
100241492 KB in 85477 files.
     57380 KB in 20228 indexes.
         0 KB in bad sectors.
    226627 KB in use by the system.
     65536 KB occupied by the log file.
188708420 KB available on disk.
      4096 bytes in each allocation unit.
72308479 total allocation units on disk.
47177105 allocation units available on disk.
15.
There are no backup error logs here - only .etl files...
C:\Windows\Logs\WindowsServerBackup\
Wbadmin.1.etl = 9:42AM on 8/12
Wbadmin.2.etl = 4:51AM on 8/12
Per windows Win troubleshooting:
http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
--> Related to Windows backup and not VSS?
2155348001 - 0x80780021 - Windows Backup timed-out before the shared protection point was created.
Should we run the "FIXVSS08.BAT" script - restarts services and re-registers DLL's - does this ever help?
Will this server need a reboot since VSS is in a state and we can't even test backups?
Is there a tool we can use to debug VSS or troubleshoot or OS backups further?
MSReport/Diag, VSS debugging, or another way of helping fix our OS(SystemState/C: drive) backup issues?
Any help is greatly appreciated - thx.
-SP
Scot Pichelman

Hi Scot,
Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
after testing.
And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
If issue still exists, please try the steps below as well:
1. Please check DCOM Server Process Launcher service is started.
2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
Note: Backup the key before edit incase it cause any issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
Find "ObjectName" and change the value to LocalSystem.
Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
If DCOM still not work, please compare the content of the following key with a working server:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Edit if there is any difference and make sure you created a backup of the key before editing.
If you have any feedback on our support, please send to [email protected]

DCOM error "1260" on Windows 2008 R2 terminal server when SAP exports data into Office 2007 (Excel or Word)

Hi all,
We are experiencing an issue which happens at random whenever a user tries to export data from SAP into Excel or Word. Excel or Word is started but remain empty. We then see the below errors in the event log. And the problem is very random
as sometimes all they have to do is wait 10 minutes and the next try will be successful. Not even log off/on. Could someone tell me what the error "1260" is saying?     thanks for your help.
Pete
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          7/23/2013 4:07:36 PM
Event ID:      10000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Servername.domain.com
Description:
Unable to start a DCOM Server: {00020906-0000-0000-C000-000000000046}. The error:
"1260"
Happened while starting this command:
"C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE" -Embedding
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          7/23/2013 3:54:34 PM
Event ID:      10000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Servername.domain.com
Description:
Unable to start a DCOM Server: {00024500-0000-0000-C000-000000000046}. The error:
"1260"
Happened while starting this command:
"C:\Program Files (x86)\Microsoft Office\Office12\EXCEL.EXE" /automation -Embedding

Hi,
Based on my research, please try the following:
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\termsrv
Under this subkey, add the following registry entries:
Name
Type
Value data
Logoff
REG_SZ
TSEventLogoff
Logon
REG_SZ
TSEventLogon
Restart the Terminal Server computer.
Note: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry
before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, please refer to
How to back up and restore the registry in Windows.
Hope this helps.
Best Regards
Jeremy Wu

DCOM issue

Similar Messages

Maybe you are looking for