PXI-8187 System state: Unconfigured

Bonjour,
j'ai un problème au boot avec mon controleur PXI-8187 dans un chassis PXI-1000B
message affiché:
Labview RT Boot Loader
(C) Copyright ....
Intel 8255x Ethernet found.
Initializing network ... done: IP address is 0.0.0.0
System state: Unconfigured
Merci pour votre reponse
Cordialement.

Bonjour,
Tout d'abord, il faut connecter votre contrôleur à un PC Host. Sur ce PC Host, il faut que LabVIEW RT (même version que sur votre contrôleur PXI) et MAX (Measurement and Automation eXplorer) y soient installés.
1/ Dans MAX, allez à la rubrique "Systèmes déportés" ainsi votre contrôleur doit apparaître sous cette arborescence.
2/ Une fois votre contrôleur sélectionné, dans la partie droite de MAX, pour configurer l'adresse IP de votre contrôleur, sélectionnez l'obtention d'une adresse IP en DHCP. Afin d'avoir les mêmes paramètres réseau que le PC Host.
3/ Cliquez sur le bouton "Appliquer"
4/ Redémarrez votre contrôleur.
Lors du redémarrage de celui-ci, l'adresse IP configurée précedemment dans MAX, doit apparaître sur l'écran de votre contrôleur.
Ensuite, pour l'utilisation de vos cartes PXI de votre chassis, vous devez installer les drivers correspondants à ces cartes en allant dans la partie "logiciels" de voter contrôleur puis en cliquant sur "Installer". Attention, il faut que les drivers soient installés sur le PC Host et soient plus récents que Novembre 2003.
De plus, voici une :note d'application en anglais reprenant ces différents points.
Salutations,
Isabelle
Ingénieur d'applications
National Instruments France

Similar Messages

How to use SMB trigger input on PXI-8187 in LabView

Hello!
I have PXI-8187 controller instaled in PXI-1031 and two PXI-4071 digital multimeters. I want to trigger mesurement with external trigger. One way is to used AUX port on DMM, another can be TRIG input on PXI 8187 CPU unit. Is possible to use this possibility in LabView 7? How?
Best regards!

There are multiple reasons why this is not a supported feature for triggering under Windows and why NI does not recommend using the controller's SMB connector for this purpose. National Instruments has hardware that was designed specifically for extremely accurate clock generation, synchronization, and triggering between PXI chassis (PXI-665x) and other recommended alternatives listed below.
Non-deterministic propagation delays
1. The controller's SMB input is not guaranteed to have a defined propagation delay to the backplane. This means the SMB trigger on the Windows PXI controller is useless for customers that want deterministic triggering. Unlike our PXI-665x boards which have a maintained API and precise triggering properties, the PXI controller's SMB connector and routing circuitry is intended for Watchdog use under LabVIEW RT and isn't designed for this use case. A trigger propagating through the SMB circuitry and going to the backplane, or vice-versa, could have a great deal of variance in the propagation delay which makes gathering useful triggers impossible. This propagation delay is not something National Instruments specs.
An excellent available workaround: Use the measurement hardware's trigger inputs
2. The triggering inputs on our measurement hardware (that customers likely have in their system) can route triggering signals to the PXI backplane (usually through PFI lines) with deterministic results. This functionality is fully supported in most of our APIs and will be maintained between generations of devices.
NOT backward or forward compatible
3. The SMB input is NOT guaranteed to be compatible between different versions of our PXI controllers under Windows. The hardware properties along with an excellent workaround are the reason we do not support doing routing of triggers through the SMB connector on our PXI family of embedded controllers under Windows. If you are still interested in the beta software despite the shortcomings, visit www.ni.com/support and submit an e-mail request.
Adam Ullrich
PXI/VXI Product Support Engineer
National Instruments

PXI-8187 alwayes boot RT in safe mode

Trying to boot RT on PXI-8187 controller with original setup, what ever RT boot selection is used either hardware switch or BIOS RT boot option, the terminal will show the following:
Unable to load LabVIEW RT from drive!
Booting safe mode from ROM...
mount: Mounting /dev/Ma1 on /home/ftp/c failed: Invalid argument
Entering safe mode.
IP address is: 0.0.0.0
Of course after that you can't do any thing to configure the RT target from the MAX on the host computer.
Please Help.

Thanks,
The initial was NTFS but it has evolved:
I used the recovery CD to change the file system to NTFS, it took a while and it installed windows XP from scratch differently from FirstWare that ghosts it (I think). And it didn't install any NI stuff what so ever.
At the end I got the same result as with using the remote system format disk option.
i.e. The RT controller boots in safe mode displaying the previous message without the mount error but this time I can configure the IP address.
Still I can't install software to it, I get the list of features to install, I select them and press next, then I get a dialog saying:
Cannot process install because other dependencies are required:
LabVIEW RT 1.0.1
LabVIEW RT 6.0.1
LabVIEW RT 6.1.0
LabVIEW RT 7.0.0
LabVIEW RT 7.1
Is this a host or RT Controller issue now?
What's next? Thanks for the help
manora

Upgrade Host-PXI 8187

I have a PXI 8187 connected to a computer (p3-400) with the operative system Win2000 that is a little finds a little outdated. So I acquired a new computer (p4d-3G) in which I intend to install the operative system WinXP SP2 and labview 7,1 (and still Max 3.1.1.3003 and ni-daq 7,3 at least). After all the installation I verified that the linking of the two if made using labview work fine, however max/ftp has very slow answers (the transfer is +-6kB/s with a linking 100mbits between both).
Will it be necessary to format the PXI and make a similar installation to the host computer?
Many thanks Luis Noites

Hello Mathieu STEINER, I didn’t reply directly to your email because you didn’t send it to me (after this I talked with the others and them said the mail arrived only to them), sorry.
Best regards, Luis

How to Delete Non-System State Backups in Windows 2008R2

Hello,
I am running a Windows 2008R2 server which uses Windows Server Backup to do the backups. We are using the backup-tool to create non-system state backups of the data-directories on this machine. The backup is done on a dedicated disk connected through iscsi
(to a Synology box). This backup disk has become too small and we have now replaced the Synology box with a bigger one. Here i created a new LUN again for the backup purposes.
Now for my question; The wbadmin.exe tool supplied with W2008R2 does not offer a way to delete the old backups. I know that in Win2012 (which we we also have running) I could add the new iscsi location and then (when enough backups are available on the new
target) use wbadmin.exe delete backup to delete the old non-system state backups; e.g.
wbadmin delete backup -version:08/07/2013-21:00
This (very undocumented) feature of Windows 2012 and higher works quite nice and is exactly what i am searching for on the W2008R2 machine; a way to delete the old backups (and under the hood delete the corresponding snapshots)
I've done quite a bit of research and it should be possible to do something similar in 2008 but then manually, The howto is described in the following link: http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx .
Basically it describes that you should use DiskShadow.exe to remove e.g. the oldest snapshot with a command like :
Delete shadows OLDEST \\?\Volume{7fc1871b-2e1f-11dd-a339-001e4fb7af35}
Windows Server backup (wbadmin) should then on the next run 'see' this deletion and update its list of available backups:
"You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during
the next backup."
I've done this on our box and it indeed removes the shadows from the list. However, in the Windows Backup 'dashboard' it still lists the backups as available. Also after a new backup has finished (according the the article this is when it should 'update'
its backup catalog). When I try to restore a backup from a date that i just removed it gives a nice message that this is impossible because the snapshot is not available (duh :)) ;
Unable to browse Local disk. The shadow copy of the backup stored on the backup destination cannot be found.
So it seems that the aforementioned method works; it removes the snapshot and frees diskspace, but it doesn't update the Windows Backup catalog. As a result the management tool (GUI) still lists the backups which are no longer available! How can i change
this? Is there any way to do this? I found one article which mentions that the Dashboard bases its screen on the Windows Logs and not on the actual VSS snapshots available:
http://forum.wegotserved.com/index.php/topic/23757-start-afresh-with-server-backup/ (WHS) In my situation however this seems unlikely because i don't have any logs that date back as far as my backups go.
In my opinion this is a real bug and it leaves us with a in-consequent backup schema. Does anyone have similar situations or even a solution to my problem?
Kind Regard, Martin

Hi Mandy,
Yes! I think i got my answer and I now get how windows backup works in Windows 2008 :-) It turns out that I dismissed some suggestions a bit too soon. The answer lies in the command mentioned earlier :
Wbadmin delete catalog
This command does delete all the backups from a perspective of the Windows Backup UI, but leaves the VSS snapshots intact. This means that the backups are still available, but you just can't restore them with the User Interface. In order to 'update' the
UI with the current available snapshots (which you can list with diskshadows list shadows all), you have to re-add the existing media on which the backups took place using the Wizard of the UI. It will then inform you that existing backups are available and
if you want to keep these for restore purposes. If you click 'yes', and THEN perform a backup ... All the current available backups will be shown in the User Interface :-)
So for my steps taken to change from one iscsi (iscsi1) to another (iscsi2):
- Add the 2nd iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Add more backup destinations -> iscsi2
- Remove the 1st iscsi target with the Windows Backup UI
using Backup schedule , Modify backup -> [desired options] => Remove current backup destinations -> iscsi1
- Run some backups on the new destination. Old restore points are now still available. When enough restore points are available on the new volume iscsi2 start deleting old data from iscsi1 as follows:
- Run diskshadow
diskshadow
- list all the current snapshots
list shadows all
- remove all the snapshots of iscsi1 (repeat until all shadows are gone of iscsi1)
delete shadows oldest \\?\volume{yourvolumeid}\
- delete the windows backup catalog
wbadmin delete catalog
- Restart the windows backup UI and re-add your schedule on the new volume iscsi2. It will now ask if you want the keep the existing data for restore purposes; click yes.
- After the next backup only the backups of volume iscsi2 will be listed and everything is fine !
I Hope my post will help others with similar questions. It was quite a search before I understood the way it works. Basically as long as your VSS snapshots are still available and listed by diskshadow you still have the backups and you will be able to get
this in sync with the steps above (delete schedule and re-add originating targets containing the snapshots). After the next backup the UI will update itself.
(In my case someway along the way I lost my originating snapshots, but because I already had my new backup set it didn't bother me; It kept me from having to delete all 510 old backups :) with diskshadow)
Regard, Martin

Remote system state

i want to know whether the remote system state on or off. any body help me to find remote system on or off state using java.net package. no need to use RMI concepts.

udhaya_Sri wrote:
i want to know whether the remote system state on or off. any body help me to find remote system on or off state using java.net package. no need to use RMI concepts.I doubt it (not a foolproof one anyway), and it would be likely to be system-dependent (and if I was the administrator, I'd probably turn it off).
ping usually works, but again, some systems may have it turned off. Some systems (like Unix) also provide an 'isalive' command, but it's probably based around ping.
Winston

Windows "Blue screen of Death" when booting computer attached to LabVIEW PXI realtime system

Good Morning (at least in the western hemisphere)!
I'm having a problem on two test systems where intermittently, at least on one machine, I get a Windows "Blue Screen of Death" error message when booting the machine connected to a PXI RT system. I reloaded the RT systems software yesterday (LV RT 7.1.1, NI-VISA 3.3.1) and am having this problem on two different setups, two laptops, two PXI chassis. Our short term work around has been to boot with the network cable removed at one end or the other, but these are the baseline models for a larger test system in the design/construction stage that will not be used by knowledgeable engineers but by (probably more knowledgeable!) technicians. Any ideas would be a help
Thanks again,
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Blue screens are almost always caused by drivers and not by applications, so chances are there's a problem on the driver level. The crash log file will be instrumental to diagnosing this problem.
Turn on the crash event logging as described in this Microsoft KB:
http://support.microsoft.com/kb/314084/EN-US/
...and then post the details from the crash found in the Windows Event Viewer here. That will help us narrow the problem down.
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

Has anybody had an issue with System State Backups on a Dell PowerEdge R510 Server running Server 2008 R2?

Hi,
We have recently had issues running system state backups on our 2008 R2 Domain Controllers.  They are running on Dell PowerEdge R510 Physical Hardware. Whenever you initiate a system state backup, the Domain Controller becomes unresponsive
forcing us to physically reboot it.   Nothing in the Event logs or the Dell Open Management Hardware Software indicates issues with Phyiscal disks but we can always replicate the issue by starting the system state backup.
The system state backup is initialted as a batch file that runs as a scheduled task.   the commands run are as follows:
WBADMIN START SYSTEMSTATEBACKUP -backupTarget:[drive letter] -quiet
We have 4 Domain Controllers with identical disk configurations. When the DCs were setup I confirmed the system state backups were working but the issue started occuring sometime in Dec 2014. We are going to run the Dell Hardware Update Utility
to update the RAID, BIOS, Firmware updates but Has anyone experienced a similar issue that may have been triggerd by a Microsoft Patch?
Thanks,
Kevin C.
kconway@fnalgov

Hi Kevin,
This issue could be due to the Mountmgr.sys driver incorrectly maintains a global mutex. This behavior causes a deadlock situation in the Mountmgr.sys driver.
Please install the hotfix in the article below to resolve the issue:
A computer stops responding because of a deadlock situation in the Mountmgr.sys driver in running Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2614892
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Compare system state (number and types of objects in memory)

We have 2 exactly identical servers running our application talking to the same database.
When some obejct from server 1 is deleted, a message is passed to server 2 to delete the object from its cache too.
Forget the database, I want to design a testing system which compares the system-state (number and type of live-objects) in memory for server 1 and server 2 after the operation and the message, and reports any discrepancy.
Any ideas ?

Are you trying to debug a distributed cache implementation?
If you want to inspect the state of your application on multiple servers creating a JMX bean might be a solution.
http://java.sun.com/developer/technicalArticles/J2SE/jmx.html

Wbadmin System State Backup "Parameter is incorrect"

Hello,
We have two physical Windows Server 2008 R2 x64 Standard Domain Controllers and the system state backup on both fails with the same error.
We issue the command:
wbadmin start systemstatebackup -backuptarget:c:
(NOTE: We did the REG fix to allow backups to the system volume)
and we get this as the output:
C:\Windows\system32>wbadmin start systemstatebackup -backuptarget:c:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Starting to back up the system state [28/02/2010 21:26]...
Retrieving volume information...
This will back up the system state from volume(s) System(C:) to c:.
Do you want to start the backup operation?
[Y] Yes [N] No y
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Please wait while system state files to back up are identified.
This might take several minutes...
Summary of the backup operation:
The backup of the system state failed [28/02/2010 21:27].
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-28-02-2010_21-26-31.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-28-02-2010_21-26-31.log
The operation ended before completion.
The parameter is incorrect.
C:\Windows\system32>
This happens on both servers and the two backup log files mentioned in the output are both empty.
There's no other information that I can find so I don't know what the "parameter" is or why it is incorrect.
Has anyne come across this problem and know what the error is referring to?
Thanks
Sunil

I received a PowerShell script from Suhas and ran it on the affected server, the script output gave:
1.
     Service Name    : RMAGENT
     Service Caption : RMAGENT
     Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
     Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
     Reason          : The service path contains a double slash. Network paths or paths containing a double slash are not supported.
2.
     Service Name    : RMAGENT
     Service Caption : RMAGENT
     Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
     Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
     Reason          : The service path does not have a proper path format. Only paths beginning with [<Drive>]:\ format are supported.
The "RMAgent" is from Microsoft Data Protection Manager 2007 System Recovery Tool (DPM-SRT) and I think is the remote agent that DPM-SRT uses to backup the remote system.
The DPM-SRT RMAgent isn't supported and doesn't work on Windows Server 2008 R2 systems and I am not sure how it ended up installed on the server. Removing this service should solve the problem and allow the System State Backups to work. The DPM-SRT agent wasn't listed in the "Programs and Features" and so couldn't be installed from there (if it was I would have spotted this a long time ago and probably solved the problem). Instead, I used the information at:
http://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/
To delete the RMAgent service: sc delete "RMAgent" in an Administrator CMD prompt. This removed the registry entries shown in the script output above. When this was done, I ran the script again just to be sure there was nothing else and indeed the RMAgent entries had gone and there were no other items that needed attention.
Finally, I tried "webadmin start systemstatebackup -backuptarget:C:" again in an administrator CMD prompt and it completed successfully.
I would like to thank Abhinav Mathur and Suhas Rao in particular for their very helpful script.
Sunil

System Stats opinions Please - WORKLOAD vs. NOWORKLOAD?

Dear Experts,
Bit of a background - We've a big (10TB) 10.2.0.5, 5 node RAC system for a big Oracle eBusiness Suite (R12 - HRMS/Payroll) implementation and at the minute we are running on some old (2 years old) gathered NOWORKLOAD system stats and since then a significant underlying IO infrastructure change has gone in and we are planning to upgrade the underlying server infrastructure from IBM P5 to IBM P7 soon as well (which introduces significant CPU changes etc.) and me personally think its the time to let Oracle know about all these changes under the carpet by updating the System Stats and since its likely going to be a significant change as potentially all the plans will be impacted (and few/some might go in an unintended direction) so want to know your opinion on these questions about it please :
1. Shall we just update the Noworkload Stats and leave it as it is (db_file_multiblock_read_count in left unset i.e. left for the system to set automatically).
OR
2. Shall we go for the WORKLOAD stats instead? If we go this way then I am planning to go by the brilliant strategy mentioned by Christian Antognini in his lovely book 'Troubleshooting Oracle Performance' for stability point of view.
3. We are planning to go 11g (11.2.0.2+) in the 2nd half to next year as well - is better to leave this evil till then if 11g introduces or improves the system stats mechanism significantly? An opinion favoring this is also that we'll get better and more robust testings done if we pile it on 11g project so may be a bit safer approach (and better for work/human resources planning as well).
Out of the 5 RAC nodes, 2 are dedicated to OLTP stuff, 2 for Batch (Payrolls etc.) and 1 for (low priority) Reporting so obviously there are concerns around getting to a setting that's going to be the best fit for all of them and since thats not easy to achieve the risk is higher.
I am sure I am not new here and some of you'd have come across these questions as well so am wondering if I can get some opinions or advices please? Particularly from the people who have gone from NOWORKLOAD to WORKLOAD (preferable eBusiness suite and even better HRMS/Payroll) please and also from the people who've distributed workload like we have on difference RAC nodes- if they can share their experiences on how did it go for them - that'll be good please? (Obviously everyone's system is different and so is everyone's workload but if 8 out 10 say its been good for them or even bad - then that gives a bit of a feel about it).
Or are most people still running on 'safer' NOWROKLAOD stats please becs WORKLOAD is deemed to be a bigger change?
Also, in the end - I've heard some not so great stuff about IBM P7 as well - just wondering if there are people out there with some experience on these as well please?
Thanks in advance.

pdthedba wrote:
3. We are planning to go 11g (11.2.0.2+) in the 2nd half to next year as well - is better to leave this evil till then if 11g introduces or improves the system stats mechanism significantly? An opinion favoring this is also that we'll get better and more robust testings done if we pile it on 11g project so may be a bit safer approach (and better for work/human resources planning as well).Be careful about gathering system statistics in 11.2.0.2. Why? Well there is a bug.
Workload System Statistics Bug in 11.2
However, as of earlier this year there is a patch to fix it: 9842771.

System State Backup fail. Writer name: 'NTDS' : State: [11] Failed : Last error: Non-retryable error

Hello!!! Everybody,
I have Win Server 2008 R2 contain Domain controller (No Hyper-V). I have to take "SYSTEM STATE DATA BACKUP". I have ran following command on this Server.
c:\>wbadmin start systemstatebackup -backuptarget:d:
but backup was not successful & I got following error in command prompt.
" A VOLUME SHADOW COPY SERVICE OPERATION HAS OCCURRED : <0X800423f4>. THE WRITER EXPERIENCED A NON-TRANSIENT ERROR. IF THE BACKUP PROCESS IS RETRIED,THE ERROR IS LIKELY TO REOCCUR."
I also ran following command to know exact problem.
c:\>vssadmin list writers
I got following error
Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {21c57902-5037-467b-b9a3-72ed41c9723e}
   State: [11] Failed
   Last error: Non-retryable error
I also checked Event Viewer & got following 3 noserror.
(1) Event ID : 8229, Source : VSS
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely reoccur.
Process ID : 608
(2) Event Id : 412, Source : ESENT. Task Category: Logging/Recovery
lsass (636) Unable to read the header of log file "\\?\Globalroot\device\harddiskvolumeshadowcopy2\Windows\NTDS\edb.log".Error:546
(3)Event Id : 521 Source : Backup
The backup operation that started at '‎2014-‎05-‎13T01:44:31.444000000Z' 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 '2155348129'. Please review
the event details for a solution, and then rerun the backup operation once the issue is resolved.
I have also restart the server but problem is not resolved. I have no SQL in my Server.
I also re-register the VSS components with the help of following website.
Website Link : https://kb.acronis.com/content/45776
You are requested please solve my problem on very urgent basis.

You can refer below link for your issue
http://waynestorey.com/blog/2012/01/18/windows-backup-fails-with-event-id-521-error-code-2155348129/
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

DPM 2012 R2 failing on backup of BMR and System State

We are running DPM 2012 R2 on Windows Server 2012 and I am trying to protect another Windows 2012 Server with a Bare Metal Recovery and system state but it fails on initial synchronization. I get the following error in DPM:
DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup. On protected computers running Windows Server2008, verify that Windows Server
Backup (WSB) is installed and that it is not performing any other backup or recovery task. (ID 30214 Details: Internal error code: 0x80990ED0)
This is a new server and there is 65.7 GB of 99.9 GB free on the C drive. 131 of 136 GB free on the F drive. The P drive only has 100 MB free of 36.3 GB but that is where the pagefile is located, nothing else is on the P drive.
Would that be a problem or is that irrelevant?
The replica volume is 30 GB and the recovery point volume is 6.06 GB. I tried increasing the replica volume all the way up to 200 GB and the recovery point volume to 30 GB but that didn't matter.
Why is this not working?

Hi,
Try this and troubleshoot any errors along the way.
1) Set up a network share on a remote machine
\\server\bmrshare
2) From an administrative command prompt on the Protected Server you want the BMR backup for, type:
wbadmin.exe start backup -allcritical -backuptarget:\\server\bmrshare
This should show you the list of volumes included in the BMR backup and ask "Do you want to start the backup operation?. - Type
Y to continue..
3) Once completed, see how large the BMR backup is on the remote server, then resize the DPM replica accordingly to accommodate the size of the manual BMR backup.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 CU 4 - issue w/ system state backup completing on non domain servers with T2embed.dll

I am really new to DPM and just took over a system that has servers being backed up that are not part of the domain. The volumes backup fine and system state will not complete. In looking at the protection group server the WindowsImageBackup folder is created
and the backup starts however it will fail and DPM server will say Replica is inconsistent. Back on the protected server in the backup event log, it fails w/ error code 2155347997. In the backup error log file in C:\windows\logs\windowsserverbackup.
It says "Error in backup of C:\windows\system32\t2embed.dll during read. Error [0x80070005] Access is denied.
We have about 4 other servers that are not domain joined and they are getting similar errors w/ t2embed.dll in that system32 directory or in the WinSXS folder. All servers are 2008 SP2 or 2008 R2 SP1.
Thank you in advance for you help

Hi,
DPM has no control over errors that Windows server backup receives, but check permissions and Remove the DENY permission for EVERYONE on the below files:
C:\Windows\system32\t2embed.dll
C:\Windows\winsxs\amd64_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_13e628b635935244\t2embed.dll
C:\Windows\winsxs\x86_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_b7c78d327d35e10e\t2embed.dll
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Windows Server 2008 R2 - System State Backup - Application Log: CAPI2 513

When performing a system state backup from wbadmin, I get...
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Please wait while system state files to back up are identified.
This might take several minutes...
Summary of the backup operation:
The backup of the system state failed [12/15/2011 6:38 PM].
Log of files successfully backed up:
C:\windows\Logs\WindowsServerBackup\Backup-15-12-2011_18-38-05.log
Log of files for which backup failed:
C:\windows\Logs\WindowsServerBackup\Backup_Error-15-12-2011_18-38-05.log
The operation ended before completion.
The system writer is not found in the backup.
In the event log, I get...
Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: 12/15/2011 6:38:24 PM
Event ID: 513
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server1.domain.com
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details:
AddCoreCsiFiles : GetNextFileMapContent() failed.
System Error:
The parameter is incorrect.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
<EventID Qualifiers="0">513</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-12-15T23:38:24.430498600Z" />
<EventRecordID>144157</EventRecordID>
<Correlation ActivityID="{0450BC50-F800-0002-8457-553A80BBCC01}" />
<Execution ProcessID="1240" ThreadID="4360" />
<Channel>Application</Channel>
<Computer>Server1.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>
Details:
AddCoreCsiFiles : GetNextFileMapContent() failed.
System Error:
The parameter is incorrect.
</Data>
</EventData>
</Event>
The System Writer is not showing up when I view vssadmin list writers.
I have already tried every tip in the following links:
http://technet.microsoft.com/en-us/library/cc734021(WS.10).aspx
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/bb760434-de80-4cb6-ae9e-bd253e4b037c/
I have also run sfc /scannow and rebooted. No luck.
I think the reason none of the tips at the above links work for me is that the System Error is NOT access denied like many others are getting, but is instead
The parameter is incorrect. I think that's the key.
Any ideas why I am getting this error and why my System Writer is nowhere to be found?

Hi,
You mentioned that “The System Writer is not showing up when I view vssadmin list writers.”
you may reboot the related services or re-register the writers, please refer to:
How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Best regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

PXI-8187 System state: Unconfigured

Similar Messages

Maybe you are looking for