Adobe 10 error #1460 - Timeout period expired

We have been having a problem with saving documents since the upgrade to Adobe 10. If the document is not saved fast enough,
we get the timeout period expired error #1460. Is there some way to adjust this timeperiod?

http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5b439fe-1aa9-4823-a3ac-d0be643a5073/query-using-ad-module-timed-out?forum=winserverDS
has some more information on this, though I don't know if there were any improvements to the AD Module in the last year that might change this situation.
Long story short, the AD module is good for small scale, but beyond that, you might be better off using the System.DirectoryServices classes for better performance and finer control.

Similar Messages

Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Hi Everybody,
I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard " This operation
returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
thanks

Hi,
Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
updates. Please post the error or warning report.
Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support.microsoft.com/kb/2784261
Hope this helps.
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.

"Error: 0x800705B4. This operation returned because the timeout period expired"

Hello,
I deployed security updates Mid October 201, however some clients failed to install with the error "0x800705B4 this operation returned because the timeout period expired when installing updates".
Although, i saw an article but this did not address the issue. It was advised i temporarily disable any third party antivirus software and firewall.
Unfortunately, we use SEP antivirus and any attempt to disable it would yanck the clients off the network. Windows Firewall is also disabled on these clients.
Can anyone help urgently?

Hi,
What's the status in Software Center about the updates?
Have you checked SCCM updates logs on the clients?
http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
Please also check the boundary groups associated with DPs have been configured correctly.
Best Regards,
Joyce
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.

Software deployments - timeout period expired

Is there an undocumented timeout period when deploying Application packages ? I've noticed that after about a month, deployment status on computers which haven't received a particular Application package return with "This operation returned because
the timeout period expired" We've re-scheduled installation deadlines every few subsequent days to catch as many online computers in our device collection as possible. I don't see any time-out period in the settings for the Application package
apart from the estimated installation time and max allowed run time (set at a couple of hours)
Thanks

So, then the clients are having issues getting content. You need to troubleshoot this process as it really has nothing to do with the deployment itself. And no, to my knowledge, you can't tweak this timeout. As mentioned, you really need to figure out
why the content isn't being downloaded in the first place and address that.
Jason | http://blog.configmgrftw.com

SSRS Error: The timeout period elapsed prior to completion of the operation or the server is not responding

Hi, I am using SQL Server 2008 R2 Stored Procedure as my dataset and running yearly sales report in SSRS 2008 R2. The weird thing is in SSMS the stored procedure does not take more than 10 seconds to retrieve data and the report also works
fine in BIDS, but from ReportServer if I were to pick an year from 1990 - 2014 they all work fine anything prior to 1990 either shows up fine or throws the below error.
SSRS Error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'QueryDS'. (rsErrorExecutingCommand)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.
I checked ReportServerTemDb tables and no table seems to be really large to cause a problem. This report "KeepTogether" property is TRUE.
Thanks in advance.............
Ione

Was able to fix this with the help of
msdn documentation. The query dataset was set to 5 and this was somebody else's report I was fixing and I usually have my report template set to 0 so it took me a while to get there.
Ione

ZEN StonePlus-Semaphore timeout period expired+firmware issue

Hello, im new here, i apolgize if the topic with same problem already exist. (i found similar, but from 2007.)
I have a problem with my Zen Stone Plus 2GB. The firmware is broken i think. It wont turn up, pc wont recognize it in any way.
I tried this :
http://forums.creative.com/t5/MP3-Pl...67B37F890FAA05
Hey I keep replying to myself. But this time it's good news, I've fixed the problem!
Here are the steps I performed:
. Put the player in recovery mode with these instructions (I was only able to do this once so follow the instructions carefully):
Here are the instructions:
a. Download and install the Mass Storage Drivers from the website.
b. Press and hold the Play button while connecting your player to the PC. If you have a one-piece player then remove the battery first.
c. Keep pressing Play until the New Hardware Wizard starts - this will only happen the first time you put your player into Recovery Mode.
d. Complete the New Hardware Wizard.
To check that you are in Recovery Mode open Device Manager (right-click My Computer and choose Properties, then the Hardware tab and Device Manager) and look for a Player Recovery Device entry.
When in Recovery Mode you can reload the firmware.
2. DO NOT INSTALL THE RIGHT FIRMWARE FOR ZEN STONE PLUS, instead upload the firmware for the MuVo player: http://files.creative.com/manualdn/D...W_LF__2_03.exe
3. After the firmware has been updated go into recovery mode again but this time upload the correct firmware for Zen Stone Plus: http://is.europe.creative.com/suppor...ame=Windows+XP
VOILA! The player has risen from death and can continue to be enjoyed!
And this says the same :
http://www.mycreativefansite.com/200...ue-on-zen.html
NOW what I have done :
. Installed drivers for creative players from their site [done]
2. Inserted the player to the PC [done]
3. Installed the "MP3 Player Recovery Device Drivers" (mentioned in above link) [done]
4. My player is now in "recovery mode" it was recognized as "Player recovery device" [done]
5. I tried to install the firmware for MUVO players (again see the link above) but it came up with the "Operating system reported error: The semaphore timeout period has expired" [fail]
6. I tried to install the latest Zen Stone Plus firmware from creative site but again - "Operating system reported error: The semaphore timeout period has expired" [fail]
http://img97.imageshack.us/img97/430/aerhbae.th.jpg - picture here !
I tried MUVO V200.
That error should came up within the installation of ZEN firmware, not the MUVO firmware. But my problem is : The MUVO firmware does the same error as the ZEN firmware.
I also tried different firmware, for MUVO T200. It wont even turn on the update - "Your player is not connected, please connect your player" it says.
Reseted milion times and the battery is charged by the way.
ps : sorry for my english
Thanks for your help !

Anyone?

Error #1502: timeout period of 15 seconds. not a long calculation

Hi guys,
I got a strange problem of Error #1502. I don't do a long calculation. i tried to debug step by step, but can not find any possible cause yet.
I took three stack traces:
y::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel2,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel2.PanelSkin880. _PanelSkin_Group1.contents.contentGroup.VGroup888.DisabledGroup890,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel2.PanelSkin880. _PanelSkin_Group1.contents.contentGroup.VGroup888.DisabledGroup890._MenusView_MenuCategory Component1,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel3,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel3.PanelSkin980. _PanelSkin_Group1.contents.contentGroup.VGroup988.DisabledGroup990,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel3.PanelSkin980. _PanelSkin_Group1.contents.contentGroup.VGroup988.DisabledGroup990._MenusView_RegularMenuI temComponent1,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView206.TitleWindowSkin207._TitleWindowSkin_Group1.contents.contentGroup.HGroup 216.viewport.viewStack.NavigatorContent235.SkinnableContainerSkin236.contentGroup.VPanel69 5.PanelSkin696._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt707.SkinnableContainerSkin708.contentGroup.MenusView719._MenusView_VPanel3.PanelSkin980. _PanelSkin_Group1.contents.contentGroup.VGroup988.DisabledGroup990._MenusView_RegularMenuI temComponent1.FormItem1033._RegularMenuItemComponent_HGroup2.HGroup1036.menuItemProperties ,
name: null } )
Error: Error #1502: A script has executed for longer than the default
timeout period of 15 seconds.
         at org.swizframework.core::BeanFactory/isPotentialInjectionTarget()[/
projects/swiz-framework/src/org/swizframework/core/BeanFactory.as:434]
         at org.swizframework.core::BeanFactory/setUpEventHandler()[/projects/
swiz-framework/src/org/swizframework/core/BeanFactory.as:456]
         at org.swizframework.core::BeanFactory/setUpEventHandlerSysMgr()[/
projects/swiz-framework/src/org/swizframework/core/BeanFactory.as:486]
         at flash.display::DisplayObjectContainer/addChildAt()
         at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::
$addChildAt()
         at mx.core::UIComponent/addChildAt()
         at flashx.textLayout.container::ContainerController/addTextLine()
         at flashx.textLayout.container::ContainerController/http://
ns.adobe.com/textLayout/internal/2008::updateCompositionShapes()
         at flashx.textLayout.compose::StandardFlowComposer/
updateCompositionShapes()
         at flashx.textLayout.compose::StandardFlowComposer/
updateToController()
         at flashx.textLayout.compose::StandardFlowComposer/
updateAllControllers()
         at flashx.textLayout.container::TextContainerManager/
updateContainer()
         at spark.components::RichEditableText/updateDisplayList()
         at mx.core::UIComponent/validateDisplayList()
         at mx.managers::LayoutManager/validateClient()
         at mx.core::UIComponent/validateNow()
         at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/
internal::validateBaselinePosition()
         at spark.components.supportClasses::SkinnableComponent/
getBaselinePositionForPart()
         at spark.components.supportClasses::SkinnableTextBase/get
baselinePosition()
         at mx.containers::FormItem/updateDisplayList()
         at mx.core::UIComponent/validateDisplayList()
         at mx.core::Container/validateDisplayList()
         at mx.managers::LayoutManager/validateDisplayList()
         at mx.managers::LayoutManager/doPhasedInstantiation()
         at mx.managers::LayoutManager/doPhasedInstantiationCallback()
        BeanFactory::setUpBean( Bean{ source:
RestaurantView203.TitleWindowSkin204._TitleWindowSkin_Group1.contents.conte
ntGroup.HGroup213.viewport.viewStack.NavigatorContent232.SkinnableContainerSkin233.content Group.VPanel692.PanelSkin693._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack. NavigatorContent704.SkinnableContainerSkin705.contentGroup.MenusView716._MenusView_VPanel3 ,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView203.TitleWindowSkin204._TitleWindowSkin_Group1.contents.contentGroup.HGroup 213.viewport.viewStack.NavigatorContent232.SkinnableContainerSkin233.contentGroup.VPanel69 2.PanelSkin693._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt704.SkinnableContainerSkin705.contentGroup.MenusView716._MenusView_VPanel3.PanelSkin977. _PanelSkin_Group1.contents.contentGroup.VGroup985.DisabledGroup987,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView203.TitleWindowSkin204._TitleWindowSkin_Group1.contents.contentGroup.HGroup 213.viewport.viewStack.NavigatorContent232.SkinnableContainerSkin233.contentGroup.VPanel69 2.PanelSkin693._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt704.SkinnableContainerSkin705.contentGroup.MenusView716._MenusView_VPanel3.PanelSkin977. _PanelSkin_Group1.contents.contentGroup.VGroup985.DisabledGroup987._MenusView_RegularMenuI temComponent1,
name: null } )
BeanFactory::setUpBean( Bean{ source:
RestaurantView203.TitleWindowSkin204._TitleWindowSkin_Group1.contents.contentGroup.HGroup 213.viewport.viewStack.NavigatorContent232.SkinnableContainerSkin233.contentGroup.VPanel69 2.PanelSkin693._PanelSkin_Group1.contents.contentGroup.menuDetailsViewStack.NavigatorConte nt704.SkinnableContainerSkin705.contentGroup.MenusView716._MenusView_VPanel3.PanelSkin977. _PanelSkin_Group1.contents.contentGroup.VGroup985.DisabledGroup987._MenusView_RegularMenuI temComponent1.FormItem1030._RegularMenuItemComponent_HGroup2.HGroup1033.menuItemProperties ,
name: null } )
Error: Error #1502: A script has executed for longer than the default
timeout period of 15 seconds.
         at flashx.textLayout.compose::BaseCompose/fitLineToParcel()
         at flashx.textLayout.compose::ComposeState/composeNextLine()
         at flashx.textLayout.compose::BaseCompose/
composeParagraphElementIntoLines()
         at flashx.textLayout.compose::ComposeState/composeParagraphElement()
         at flashx.textLayout.compose::BaseCompose/composeBlockElement()
         at flashx.textLayout.compose::BaseCompose/composeInternal()
         at flashx.textLayout.compose::ComposeState/composeInternal()
         at flashx.textLayout.compose::BaseCompose/composeTextFlow()
         at flashx.textLayout.compose::ComposeState/composeTextFlow()
         at flashx.textLayout.compose::StandardFlowComposer/http://
ns.adobe.com/textLayout/internal/2008::callTheComposer()
         at flashx.textLayout.compose::StandardFlowComposer/internalCompose()
         at flashx.textLayout.compose::StandardFlowComposer/compose()
         at flashx.textLayout.container::TextContainerManager/compose()
         at flashx.textLayout.container::TextContainerManager/
updateContainer()
         at spark.components::RichEditableText/updateDisplayList()
         at mx.core::UIComponent/validateDisplayList()
         at mx.managers::LayoutManager/validateClient()
         at mx.core::UIComponent/validateNow()
         at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/
internal::validateBaselinePosition()
         at spark.components.supportClasses::SkinnableComponent/
getBaselinePositionForPart()
         at spark.components.supportClasses::SkinnableTextBase/get
baselinePosition()
         at mx.containers::FormItem/updateDisplayList()
         at mx.core::UIComponent/validateDisplayList()
         at mx.core::Container/validateDisplayList()
         at mx.managers::LayoutManager/validateDisplayList()
         at mx.managers::LayoutManager/doPhasedInstantiation()
         at mx.managers::LayoutManager/doPhasedInstantiationCallback()
Error: Error #1502: A script has executed for longer than the default
timeout period of 15 seconds.
         at mx.managers.layoutClasses::PriorityQueue/removeSmallestChild()
         at mx.managers::LayoutManager/validateClient()
         at mx.core::UIComponent/validateNow()
         at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/
internal::validateBaselinePosition()
         at spark.components.supportClasses::SkinnableComponent/
getBaselinePositionForPart()
         at spark.components.supportClasses::SkinnableTextBase/get
baselinePosition()
         at mx.containers::FormItem/updateDisplayList()
         at mx.core::UIComponent/validateDisplayList()
         at mx.core::Container/validateDisplayList()
         at mx.managers::LayoutManager/validateDisplayList()
         at mx.managers::LayoutManager/doPhasedInstantiation()
         at mx.managers::LayoutManager/doPhasedInstantiationCallback()
         BeanFactory::setUpBean( Bean{ source:
RestaurantView205.TitleWindowSkin206._TitleWindowSkin_Group1.contents.conte
Any idea of how to solve the problem or how to find out the cause will be highly appreciated. My Flash builder profiler is not working today, that might help.
Many thanks,
Cheng Wei

Thanks for your prompt reply.
No, i am not. It is hard to create a simple demo here, but i can recreate it with my application. It is being very strange, it only happens to one MenuCategory(a concept from our application). I don't think screenshot will help here, but i will do some here. Is it possible to request a remote assistance(e.g. via TeamViewer, coming from java background, i sometimes find flex is hard to find out the cause of a problem)?
1.good category
The only bad category found so far, stuck when clicking on second category - Kids choice. Kids choice only has 4 menu items.
Could be an application problem, but from the stack trace, i don't have an idea, where the problem is from yet.
Your help is highly appreciated.
Cheers,
Cheng Wei

Sqliosim semaphore timeout period expired...

I want to know about the semaphore timeout error caused while read/write io of sqliosim.
I have mapped lun to windows through FC connection and started io using sqliosim, i am getting semaphore timeout error.
I have found many microsoft links which talks about this error but not explained exactly the reason of this error
May i know the reasons of this error?
Sample testcase to get this error?
Is this related to disk device registry timeout?
how i can regenerate this error using sqliosim?

Hi vikram jadhav1,
The error "0x80070079: The semaphore timeout period has expired" is returned from the Windows API "winerror.h". It occurs when a synchronization object of type semaphore times out.
A semaphore object is a synchronization object that maintains a count between zero and a specified maximum value. The count is decremented each time a thread completes a wait for the semaphore object and incremented each time a thread releases the semaphore.
When the count reaches zero, no more threads can successfully wait for the semaphore object state to become signaled. The state of a semaphore is set to signaled when its count is greater than zero, and nonsignaled when its count is zero. It acts as a gate
that limits the number of threads sharing the resource to a specified maximum number.
So, in case the semaphore object is nonsignaled(its count is zero) and there are threads waiting for the object, the error occurs when the waiting reaches the timeout.
The error can occur in many scenarios. E.g. TCP/IP, Disk Driver, VSS etc.
It this case, it seems to be a driver issue. However, it is really hard to say what it is the exact cause without the detailed error message.
To understand the exact root cause, I would suggest you to open premier case to Microsoft. The premier team can help to debug the sqliosim to get the cause.
Short answers to your other questions:
--Sample testcase to get this error?
No
--Is this related to disk device registry timeout?
It may be. Debug is required to confirm it.
--how i can regenerate this error using sqliosim?
Without get the root cause, it is hard to reproduce it.
Thanks,
Jinchun Chen

Timeout period expired

Hi Experts,
Sometimes i'm getting below error msg while executing powershell commands..
is there any way to avoid this error msg by extending the timeout?
Regards, Nidhin.CK

http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5b439fe-1aa9-4823-a3ac-d0be643a5073/query-using-ad-module-timed-out?forum=winserverDS
has some more information on this, though I don't know if there were any improvements to the AD Module in the last year that might change this situation.
Long story short, the AD module is good for small scale, but beyond that, you might be better off using the System.DirectoryServices classes for better performance and finer control.

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

System error 1460 has occurred (0x000005b4). when trying to create two-node cluster in R2

I'm trying to create a brand new two node Windows 2008 R2 Enterprise 64bit cluster. When I try with the GUI I get the following:
An error occurred while creating the cluster.
An error occurred creating cluster 'printcluster'.
This operation returned because the timeout period expired
When I try via command prompt using the following command:
cluster /cluster:PrintServices /create /nodes:"node1 node2" /ipaddr:10.9.11.194/255.255.255.0
I get the following:
4% Initializing Cluster PrintServices.
9% Validating cluster state on node <node1>.
13% Searching the domain for computer object PrintServices
18% Creating a new computer object for PrintServices in the domain
22% Configuring computer object PrintServices as cluster name object
27% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node1>.
31% Validating installation of the Cluster Disk Driver on node <node1>.
36% Configuring Cluster Service on node <node1>.
40% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node2>.
45% Validating installation of the Cluster Disk Driver on node <node2>.
50% Configuring Cluster Service on node <node2>.
54% Starting Cluster Service on node <node1>.
54% Starting Cluster Service on node <node2>.
59% Forming cluster PrintServices.This phase has failed for Cluster object 'PrintServices' with an error status of 1460 (0x000005B4).
Cleaning up <node1>.
Cleaning up <node2>.
Cleaning up PrintServices.
When I run a Cluster validation, I get 100% Green, no errors.
My disks are SAN Attached.
I have other Windows 2008 non-R2 clusters that never had this problem... Any ideas?
-PaulPaul S

Hi Paul,
I suggest trying the following steps to troubleshoot this issue:
1. Open Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
3. Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter."
4. Under the subkey that you found in step 3, add the following string value registry entry:
Name: DatalinkAddress
Value data: 02-AA-BB-CC-DD-01
5. Restart the computer.
6. Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters.
7. On each computer that you want to make a cluster node, use the Server Manager console to remove the Failover Clustering feature.
8. Restart each computer from which you have removed the Failover Clustering feature.
9. Add the Failover Clustering feature on all these computers again.
10. Run cluster validation against these computers.
11. Try creating a cluster.
If the issue persists, please let me know what errors are logged in Event Logs.
Tim Quan - MSFT

Evaluation period expired

Hi all,
I am using Xilinx 10.1 webpack... while i am compiling the code, the following error occur. Please any one guide me to
clear the error..
ERROR:Par:332 - The evaluation period for this evaluation software has expired. As stated in the guidelines of the
Evaluation Agreement, which was shipped to you along with the Evaluation CDs, this software will no longer operate.
We are eager to assist you as you conclude your evaluation of the Xilinx solution. Your local Field Applications
Engineer or salesperson is available to answer any questions or to assist you in the purchase of an annual software
license. You may also contact Xilinx directly at [email protected]
Thank you for evaluating the Xilinx solution. We appreciate your interest in Xilinx and we look forward to earning
your confidence and your business.
Process "Place & Route" failed

Hi mwilliams2684,
According to your description, you used SQL Server 2012 volume license edition on your VMware Vcenter server. Then error message “Evaluation Period Expired” was thrown out in the logs.
Firstly, as other post, we need to verify if you have installed SQL Server Standard 2012. There are other ways to review the version of SQL Server, please refer to this article: How to tell what SQL Server version you are running (http://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/).
Besides, error “Evaluation Period Expired” usually occurs when we are running an evaluation instance of SQL Server and the evaluation time period has expired. For detail information, please refer to this article: "Evaluation period has expired"
error message when working with SQL server (http://support.microsoft.com/kb/971268).
Finally, for more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use
the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Best regards,
Qiuyun Yu

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
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.

VIP Swap and 'The semaphore timeout period has expired' errors

We use the VIP swap technique of rolling out new versions of our apps. These apps use an Azure SQL Database. Starting sometime early this year we started seeing SQL Database errors during the VIP swap. The problem is very consistent, if we have database
activity during the VIP Swap it is very likely to generate one or more of these errors. As you can see below in our custom formatted version of the error the actual SQL Error number is 121 and the text is 'The semaphore timeout period has expired':
SQLError Number:121, Message:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
We do utilize the Enterprise library for transient error handling and I have seen these errors from time to time and random points, but the fact that this is very consistent with a VIP swap bothers me. Since both deployments exist before and after the VIP swap
why would there be any interruption in SQL Database connectivity? Our apps consist of a Web App, a few Web Services, and a few Worker Roles. I have seen this error from all of them at different times during VIP swaps.
Any ideas?

Hi Curious,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Error 0x80070079: The semaphore timeout period has expired

Whenever I try to copy large files over a wireless network (Laptop > Desktop) I get the following error:-
Error 0x80070079: The semaphore timeout period has expired
I've done a search on Google and have found that a number of other users are having the same problem, but no-one seems to have a fix for it.
Can anyone help?
(I'm running Vista Ultimate on both my Laptop & Desktop)

Lionel Chen - MSFT wrote:
Hello Ady,
Thanks for your post!
This issue may be a little complex and require some steps to troubleshoot:
1.    Update the driver of wireless network adapters in both of your computers.
2.    Temporarily disable all the firewalls and anti-virus applications, then check the issue again.
3.    To exclude the factors from other services and applications, do a clean boot to check the issue and perform Step 4.
(KB929135) How to troubleshoot a problem by performing a clean boot in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;929135
4.    With clean boot, try to apply the hotfixes contained in the following KB articles:
(KB932045) Error message when you use a network connection to copy a large file from one Windows Vista-based computer to another Windows Vista-based computer: "The connection has been lost"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932045
(KB932063) Several problems occur on a Windows Vista-based computer when you work in a wireless network environment
http://support.microsoft.com/default.aspx?scid=kb;EN-US;932063
If problem still persists after steps above, this issue is very possibly due to network devices or configurations, please let me know:
1.    Whether this problem occurs in wired network?
2.    If strengthening the network signals, the problem can be changed?
3.    What size of files will lead to this error.
4.    Does this error terminate the copy process?
5.    Models of the wireless network adapter and wireless router.
More details about his issue are preferred. Thanks!
Have a nice weekend!
Regards,
Lionel Chen
Microsoft Online Community Support
Well this did'nt work for me.
Any other solution?
Using XP Prof. Service Pack 3 beta.

Adobe 10 error #1460 - Timeout period expired

Similar Messages

Maybe you are looking for