NetStream.Publish.Failed

I'm trying to connect 2 swfs over Stratus and the second client is getting NetStream.Publish.Failed when I try to publish a stream. They both have connected to Stratus via the NetConnection and one can publish a stream but the second can not. I've made sue that each swf is using a different name to publish. I can't find this error listed anywhere in the documentation it only listed NetStream.Publish.BadName. I'm using the AIR 2 RC1 beta sdk from adobe labs set to publish for 10.1.
Are there any other reasons why i would be getting NetStream.Publish.Failed?

I found out why it was failing. I was entering the peerID I wanted to allow connection from instead of allowing any direction connection.
so I had:
stream = new NetStream(connection, farID);
stream.publish( channel );
where is should be:
stream = new NetStream(connection, NetStream.DIRECT_CONNECTIONS);
stream.publish( channel );
then the other client needs to use both my farID and name of my stream in order to connect

Similar Messages

  • NetStream.publish for P2P NetGroup fails in the FMS 4.0 AS

    Hi,
    I recently tried to modify the system-provided codes in the "multicast" folder, and could not get it work. I pinned down the issue to be the function call NetStream.publish("p2p_pindao1", "live") always failed for me. The proof the function call failed including:
    1. The returned value is false.
    2. I got no further events beyond NetStream.Connect.Success, i.e. I did not get the expected NetStream.Publish.Start
    The following are the testing codes
    application.onAppStart = function()
    var nc = new NetConnection();
    nc.onStatus = testNetStatus;
    nc.connect("rtmfp://localhost/TVLive");
    trace("to connect");
    function testNetStatus(info)
    trace("TestNetStatus:" + info.code);
    var gs = new GroupSpecifier("net.lysk.pindao1");
    gs.serverChannelEnabled = true;
    gs.postingEnabled = true;
    gs.peerToPeerDisabled = false;
    // Multicast address over which to exchange peer discovery.
    //var p2pm = "224.0.0.255:30000"; // BUGBUG
    // Must be enabled for LAN peer discovery to work
    //gs.ipMulticastMemberUpdatesEnabled = true; 
    var ng = new NetGroup(this, gs);
    ng.objNc = this;
    ng.objGs = gs;
    ng.onStatus = testNetGroupStatus;
    function testNetGroupStatus(info)
    trace("testNetGroupStatus:" + info.code);
    var ns = new NetStream(this.objNc, this.objGs);
    ns.onStatus = testNetStreamStatus;
    function testNetStreamStatus(info)
    trace("testNetStreamStatus:" + info.code);
    if (info.code == "NetStream.Connect.Success")
      if(!this.attach(Stream.get("mp4:sample1_1000kbps.f4v")))
       trace("can not attach");
      if (!this.publish("testpublish", "live"))
       trace ("can not publish");
    tracing outputs are the following:
    to connect
    TestNetStatus:NetConnection.Connect.Success
    testNetGroupStatus:NetGroup.Connect.Success
    testNetStreamStatus:NetStream.Connect.Success
    can not publish
    Your help in solving the problem will be highly appreciated.
    Thanks.

    em, it appears I was wrong in believing peerToPeerDisabled=true sufficed for P2P publishing, while multicastEnabled was for IP multicast. I will try out the answer. Thanks for the help.

  • AppV5 Office 2013 (Visio) couldn't get published (failed configuration in folder ProgramData\App-V 0x7D401F30-0x5)

    Environment:
    Server: AppV 5 SP1 Pub and Mgmt server (no Hotfixes applied)
    Client: Windows 7 SP1 x64 with AppV 5.0 SP2 client (tried RTM and with HF5)
    Created a Visio 2013 package with ODT (latest version). Only Visio, no other products added. Used the PACKAGEGUID to specify a custom PackageGUID.
    Configuration.xml;
    <Configuration>
    <Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
    <Product ID="VisioStdVolume">
    <Language ID="en-us" />
    <Language ID="nl-nl" />
    <Language ID="fr-fr" />
    </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="VisioStd2013Setup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    <Property Name="PACKAGEGUID" Value="0123e69c-b152-4c70-b178-41be0d2b7d1b" />
    </Configuration>
    Adding and Publishing locally with Powershell works like expected. But using the App-V 5.0 Mgmt/Publishing server it fails on all clients.
    Package is published to computers.
    Domain Computers have READ permission on the AppV Content share.
    Previously Office 2013 packages could be published without any errors.
    AppV logs:
    Event ID: 19104:
    Part or all packages publish failed.
    published: 0
    failed: 1
    Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
    Event ID: 1008
    Package {0123e69c-b152-4c70-b178-41be0d2b7d1b} version {5197e402-1206-4940-bd96-a0597e7d4b1f} failed configuration in folder 'C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F' with error 0x7D401F30-0x5.
    Event ID: 4001
    The App-V client failed to create a process for machine script event AddPackage with command line: '"C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=0123e69c-b152-4c70-b178-41be0d2b7d1b PackageRoot="C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=FN8TT-7WMH6-2D4X9-M337T-2342K,YC7DK-G2NP3-2QQC3-J6H88-GVGXT,C2FG9-N6J68-H8BTJ-BW3QX-RM3B3 PRIDName=VisioStdVolume'. Windows error: Access is denied.. The path must be a Windows application (.exe file).
    Analytic and Debugs logs aren’t very helpful (Client-Publishing):
    No package published.
    Published: false
    Failed: 0
    So, Access denied (0x5) on Integrator.exe in ProgramData? As we have AppLocker in place, checked the AppLocker logs. But no trace in there.
    Other AppV5 applications does work
    Tested on two different App-V 5 Pub Servers (5.0 SP1 and SP1 with HF4), same behaviour.
    Tested on three Win7 SP1 x64 clients, same behaviour.
    EnablePackageScripts (client config) is enabled on all clients.
    Issue was
    reported before on the forums, but Domain Users and Domain Computers have already READ permissions to the AppV Content Share (NTFS permissions) where the .appv file is stored.
    Added (as a test) Domain Computers and Everyone Full Control to c:\ProgramData\App-V, doesn’t solve it.
    Cannot use ProcMon, because the Publish event occurs before user login.
    I’m out of ideas. Someone that could assist me please?

    The above fix was a lucky shot.
    This solved it (hopefully) for good;
    http://www.the-d-spot.org/wordpress/2014/11/05/appv5-office-2013-package-cannot-be-published-access-is-denied-on-integrator-exe/

  • Publish failed (when using Calendar instead of GregorianCalendar..)

    I have a web service written in Workshop 9.2.2 running on a WLS9.2 Server.
    One attribute in my web service is of type java.util.Calendar. Now when I try to publish that I get a "Publish Failed" almost immeditately.
    HOWEVER, when I change the type of the attribute to java.util.GregorianCalender, the publish works fine...
    This seems like a bug to me, as the WLS doc says that I should use Calendar as a data type for dates in web services and it clearly supports it.
    Can I upgrade to the latest version of Workshop and continue using WLS9.2?
    Here's the log file:
    !ENTRY com.bea.wlw.server.core 1 2000 2008-03-19 15:35:59.994
    !MESSAGE Releasing deployment manager @0
    !ENTRY com.bea.wlw.server.core 1 2000 2008-03-19 15:35:59.994
    !MESSAGE Publishing finished.
    !ENTRY org.eclipse.wst.server.core 4 0 2008-03-19 15:36:00.10
    !MESSAGE Publishing failed
    !SUBENTRY 1 com.bea.wlw.server.core 4 0 2008-03-19 15:36:00.10
    !MESSAGE Error with publish task 'WebServicesProjectBuildTask'.
    !SUBENTRY 2 com.bea.wlw.webservices.core 4 4 2008-03-19 15:36:00.10
    !MESSAGE Error while compiling web services in WL92WS.
    !STACK 0
    com.bea.wlw.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\bea\user_projects\w4WP_workspaces\WSTest\WL92WS\src\webservices\contentreceiver\ContentReceiverService.java
         at com.bea.wlw.webservices.core.compiler.WebServiceCompiler$3.invoke(WebServiceCompiler.java:249)
         at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.accessCompiler(WebServiceCompiler.java:291)
         at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile0(WebServiceCompiler.java:244)
         at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile(WebServiceCompiler.java:202)
         at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.build0(WebServiceProjectCompiler.java:157)
         at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.access$0(WebServiceProjectCompiler.java:119)
         at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler$1.run(WebServiceProjectCompiler.java:92)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1721)
         at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.build(WebServiceProjectCompiler.java:108)
         at com.bea.wlw.webservices.core.publish.WebServiceProjectPublishTask$WebServicesBuildOperation.processWebServices(WebServiceProjectPublishTask.java:119)
         at com.bea.wlw.webservices.core.publish.WebServiceProjectPublishTask$WebServicePublishOperation.processWebModule(WebServiceProjectPublishTask.java:53)
         at com.bea.wlw.server.core.model.WeblogicWebPublishOperation.processRootChildModule(WeblogicWebPublishOperation.java:118)
         at com.bea.wlw.server.core.model.WeblogicWebPublishOperation.processRootModule(WeblogicWebPublishOperation.java:84)
         at com.bea.wlw.server.core.model.WeblogicPublishOperation.execute(WeblogicPublishOperation.java:72)
         at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.performTasks(WeblogicServerBehaviour.java:786)
         at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:434)
         at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:332)
         at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803)
         at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791)
         at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
    Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\bea\user_projects\w4WP_workspaces\WSTest\WL92WS\src\webservices\contentreceiver\ContentReceiverService.java
         at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:471)
         at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:439)
         at com.bea.wlw.webservices.core.compiler.WebServiceCompiler$3.invoke(WebServiceCompiler.java:247)
         ... 20 more
    Caused by: weblogic.wsee.tools.WsBuildException: java.lang.IllegalArgumentException: 'java.util.Hashtable<java.util.Locale,int[]>' does not name an array
         at weblogic.wsee.tools.jws.WebServiceInfo.createBindings(WebServiceInfo.java:219)
         at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.process(WsdlBuilder.java:41)
         at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:36)
         at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:467)
         ... 22 more
    Caused by: java.lang.IllegalArgumentException: 'java.util.Hashtable<java.util.Locale,int[]>' does not name an array
         at com.bea.util.jam.internal.elements.ArrayClassImpl.normalizeArrayName(ArrayClassImpl.java:100)
         at com.bea.util.jam.internal.JamClassLoaderImpl.loadClass(JamClassLoaderImpl.java:80)
         at com.bea.util.jam.internal.classrefs.QualifiedJClassRef.getRefClass(QualifiedJClassRef.java:80)
         at com.bea.util.jam.internal.elements.FieldImpl.getType(FieldImpl.java:89)
         at com.bea.staxb.buildtime.Java2Schema.isJaxRpcEnumType(Java2Schema.java:1646)
         at com.bea.staxb.buildtime.Java2Schema.checkPropertyConstructors(Java2Schema.java:1829)
         at com.bea.staxb.buildtime.Java2Schema.processProperty(Java2Schema.java:1753)
         at com.bea.staxb.buildtime.Java2Schema.bindProperties(Java2Schema.java:1368)
         at com.bea.staxb.buildtime.Java2Schema.createBindingTypeFor(Java2Schema.java:855)
         at com.bea.staxb.buildtime.Java2Schema.findOrCreateBindingTypeFor(Java2Schema.java:676)
         at com.bea.staxb.buildtime.Java2Schema.createBindingTypeFor(Java2Schema.java:804)
         at com.bea.staxb.buildtime.Java2Schema.findOrCreateBindingTypeFor(Java2Schema.java:676)
         at com.bea.staxb.buildtime.Java2Schema.internalBind(Java2Schema.java:440)
         at com.bea.staxb.buildtime.BindingCompiler.bind(BindingCompiler.java:125)
         at com.bea.staxb.buildtime.BindingCompiler.bindAsExplodedTylar(BindingCompiler.java:161)
         at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1311)
         at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:214)
         at weblogic.wsee.tools.jws.WebServiceInfo.createBindings(WebServiceInfo.java:215)
         ... 25 more
    !SUBENTRY 1 com.bea.wlw.server.core 4 4000 2008-03-19 15:36:00.72
    !MESSAGE Error(s) occurred during publish assembly. No modules will be published.

    Hi
    This looks like a known issue. I see that its fixed in Workshop 10.0 onwards.
    If you want a fix for 9.2 version please open up a BEA support case at http://support.bea.com . Please refer to the Cr's CR340337, CR360247 when opening the case.
    Can I upgrade to the latest version of Workshop and continue using WLS9.2?Yes, you can. With the latest version of workshop you can develop applications against WLS9.2.x and WLS10.x. So you would be able to use the same app on 9.2 on the latest workshop version.
    Vimala-

  • Preview/Publish Fail & Freeze in Captivate 5

    I'm experiencing freezing & "publish failed" messages when I attempt to preview or publish my project.  My project contains 1 slide with a text caption and 40 slides recorded as a demo with no audio.  I've attempted:
    clearing the cache
    reducing the project size
    copying recorded slides to a blank presentation
    installing the latest Captivate 5 update
    I have many other similar projects without this problem. Nothing seems to be working!

    I had a similar problem when I tried to publish a project in Captivate 5 that I had first created in Captivate 3.  This problem did not happen with every  3 --> 5 conversion, only in some projects.  Very mysterious.
    For me, I noticed that it ALWAYS froze during each Publish attempt at EXACLTY the same spot around 41%, so that caused me to become suspicious:  What was around 41% of the way through my slideshow that was unique/different/unusual?
    Finally I realized that there was a slide part way through the project in which I had used a quiz feature in Captivate 3 that was not available in Captivate 5,  So, when I deleted that slide and re-did it in Captivate 5, the publish worked fine.
    Just thought I would throw this in for consideration in case:
    your project was actually created in Captivate 3 first and now you are publishing in 5.
    if your project freezes at exactly the same spot during each publish,  you can investigate slides around that area to determine if there is anything unique/different/unusual

  • Using variable name for Netstream Publish() (actionscript)

    Relatively new to Actionscript.  In the netstream publish() or play() methods, can I pass variable names to the methods instead of hard-coding the stream name?
    Example:
    private function publishLiveStream():void
                ns = new NetStream(nc);
                ns.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
                ns.client = this;
              // blah blah other stuff...
               ns.publish("thefilename", "record");
    I want to replace "thefilename" with a value passed from an input box or use dynamic naming (i.e. current date & time).

    you can use in procedure using sunopisis technology
    OdiExportMaster "-TODIR=/temp/" "-ZIPFILE_NAME=export.zip" "-XML_CHARSET=ISO-8859-1" "-JAVA_CHARSET=ISO8859_1" "-EXPORT_VERSIONS=YES"
    or you can use (unix System)
    OdiExportMaster "-TODIR=/#v_FileName" "-ZIPFILE_NAME=export.zip" "-XML_CHARSET=ISO-8859-1" "-JAVA_CHARSET=ISO8859_1" "-EXPORT_VERSIONS=YES"
    Hope it will work
    Thanks

  • Desktop RTMP video works fine - but Android gives me NetStream.Seek.Failed

    I have an app built using Adobe AIR. The app uses StageVideo and plays a live RTMP H264 encoded stream using NetStream.play. The app works as expected in ADL, and when installed as an app on the desktop.
    But if use the exact same code and install the app on the Android, I get the NetStatusEvent "NetStream.Seek.Failed". So because of this event the I am unable to play the video stream on the Android.
    So my question: If you are building an app for the Android, can you not resuse the exact same NetStream code that you used on the desktop? Is there a bug on the Android runtime that is preventing RTMP from seeking correctly?
    FYI: The netstream.play startvalue is -2 (so it will look for recorded stream first, then a live stream. In my case it is a live stream)
    I am using Adobe AIR 3.7.0.2090, and Samsung Galaxy Tab 3, Android 4.2.2
    The same problem or error occurs when using the AIR 3.8.0.930 SDK

    This is longer an issue. I am now using Adobe AIR SDK 3.8.0.1040, and have made some recent updates to the code. I am not sure what fixed the issue, but I can say that yes, the Android is working as expected and I am reusing the exact same code from the desktop app for the Android.

  • Problem with connection ( NetStream.Publish.BadName)

    Fri Sep 11 2009 08:52:10 : Session Started
    Fri Sep 11 2009 08:52:11 : Audio Encoding Started
    Fri Sep 11 2009 08:52:11 : Video Encoding Started
    Fri Sep 11 2009 09:13:59 : Primary - Network Status: NetConnection.Connect.Closed status
    Fri Sep 11 2009 09:14:04 : Primary - Disconnected
    Fri Sep 11 2009 09:14:04 : Primary - Re-establishing connection, attempt 1
    Fri Sep 11 2009 09:14:05 : Primary - Reconnected to FMS/3,0,1,123
    Fri Sep 11 2009 09:14:05 : Primary - Network Command: onBWDone
    Fri Sep 11 2009 09:14:05 : Primary - Stream[onetv] Status: Success
    Fri Sep 11 2009 09:14:05 : Primary - Network Command: onFCPublish
    Fri Sep 11 2009 09:14:07 : Primary - Stream[onetv] Status: NetStream.Publish.Start
    Fri Sep 11 2009 09:14:58 : Primary - Network Status: NetConnection.Connect.Closed status
    Fri Sep 11 2009 09:15:04 : Primary - Disconnected
    Fri Sep 11 2009 09:15:05 : Primary - Re-establishing connection, attempt 1
    Fri Sep 11 2009 09:15:05 : Primary - Reconnected to FMS/3,0,1,123
    Fri Sep 11 2009 09:15:05 : Primary - Stream[onetv] Status: Success
    Fri Sep 11 2009 09:15:05 : Primary - Network Command: onFCPublish
    Fri Sep 11 2009 09:15:07 : Primary - Stream[onetv] Status: NetStream.Publish.BadName
    Fri Sep 11 2009 09:27:20 : Audio Encoding Stopped
    Fri Sep 11 2009 09:27:20 : Video Encoding Stopped
    Fri Sep 11 2009 09:27:20 : Session Stopped
    Fri Sep 11 2009 09:27:23 : Primary - Network Status: NetConnection.Connect.Closed status
    Fri Sep 11 2009 09:27:23 : Primary - Disconnected
    Fri Sep 11 2009 09:27:24 : Primary - Connected to FMS/3,0,1,123
    Fri Sep 11 2009 09:27:24 : Primary - Network Command: onBWDone
    Fri Sep 11 2009 09:27:28 : Primary - Network Command: onFCPublish
    Fri Sep 11 2009 09:27:28 : Primary - Stream[onetv] Status: Success
    Fri Sep 11 2009 09:27:28 : Primary - Stream[onetv] Status: NetStream.Publish.Start
    Fri Sep 11 2009 09:27:28 : Session Started
    Fri Sep 11 2009 09:27:29 : Video Encoding Started
    Fri Sep 11 2009 09:27:29 : Audio Encoding Started
    Fri Sep 11 2009 12:23:03 : Primary - Network Status: NetConnection.Connect.Closed status
    Fri Sep 11 2009 12:23:09 : Primary - Disconnected
    Fri Sep 11 2009 12:23:09 : Primary - Re-establishing connection, attempt 1
    Fri Sep 11 2009 12:23:09 : Primary - Reconnected to FMS/3,0,1,123
    Fri Sep 11 2009 12:23:09 : Primary - Stream[onetv] Status: Success
    Fri Sep 11 2009 12:23:09 : Primary - Network Command: onFCPublish
    Fri Sep 11 2009 12:23:11 : Primary - Stream[onetv] Status: NetStream.Publish.BadName
    Fri Sep 11 2009 12:26:26 : Audio Encoding Stopped
    Fri Sep 11 2009 12:26:26 : Video Encoding Stopped
    Fri Sep 11 2009 12:26:26 : Session Stopped
    Fri Sep 11 2009 12:26:32 : Primary - Network Status: NetConnection.Connect.Closed status
    Fri Sep 11 2009 12:26:32 : Primary - Disconnected
    Fri Sep 11 2009 12:26:37 : Primary - Connected to FMS/3,0,1,123
    Fri Sep 11 2009 12:26:49 : Primary - Network Command: onFCPublish
    Fri Sep 11 2009 12:26:49 : Primary - Stream[onetv] Status: Success
    Fri Sep 11 2009 12:26:49 : Primary - Stream[onetv] Status: NetStream.Publish.Start
    Fri Sep 11 2009 12:26:49 : Session Started
    Fri Sep 11 2009 12:26:50 : Audio Encoding Started
    Fri Sep 11 2009 12:26:50 : Video Encoding Started
    Hy, this is from my log.
    I connect the flash media encoder to flash media server, and after a short time it disconnect from server and try to reconect automatically, that is good, but IT DON'T CONNECT!!!
    Stream[onetv] Status: NetStream.Publish.BadName
    Fri Sep 11 2009 12:26:26 : Audio Encoding Stopped
    Fri Sep 11 2009 12:26:26 : Video Encoding Stopped
    Fri Sep 11 2009 12:26:26 : Session Stopped
    Where is the problem??? What i can do to resolve this problem?????
    I'm waiting for your answers!
    Thanks

    The NetStream.Publish.BadName status means an attempt was made to publish to a stream that is already being published by someone else. Is another client using the same stream name?
    About the connections being closed, there a lots of conditions that could cause the connection to be lost. It may not be an FMS or FMLE error, it could be poor conditions on the local network, or between the local network and the server.

  • ICal Publish failed

    After starting a new .Mac family pack membership. I changed my .Mac user/pass in System Prefs, and "unpublished" the calendars in iCal.
    Now, when I go to Publish them I get
    Publish failed for calendar 'Main'.
    Request to the server failed.
    Which seems like a connectivity problem but I can Sync perfectly with .Mac and also access my iDisk ok.
    I have tried deleting a calendar and re-creating it. I also tried publishing a brand new calendar. Those gave the same errors, so I don't think the problem is in the calendar itself.
    This is lame of course, because a main reason for my changing to the family pack was so my workgroup could all publish for group calendaring.
    Any help would be greatly appreciated, thanks.
    David

    Apple helped me finally fix this problem. Go into System Prefs, .Mac.
    Go to the iDisk tab, and change your Public Folder settings to Read and Write. (This is a temporary change)
    Next try several things to test it. Try opening your iDisk from the Finder. Try writing to the iDisk inside a folder such as "Documents".
    When I had this problem, the iDisk would not allow writing, and would fail with a disk space error.
    You can also test Backup, or Calendar publish now. If everything is working, you can reset the Public Folder settings to Read Only.
    What Apple explained to me via phone, is that there was a permissioning error when the new account was originally set up. Somehow, setting it to Read/Write fixes these permissions, and then you can work with all .Mac features as intended. If you still further probs, I recommend requesting to Apple support that they escalate your request to a more highly qualified engineer, and arrange a phone call. That was the deal for me, and he had it fixed in 2 minutes, after months of frustration.
    Best,
    David
    CEO, Clearlightpictures.com

  • Publish Failed: Captivate 6.1, Mac OSX 10.8.5

    I am experiencing the dreaded and unhelpful "Publish Failed" error message as well. I receive the message only when I am publishing a project with a quiz; projects without quizzes publish without any issue. I am publishing only to SWF output. I am running the latest build of Captivate: 6.1.0.319. I'm running a MacBook Pro Retina on OSX 10.8.5.
    Reading through similar previous threads, I saw mention of a file named "Default.html" to be found in ../Publish/SCORM/Default/1_2.
    But the file I find residing there is named "Default_HTML5.html". I don't know if this makes any difference.
    I have deleted the plist file as well. Still no joy.
    Please, I am open to any suggestions. Thanks in advance.

    Hi There,
    Greetings from Adobe.
    Please try the below steps and see if it works for you:
    It seems that Defaul.htm is missing from your SCORM folder . I am sending you the Zip file. Please unzip it and replace it with the SCROM folder already located on Captivate installed location. Please follow the below steps:
    Download the zip file from the following link -  https://workspaces.acrobat.com/?d=pjLGDuZsiduZy79qoEcDEw
    Unzip it.
    Take the backup of the SCORM folder present at “/Applications/Adobe Captivate 6/Templates/Publish/”
    Replace the one with the unzipped folder.
    Re-launch the captivate.
    Open the captivate project which has SCORM1.2 reporting.
    Re-Publish it.
    Let me know if you still face the same issue.
    Regards,
    Mayank

  • Why do I get Publish Failed Error Message when trying to publish a project to SWF. I am using Captivate 6 (32 Bit) Version 6.0.1.240. I have tried clearing the Cache and renaming my Preferences folder

    Why do I get Publish Failed Error Message when trying to publish a project to SWF. I am using Captivate 6 (32 Bit) Version 6.0.1.240. I have tried clearing the Cache and renaming my Preferences folder

    Try the troubleshooting tips here:
    http://www.infosemantics.com.au/adobe-captivate-troubleshooting/basic-troubleshooting-tech niques
    You may have something in your project on one of the slides that is tripping up the publishing process.

  • NetStream.Publish.BadName

    For some reason my Internet connection between FME and FMS is
    not stable. When connection
    with my live stream is dropped I can't reconnect to FMS and
    I'm getting " NetStream.Publish.BadName"
    error. It is because previous session (project) exists for
    random time.
    The only solution I made is to put FME in command line mode
    in batch continous loop (as
    FME exits on that error so the standard reconnect procedure
    does not work) - it takes even
    few minutes in few cases I was able to trace (many tries). In
    GUI mode situation is much is
    worse - there is dialog window that requires clicking when
    that error occurs.
    The other one is manual and requires someone watching stream
    24/7 - vhost restart - plus all
    clients are dropped. Baaad - it is better to make clients
    wait for stream 2-5 minutes than force all of them
    to restart live stream Flash player.
    Is live streaming with FME + FMS designed to work only on
    stable LAN connection?
    Even if that is true such disconnects can occur - so this bug
    is really anoying.
    Does anyone found other solutions than mine?

    The same problem with latest FME 3.2 and FMS 4.5 default live app. Setting PublishTimeout=-1 serverside and/or increasing reconnect interval in FME does not help.
    Any workaround except custom live app with shared objects?

  • Scheduled Publish failed

    Hi,
    i have a Scheduled realtime Publish,but it failed,could you help me?Thank you!
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event ApprovalQueue was not executed as another cluster member has executed it.
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:45:00 CST 2015
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event PublishEvent_1422966231808 was not executed as another cluster member has executed it.
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:35:00 CST 2015
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event CacheServer was not executed as another cluster member has executed it.
    [2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:35:00 CST 2015

    Can you explain more about the failure? Are you saying the event did not run on time or the publishing failed?

  • NetStream publish and play synchronize buffers

    NetStream publish and play synchronize buffers

    I haven't tried to run your code, but something obvious is
    the server-side code. It doesn't do anything.
    When you publish a stream, you need to tell other client to
    connect to it... manually. There are three thing to account for. A
    client connecting needs to subscribe to all existing streams. A
    client connecting needs to inform all existings clients that it has
    published its stream and give them the stream name so they can
    subscribe. The client needs to receive stream names of any new
    (future) connecting clients so it can subscribe to their stream.
    First you need to publish your stream... lets say this is
    client A and publishes a stream named stream_A.
    1. Then you need to send the stream name (stream_A) to all
    other existing clients, so they can subscribe to it.
    2. Then you need to receive the names of existing clients
    streams, so the client can subscribe to them.
    The logic in step 1, will handle any new clients connecting
    in the future.
    If anyone sees any errors in this or has a better method..
    please feel free to add to it....

  • SCUP 2011 publishing fails with error: Failed to sign package; error was: 2148081670

    Hi,
    I have a SCUP 2011 installed on the same machine has SCCM 2012 and WSUS. I installed and configured SCUP 2011, as shown in this video http://www.youtube.com/watch?v=fyEGWSFWyy0. Everything was ok, but after upgrading to SCCM 2012 R2, i'm unable to publish
    to the update server.
    Every single publishing attempt fails with error:
       at Scup.Wizards.PublishOperation.Start()         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()         01/01/1601 00:00:00    33730480 (0x202AFB0)
       at System.Threading.ThreadPoolWorkQueue.Dispatch()    Updates Publisher    27/11/2013 16:04:52    6 (0x0006)
    PublishItem: InvalidException occurred during publishing: Failed to sign package; error was: 2148081670    Updates Publisher    27/11/2013 16:04:52    6 (0x0006)
    Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.    Updates Publisher    27/11/2013
    16:04:52    6 (0x0006)
    Publish: Background processing completed.    Updates Publisher    27/11/2013 16:04:52    1 (0x0001)
    I have deleted and generate new self-signed WSUS certs, and i have imported them to the appropriated cert stores.
    I have checked and double-checked the posts about this subject on this forum, but haven't found any working solution.
    Appreciate all the help u guys can give me.
    Best regards,
    Adriano

    Hi,
    Please try applying the update below for this issue.
    System Center Update Publisher does not publish customized updates to a computer if WSUS 3.0 SP2 and the .Net Framework 4.0 are installed
    http://support.microsoft.com/%3Fkbid%3D2530678
    Have you looked at this
    System Center Update Publisher 2011 and Windows Server 2012
    http://blogs.msdn.com/b/minfangl/archive/2012/12/01/system-center-update-publisher-2011-and-windows-server-2012.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.

Maybe you are looking for

  • 2007 Meeting Workspace move via content and structure not working

    We are trying to move several meeting workspaces from a 5th level sub-site to a 2nd level site within the same site collection.  We know regular sites at the same or different level can be moved, but for some reason the meeting workspaces won't move.

  • Where is the JAR file?

    Dear sir/madam, I am now using the J2ME version 2.0 (beta) in that when I build the program I can't see the JAR file. May I know where will be the Jar file for the application? How t orun that using the Run-OTA option in this? Thanks

  • Sharing a site's data?

    Is there a way of sharing a site's data between two iWeb 09 users so we can each work on it? I don't mean anything elaborate like simultaneous collaborative editing or even check-out / check-in. I just mean downloading the current site from wherever

  • Communication Components for Flash 8

    Hi Guys, I need to develop a Flash file which has communication components in, I tried downloading the components for mx2004 which was released in 2003 but it tells me that I do not have Flash MX2004 installed. I don't but I do have flash 8 installed

  • Screen locks up ?

    When I plug the usb cable into my ipod to sync to itunes if it is not up and running(black screen) it will freeze up. this is second time this has happened. Last time I had to wait until the battery ran out to resync it to my computer. It is froze up