Support for Windows Products
Support for Windows Products
How To Fix Error 1354
If you have Error 1354 then we strongly recommend that you download and run this (Error 1354) repair tool.
Symptoms & Summary
Error 1354 and other critical errors can occur when your Windows operating system becomes corrupted. Opening programs will be slower and response times will lag. When you have multiple applications running, you may experience crashes and freezes. There can be numerous causes of this error including excessive startup entries, registry errors, hardware/RAM decline, fragmented files, unnecessary or redundant program installations and so on.
In order to fix your error, it is recommended that you download the 'Error 1354 Repair Tool'. This is an advanced optimization tool that can repair all the problems that are slowing your computer down. You will also dramatically improve the speed of your machine when you address all the problems just mentioned.
Recommended: In order to repair your system and Error 1354, download and run Reimage. This repair tool will locate, identify, and fix thousands of Windows errors. Your computer should also run faster and smoother after using this software.
File Size 746 KB
Compatible Windows XP, Vista, 7 (32/64 bit), 8 (32/64 bit), 8.1 (32/64 bit) Windows 10 (32/64 bit)
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Unable to join machines to RODC in DMZ network Windows Server > Directory Services Question 0 Sign in to vote We rolled out a RODC to our Perimeter network. There is a firewall between our perimeter network and our Corp Network. We followed the steps per TechNet article: http://technet.microsoft.com/en-us/library/dd728035(WS.10).aspxThe problem we are having is trying to add machines via the suggested script. We are trying to add a Windows 2003 server to the network from the Perimeter. We were getting "Error: 87" until we applied hotfix: "WindowsServer2003-KB944043-v5-x86-ENU.exe". Now that the hotfix has been applied we are now getting "Error: 1354" Still unable to add the server to the Domain from the Perimeter network.Has anyone run into this issue? Wednesday, November 18, 2009 10:24 PM Reply | Quote Answers 0 Sign in to vote a new KB has been published http://support.microsoft.com/kb/977510 Marked as answer by Mervyn ZhangModerator Monday, November 30, 2009 1:53 AM Sunday, November 29, 2009 2:53 PM Reply | Quote All replies 0 Sign in to vote Hello,is Error: 1354 the only information, if not please post the complete one? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. Thursday, November 19, 2009 10:30 PM Reply | Quote 0 Sign in to vote Yeah, that's all there is. We were getting Error: 87 and now are getting Error: 1354. I guess my question at this point is "has anyone gotten this to work or is this just a situation where most admins just throw RWDCs out in the DMZ"?. I hope not. Saturday, November 21, 2009 8:41 PM Reply | Quote 0 Sign in to vote Did you already check Jorge's blog posting there? http://blogs.dirteam.com/blogs/jorge/archive/2009/01/02/domain-join-through-an-rodc-instead-of-an-rwdc.aspx. I know there's a posting that comments on 1354 just as you experienced it. Is the PDC setup in the hub site where the RWDC-2008DC is located? Can you check the firewall traces whether there's something blocked?Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog) Sunday, November 22, 2009 9:00 AM Reply | Quote 0 Sign in to vote als
Message Find Members Posts Add to Buddy List Newbie Joined: 04 Nov 2009 Location: Canada Online Status: Offline Posts: 28 QuoteReply Topic: error 1354Posted: 23 Feb 2010 at 7:57pm Hi there, I used Profwiz to migrate users profiles, and join the PCs to AD domain, It worked well in my region (using a domain controller X)... but in one of our regions (With a different domain controller Y)I had the following error (1354) -------Sart log---- Using Domain Controller: https://social.technet.microsoft.com/Forums/windowsserver/en-US/1d18b9ad-0a2a-437b-94e0-edeebf156e9f/unable-to-join-machines-to-rodc-in-dmz-network?forum=winserverDS \\WEDM06.xyz...... Binding to Active Directory... Done.Joining to domain "ad.xyz" ... Fails. Error 1354. This operation is only allowed for the Primary Domain Controller of the domain. Migration Fails. --------END LOG---- AND Since the profile was migrated with success, I tried to join the PC to AD domain manually, It worked well! How to fix this problem? Is http://forum.forensit.com/forum_posts.asp?TID=240 there a way the let profwiz using a specific domain controller? Thank you in advance Support Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Online Status: Offline Posts: 1166 QuoteReply Posted: 24 Feb 2010 at 3:28am Hi, It is very rare for this to happen, but we are aware that it does. The issue will be addressed in the next release build of the Wizard. If you have an urgent requirement for this functionality, please email support@ForensiT.com Many Thanks. Post Reply Forum Jump -- Select Forum -- Product Announcements Domain Migration Desktop Management Move Computer Forum Permissions You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum This page was generated in 0.016 seconds.
cause A sequence with the specified name already exists. Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: firstname.lastname@example.orgNo related pages.
There are many reasons why Error 1354 happen, including having malware, spyware, or programs not installing properly. You can have all kinds of system conflicts, registry errors, and Active X errors. Reimage specializes in Windows repair. It scans and diagnoses, then repairs, your damaged PC with technology that not only fixes your Windows Operating System, but also reverses the damage already done with a full database of replacement files.
A FREE Scan (approx. 5 minutes) into your PC's Windows Operating System detects problems divided into 3 categories - Hardware, Security and Stability. At the end of the scan, you can review your PC's Hardware, Security and Stability in comparison with a worldwide average. You can review a summary of the problems detected during your scan. Will Reimage fix my Error 1354 problem? There's no way to tell without running the program. The state of people's computers varies wildly, depending on the different specs and software they're running, so even if reimage could fix Error 1354 on one machine doesn't necessarily mean it will fix it on all machines. Thankfully it only takes minutes to run a scan and see what issues Reimage can detect and fix.
A Windows error is an error that happens when an unexpected condition occurs or when a desired operation has failed. When you have an error in Windows, it may be critical and cause your programs to freeze and crash or it may be seemingly harmless yet annoying.
A stop error screen or bug check screen, commonly called a blue screen of death (also known as a BSoD, bluescreen), is caused by a fatal system error and is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to "crash".
One of the biggest causes of DLL's becoming corrupt/damaged is the practice of constantly installing and uninstalling programs. This often means that DLL's will get overwritten by newer versions when a new program is installed, for example. This causes problems for those applications and programs that still need the old version to operate. Thus, the program begins to malfunction and crash.
Computer hanging or freezing occurs when either a program or the whole system ceases to respond to inputs. In the most commonly encountered scenario, a program freezes and all windows belonging to the frozen program become static. Almost always, the only way to recover from a system freeze is to reboot the machine, usually by power cycling with an on/off or reset button.
Once your computer has been infected with a virus, it's no longer the same. After removing it with your anti-virus software, you're often left with lingering side-effects. Technically, your computer might no longer be infected, but that doesn't mean it's error-free. Even simply removing a virus can actually harm your system.
Reimage repairs and replaces all critical Windows system files needed to run and restart correctly, without harming your user data. Reimage also restores compromised system settings and registry values to their default Microsoft settings. You may always return your system to its pre-repair condition.
Reimage patented technology, is the only PC Repair program of its kind that actually reverses the damage done to your operating system. The online database is comprised of over 25,000,000 updated essential components that will replace any damaged or missing file on a Windows operating system with a healthy version of the file so that your PC's performance, stability & security will be restored and even improve. The repair will deactivate then quarantine all Malware found then remove virus damage. All System Files, DLLs, and Registry Keys that have been corrupted or damaged will be replaced with new healthy files from our continuously updated online database.
Downloads in July: 361,927
Download Size: 746KB
To Fix (Error 1354) you need to follow the steps below:
Download Error 1354 Repair Tool
Click the "Scan" button
Click 'Fix All' and the repair is complete.
Windows Operating Systems:
Compatible with Windows XP, Vista, Windows 7 (32 and 64 bit), Windows 8 & 8.1 (32 and 64 bit), Windows 10 (32/64 bit).