Error activating publishing feature

Hello... im having a problem while i try to activate the publishing feature, i get this error
The field {51d39414-03dc-4bd0-b777-d3e20cb350f7} defined in feature {aebc918d-b20f-4a11-a1db-9ed84d79c87e} is founded in site collection or in a subsite
I maked a program to read all the guid of fields in the sites and list,, and dont found {51d39414-03dc-4bd0-b777-d3e20cb350f7}, thanks in advance

Hi Diego,
If you have already activated the Site Collection feature SharePoint Server Publishing Infrastructure prior to activating the Site Feature SharePoint Server Publishing then run: stsadm -o activatefeature -id
AEBC918D-B20F-4a11-A1DB-9ED84D79C87E -url
http://YourWebApp.com -force.. This will force the feature to be installed..
The field PublishingStartDate is an element of the feature Asset Library 
            <Field ID="{51d39414-03dc-4bd0-b777-d3e20cb350f7}"
                Name="PublishingStartDate"
                StaticName="PublishingStartDate"
                SourceID="http://schemas.microsoft.com/sharepoint/v3"
                Group="$Resources:cmscore,group_publishingcolumns;"
                DisplayName="$Resources:cmscore,column_startdate_displayname;"
                Type="PublishingScheduleStartDateFieldType"
                Required="FALSE" CanToggleHidden="TRUE"
                Sealed="TRUE"
                StorageTZ="UTC">
            </Field>
The Asset Library is an element of the the feature Publishing Resources and a prequisite of the feature Publishing Site
<Feature  Id="AEBC918D-B20F-4a11-A1DB-9ED84D79C87E"
          Title="Publishing Resources"
          Description="Enable Publishing for site collection."
          Version="14.0.3.0"
          Scope="Site"
          Hidden="TRUE"
          DefaultResourceFile="core"
          ReceiverAssembly="Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
          ReceiverClass="Microsoft.SharePoint.Publishing.PublishingResourcesFeatureHandler"
          xmlns="http://schemas.microsoft.com/sharepoint/">
-Ivan
Ivan Sanders My LinkedIn Profile,
My Blog,
@iasanders.

Similar Messages

  • The Specified name is already in use while activating Publishing feature at site collection level in Moss2007

    Hi,
    Please suggest on this "The Specified name is already in use while activating Publishing feature at site collection level in Moss2007"
    The specified name is already in use.
    A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site.  Use your browser's Back button, and type a new name.   at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateList(String
    bstrWebUrl, String bstrTitle, String bstrDescription, String bstrListUrl, String bstrFeatureId, Int32 lTemplateID, String bstrDocTemplateType, ListQuickLaunchOptions qlOpt)
       at Microsoft.SharePoint.Library.SPRequest.CreateList(String bstrWebUrl, String bstrTitle, String bstrDescription, String bstrListUrl, String bstrFeatureId, Int32 lTemplateID, String bstrDocTemplateType, ListQuickLaunchOptions qlOpt)  

    there are some OutBox list/libraries being created when you activate publishing features, make sure those names not being used: check this post for more detail..
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/f7e93d26-c2a1-42c2-b191-dc48f734684b/the-specified-name-is-already-in-use-error?forum=sharepointgenerallegacy
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • Remove reference to Publishing Feature from site template

    Hi all, I have a custom site collection which I package as a wsp to deploy as a custom solution template to multiple sites.
    Accidentally, years ago I've activated Publishing Features in my site template and then disabled them. I still work and create new templates from my site without any problems (ShP 2010).
    Now, I've installed SharePoint 2013 and updated my site template to 2013. Then, I've created the new wsp but when I try to apply my template to a new site collection I receive an error message: "Failed to instantiate file "AlternateMediaPlayer.xaml"
    from module "Style LibraryMedia Player_Features\PublishingResources": Source path "Features\PublishingResources\AlternateMediaPlayer.xaml" not found."
    How could I remove all the reference to features belonging to Publishing Features?

    Hi Elena_B,
    According to your description, my understanding is that you want to remove reference to publishing feature from site template in SharePoint 2013.
    You can do as the followings:
    extract all files from WSP file by (a tool or) changing the wsp file to cab file and then extract all files to a working folder.
    edit the Onet.xml file to remove the unsupported features and save the changes.
    create a ddf file for makecab.exe to repack the wsp
    run cmd: makecab /f my.ddf to generate the new WSP file
    More information, please refer to the link:
    http://lassewikmark.wordpress.com/2009/11/16/howto-remove-unused-features-from-a-site-template-file/
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/37e96410-7fb9-462b-a3e7-c150f2de7107/site-template-and-disabled-feature?forum=sharepointadminprevious
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.

    Hi All,
    I am trying to activate the Publishing feature for a SharePoint website using a custom Site Definition File. The problem I am getting
    is when I try to use the custom site template I get an error message:
    New-SPSite : The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.
    The custom
    Site Definition File snippet is show below:
    <?xml
    version="1.0"
    encoding="utf-8"?>
    <Project
    Title="SiteDefinition1"
    Revision="2"
    ListDir=""
    xmlns:ows="Microsoft
    SharePoint"
    xmlns="http://schemas.microsoft.com/sharepoint/">
      <NavBars>
      </NavBars>
      <Configurations>
        <Configuration
    ID="0"
    Name="SiteDefinitionDelegateControls2">
          <Lists/>
          <SiteFeatures>
            <!--Document
    Set-->     
            <Feature
    ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}"
    Name="FeatureDefinition/15/3bae86a2-776d-499d-9db8-fa4cdc7884f8"
    />
            <!--Publishing
    Prerequisites-->     
            <Feature
    ID="{a392da98-270b-4e85-9769-04c0fde267aa}"
    Name="FeatureDefinition/15/a392da98-270b-4e85-9769-04c0fde267aa"
    />
          ...Other Site Features
          </SiteFeatures>
         <WebFeatures>
            <!--2
    Publishing Web-->
         <Feature
    ID="{94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb}"
    Name="FeatureDefinition/15/94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb"/>
         ... Other Web Features
          </WebFeatures>
          <Modules>
            <Module
    Name="DefaultBlank"
    />
          </Modules>
        </Configuration>
      </Configurations>
      <Modules>
        <Module
    Name="DefaultBlank"
    Url=""
    Path="">
          <File
    Url="default.aspx">
          </File>
        </Module>
      </Modules>
    </Project>
    I hope you can help
    Colin

    As the error says.  The Publishing Infrastructure feature must be activated at the Site Collection level where you are creating a new site PRIOR to turning on the Publishing feature.  So if you are trying to use this site definition to create a
    new Site Collection then its not going to work.  If you are trying to create a sub site then make sure that Publishing Infrastructure is enabled in the site collection before trying to create a sub site with this site definition.
    Internally Microsoft does this for the Publishing Portals using custom code.  Here's an article that discusses how to do it in SharePoint 2010.  
    http://msdn.microsoft.com/en-us/library/office/gg615465(v=office.14).aspx
    Compare what's in the article to one of the Publishing templates available out of the box in 2013 and you should be able to find the assembly that is used to load the Publishing features.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Ran into a problem by activating the SharePoint Server Publishing feature

    By activating the "SharePoint Server Publishing feature"  at site level the complete look and feel of the site has been changed to a default page layout , all the customization's were removed.
    Changes were not rolled back even after deactivating the feature.
    any help on how to get back my look and feel is appreciated.
    Thanks in advance.
    Regards
    Bhaskar
     

    Hi,
    How did you customize the site initially? Was that in SharePoint designer? And if so what part of it did you exactly customize? The page itself or the masterpage?
    Regards,
    Casper

  • Turn off publishing feature without messing up the SharePoint site

    Hi,
    Is it possible to turn off the publishing feature (after it was turned on), without goofing up the SharePoint site and creating problems?  I want to save a site as a template and just discovered that that option is not available when publishing is enabled. 
    Why does Microsoft make these decisions arbitrarily?  Ugh!
    Thanks! Patti N.

    There are many ways to tweak and achieve the target i.e. saving publishing site as template, but if you try creating a new site using that template on a non-publishing site, it will surely gonna fail with some generic error
    Even if you deactivate the ft and then save site as template, it will fail when you try creating another site using that template on a non-publishing site. So basically, it can only create a new site using that template only if the destination site have
    the publishing ft activated
    SharePoint does not support Save Site as Template option with the Publishing features turned on. The supported method to create templates for publishing sites is to use a site definition template and using a feature XML.
    Please refer:
    https://support.microsoft.com/kb/2492356?wa=wsignin1.0
    To answer your question, Why does Microsoft make these decisions arbitrarily?
    when you activate the Publishing ft is the ability to use Web Content Management and create custom Page Layouts and change the way you can mange and display the information.You can manage Content and how this content will be shared to all users, you can
    work with Content types and associate with Pages to change and categorize you information and display to public, i use for SharePoint internet Site because is a very easy way to users create new content and display to public this information, there
    another features you can use with publishing feature like active the Output Cache this feature will improve performance in the page load because the webpart, metadata and page will be stored in cache, you can also define if you want to manage the
    profiles for this cache, anonymous access or authenticated users.
    All these changes happen when you activate publishing ft and wont get revert when you deactivate the feature, Hence it is not possible
    To know more about publishing ft, please refer
    https://technet.microsoft.com/en-us/library/ff628963(v=office.14).aspx

  • Activate web publishing feature problem

    I am trying to use the object model to activate the site collection publishing feature, and the web publishing feature on a new site. Here is a snippet of my code.
    using (SPSite site = new SPSite(SiteUrl))
    using (SPWeb web = site.OpenWeb())
    //Activate the publishing feature at the site collection level (PublishingSite)
    site.Features.Add(new Guid("F6924D36-2FA8-4f0b-B16D-06B7250180FA"));
    //Activate the publishing feature at the web level (PublishingWeb)
    web.Features.Add(new Guid("94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB"));
    The problem is I get an error that says "The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated."
    I have browsed to the site and verified the Publishing feature is activated at the site collection level. I have double checked that the GUIDs are correct. Does anyone have an idea why I am getting this error and cannot activate the publishing feature on
    the web level?

    Hi
    Did you try like this, I meant adding allowunsafeupdates
    using (SPSite site = new SPSite(SiteUrl))
    using (SPWeb web = site.OpenWeb())
    { site.AllowUnsafeUpdates = true;
    //Activate the publishing feature at the site collection level (PublishingSite)
    site.Features.Add(new Guid("F6924D36-2FA8-4f0b-B16D-06B7250180FA")); site.AllowUnsafeUpdates = false; web.AllowUnsafeUpdates = true;
    //Activate the publishing feature at the web level (PublishingWeb)
    web.Features.Add(new Guid("94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB")); web.AllowUnsafeUpdates = false;
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Publishing Features Property WelcomePageUrl and Page Not Found

    Hello guys,
    I have created a Site Definition using Visual Studio 2012 which generates 3 files for us: Default.aspx - Webtemp_SiteDefinition1.xml - Onet.xml
    I have customized only the onet.xml as follows:
    <?xml version="1.0" encoding="utf-8"?>
    <Project Title="SiteDefinition1" Revision="2" ListDir="" xmlns:ows="Microsoft SharePoint" xmlns="http://schemas.microsoft.com/sharepoint/">
    <NavBars>
    </NavBars>
    <Configurations>
    <Configuration ID="0" Name="SiteDefinition1" CustomMasterUrl="_catalogs/masterpage/mymaster.master" MasterUrl="_catalogs/masterpage/mymaster.master">
    <Lists/>
    <SiteFeatures>
    <!--PublishingPrerequisites Feature-->
    <Feature ID="{a392da98-270b-4e85-9769-04c0fde267aa}"/>
    <!--PublishingResources Feature-->
    <Feature ID="{aebc918d-b20f-4a11-a1db-9ed84d79c87e}"/>
    <!--PublishingLayouts Feature-->
    <Feature ID="{d3f51be2-38a8-4e44-ba84-940d35be1566}"/>
    <!--Publishing Feature-->
    <Feature ID="{f6924d36-2fa8-4f0b-b16d-06b7250180fa}" />
    <!--Sharepoint Server Standard Feature-->
    <Feature ID="{b21b090c-c796-4b0f-ac0f-7ef1659c20ae}" />
    <!--Sharepoint Server Enterprise Feature-->
    <Feature ID="{8581a8a7-cf16-4770-ac54-260265ddb0b2}" />
    <!--Document Set Feature-->
    <Feature ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}" />
    <!--Document ID Feature-->
    <Feature ID="{b50e3104-6812-424f-a011-cc90e6327318}" />
    <!--Search Server Webparts Feature-->
    <Feature ID="{eaf6a128-0482-4f71-9a2f-b1c650680e77}" />
    <!-- Termstore Site Features -->
    <Feature ID="73EF14B1-13A9-416b-A9B5-ECECA2B0604C" />
    <Feature ID="7C637B23-06C4-472d-9A9A-7C175762C5C4" />
    <Feature ID="AEBC918D-B20F-4a11-A1DB-9ED84D79C87E">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="AllowRss" Value="false"/>
    <Property Key="SimplePublishing" Value="false" />
    </Properties>
    </Feature>
    <Feature ID="7916bd78-38dd-4595-a02f-68cd4975144a" />
    </SiteFeatures>
    <WebFeatures>
    <Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/mymaster.master"/>
    <Property Key="PagesListUrl" Value=""/>
    <Property Key="AvailableWebTemplates" Value=""/>
    <Property Key="AvailablePageLayouts" Value=""/>
    <Property Key="SimplePublishing" Value="true" />
    </Properties>
    </Feature>
    <Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="InheritGlobalNavigation" Value="true"/>
    <Property Key="IncludeSubSites" Value="true"/>
    <Property Key="IncludePages" Value="false"/>
    </Properties>
    </Feature>
    <Feature ID="94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" />
    </WebFeatures>
    <Modules>
    <Module Name="DefaultBlank" />
    </Modules>
    </Configuration>
    </Configurations>
    <Modules>
    <Module Name="DefaultBlank" Url="" Path="">
    <File Url="default.aspx">
    </File>
    </Module>
    </Modules>
    </Project>
    This code works very well while creating a Top Level Site Collection or a Site Collection under a Site Collection.
    However when I add the WelcomePageUrl Property of the Publishing Feature (see below), SharePoint throws an error "Page not found - The page you're looking for doesn't exist."
    Note that I would like to set a WelcomePageUrl which would be a customized default.aspx or even renamed aspx file (for example: mydefault.aspx)
    <Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/LenzeV4.master"/>
    <Property Key="WelcomePageUrl" Value="$Resources:osrvcore,List_Pages_UrlName;/default.aspx"/>
    <Property Key="PagesListUrl" Value=""/>
    <Property Key="AvailableWebTemplates" Value=""/>
    <Property Key="AvailablePageLayouts" Value=""/>
    <Property Key="SimplePublishing" Value="true" />
    </Properties>
    </Feature>
    Please help.

    Hello guys,
    Was on leave so could not reply!
    The trick is to name the module like the custom default page - for example in my case my default page name is "defaultCustom.aspx" hence I named the module <Module Name="defaultCustom" />.
    Here is the entire onet.xml
    <?xml version="1.0" encoding="utf-8"?>
    <Project Title="SiteDefinition1" Revision="2" ListDir="" xmlns:ows="Microsoft SharePoint" xmlns="http://schemas.microsoft.com/sharepoint/">
    <NavBars>
    </NavBars>
    <Configurations>
    <Configuration ID="0" Name="SiteDefinition1" CustomMasterUrl="_catalogs/masterpage/CustomV4.master" MasterUrl="_catalogs/masterpage/CustomV4.master">
    <Lists/>
    <SiteFeatures>
    <!--PublishingPrerequisites Feature-->
    <Feature ID="{a392da98-270b-4e85-9769-04c0fde267aa}"/>
    <!--PublishingResources Feature-->
    <Feature ID="{aebc918d-b20f-4a11-a1db-9ed84d79c87e}"/>
    <!--PublishingLayouts Feature-->
    <Feature ID="{d3f51be2-38a8-4e44-ba84-940d35be1566}"/>
    <!--Publishing Feature-->
    <Feature ID="{f6924d36-2fa8-4f0b-b16d-06b7250180fa}" />
    <!--Sharepoint Server Standard Feature-->
    <Feature ID="{b21b090c-c796-4b0f-ac0f-7ef1659c20ae}" />
    <!--Sharepoint Server Enterprise Feature-->
    <Feature ID="{8581a8a7-cf16-4770-ac54-260265ddb0b2}" />
    <!--Document Set Feature-->
    <Feature ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}" />
    <!--Document ID Feature-->
    <Feature ID="{b50e3104-6812-424f-a011-cc90e6327318}" />
    <!--Search Server Webparts Feature-->
    <Feature ID="{eaf6a128-0482-4f71-9a2f-b1c650680e77}" />
    <!-- Termstore Site Features -->
    <Feature ID="73EF14B1-13A9-416b-A9B5-ECECA2B0604C" />
    <Feature ID="7C637B23-06C4-472d-9A9A-7C175762C5C4" />
    <Feature ID="AEBC918D-B20F-4a11-A1DB-9ED84D79C87E">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="AllowRss" Value="false"/>
    <Property Key="SimplePublishing" Value="false" />
    </Properties>
    </Feature>
    <!--Custom Site Feature-->
    <Feature ID="7916bd78-38dd-4595-a02f-68cd4975144a" />
    <!--Custom Master Page Feature-->
    <Feature ID="{66b35b36-fd66-4a16-ab68-d3b47ae8cbf7}" />
    <!--Custom Layout Page Feature-->
    <Feature ID="{7a226876-f2c4-45da-b09b-bd06598cecac}" />
    </SiteFeatures>
    <WebFeatures>
    <!-- Publishing feature -->
    <Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416">
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/CustomV4.master"/>
    <Property Key="DefaultPageLayout" Value="~SiteCollection/_catalogs/masterpage/Custom.Layout.aspx"/>
    <Property Key="WelcomePageUrl" Value="$Resources:osrvcore,List_Pages_UrlName;/defaultCustom.aspx" />
    <Property Key="SimplePublishing" Value="true" />
    <Property Key="RequireCheckoutOnPages" Value="False" />
    </Properties>
    </Feature>
    <!--This Feature and Properties corresponds to the Navigation Settings UI page-->
    <Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA">
    <!-- Per-Web Portal Navigation Properties-->
    <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
    <Property Key="InheritGlobalNavigation" Value="true"/>
    <Property Key="ShowSiblings" Value="true"/>
    <Property Key="IncludeSubSites" Value="true"/>
    </Properties>
    </Feature>
    <!-- Enterprise Wiki Feature -->
    <Feature ID="76D688AD-C16E-4cec-9B71-7B7F0D79B9CD" />
    </WebFeatures>
    <Modules>
    <Module Name="defaultCustom" />
    </Modules>
    </Configuration>
    </Configurations>
    <Modules>
    <Module Name="defaultCustom" Url="$Resources:osrvcore,List_Pages_UrlName;" Path="">
    <File Url="defaultCustom.aspx" Type="GhostableInLibrary" Level="Draft" >
    <Property Name="Title" Value="$Resources:cmscore,EnterpriseWiki_Site_WelcomePageTitle;" />
    <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/Custom.Layout.aspx, Custom Web Part Page" />
    <Property Name="ContentType" Value="$Resources:cmscore,contenttype_welcomepage_name;" />
    </File>
    </Module>
    </Modules>
    </Project>

  • Error when Publish data to passive cache

    Hi,
    I am using active-passive push replication. When I add data to active cache, the data added to cache but get the below error during publish data to passive cache.
    011-03-31 22:38:06.014/291.473 Oracle Coherence GE 3.6.1.0 <Error> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): Failed to publish EntryOperation{siteName=site1, clusterName=Cluster1, cacheName=dist-contact-cache, operation=Insert, publishableEntry=PublishableEntry{key=Binary(length=12, value=0x154E094D65656E616B736869), value=Binary(length=88, value=0x12813A15A90F00004E094D65656E61
    6B736869014E07506C6F74203137024E074368656E6E6169034E0954616D696C4E616475044E06363030303432401A155B014E0524737263244E0E73697465312D436C757374657231), originalValue=Binary(length=0, value=0x)}} to Cache dist-contact-cache because of
    (Wrapped) java.io.StreamCorruptedException: invalid type: 78 Class:com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher
    2011-03-31 22:38:06.014/291.473 Oracle Coherence GE 3.6.1.0 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): An exception occurred while processing a InvocationRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache[dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
    Here is my coherence cache config xml file
    !DOCTYPE cache-config SYSTEM "cache-config.dtd">
    <cache-config xmlns:sync="class:com.oracle.coherence.patterns.pushreplication.configuration.PushReplicationNamespaceContentHandler">
    <caching-schemes>
    <sync:provider pof-enabled="true">
    <sync:coherence-provider />
    </sync:provider>
    <caching-scheme-mapping>
    <cache-mapping>
    <cache-name>dist-contact-cache</cache-name>
    <scheme-name>distributed-scheme-with-publishing-cachestore</scheme-name>
    <sync:publisher>
         <sync:publisher-name>Active Publisher</sync:publisher-name>
         <sync:publisher-scheme>
         <sync:remote-cluster-publisher-scheme>
         <sync:remote-invocation-service-name>remote-site2</sync:remote-invocation-service-name>
         <sync:remote-publisher-scheme>
         <sync:local-cache-publisher-scheme>
         <sync:target-cache-name>dist-contact-cache</sync:target-cache-name>
         </sync:local-cache-publisher-scheme>
         </sync:remote-publisher-scheme>
         <sync:autostart>true</sync:autostart>
         </sync:remote-cluster-publisher-scheme>
         </sync:publisher-scheme>
    </sync:publisher>
    </cache-mapping>
    </caching-scheme-mapping>
    <proxy-scheme>
    <service-name>ExtendTcpProxyService</service-name>
    <thread-count>5</thread-count>
    <acceptor-config>
    <tcp-acceptor>
    <local-address>
    <address>localhost</address>
    <port>9099</port>
    </local-address>
    </tcp-acceptor>
    </acceptor-config>
    <autostart>true</autostart>
    </proxy-scheme>
    <remote-invocation-scheme>
    <service-name>remote-site2</service-name>
    <initiator-config>
    <tcp-initiator>
    <remote-addresses>
    <socket-address>
    <address>localhost</address>
    <port>5000</port>
    </socket-address>
    </remote-addresses>
    <connect-timeout>2s</connect-timeout>
    </tcp-initiator>
    <outgoing-message-handler>
    <request-timeout>5s</request-timeout>
    </outgoing-message-handler>
    </initiator-config>
    <serializer>
              <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
         </serializer>
    </remote-invocation-scheme>
    </caching-schemes>
    </cache-config>

    Please find below for active and passive server start command, log files.
    Thanks.
    Active server start command
    java -server -showversion -Xms128m -Xmx128m -Dtangosol.coherence.ttl=0 -Dtangosol.coherence.cacheconfig=active-cache-config.xml
    -Dtangosol.coherence.cluster="Cluster1" -Dtangosol.coherence.site="site1" -Dtangosol.coherence.clusteraddress="224.3.6.2"
    -Dtangosol.coherence.clusterport="3001" -Dtangosol.pof.config=pof-config.xml -cp "config;lib\custom-types.jar;lib\coherence.jar;lib/coherence-common-1.7.3.20019.jar;lib/coherence-pushreplicationpattern-3.0.3.20019.jar;lib/coherence-messagingpattern-2.7.3.20019.jar;" com.tangosol.net.DefaultCacheServer
    Passive server start command
    java -server -showversion -Xms128m -Xmx128m -Dtangosol.coherence.ttl=0 -Dtangosol.coherence.cacheconfig=passive-cache-config.xml
    -Dtangosol.coherence.cluster="Cluster2" -Dtangosol.coherence.site="site2" -Dtangosol.coherence.clusteraddress="224.3.6.3"
    -Dtangosol.coherence.clusterport="3003" -Dtangosol.pof.config=pof-config.xml -cp "config;lib\custom-types.jar;
    lib\coherence.jar;lib/coherence-common-1.7.3.20019.jar;lib/coherence-pushreplicationpattern-3.0.3.20019.jar;
    lib/coherence-messagingpattern-2.7.3.20019.jar;" com.tangosol.net.DefaultCacheServer
    Active Server log
    <Error> (thread=PublishingService:Thread-3, member=1): Failed to publish the range MessageTracker{MsgId{40-1} } of messages for subscription SubscriptionIdentifier{destinationIdentifier=Identifier{dist-contact-cache}, subscriberIdentifier=Identifier{Active Publisher}} with publisher com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher@423d4f Class:com.oracle.coherence.patterns.pushreplication.providers.coherence.CoherencePublishingService
    2011-04-01 20:23:20.172/65.972 Oracle Coherence GE 3.6.1.0 <Info> (thread=PublishingService:Thread-3, member=1): Publisher Exception was as follows Class:com.oracle.coherence.patterns.pushreplication.providers.coherence.CoherencePublishingService
    (Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache [dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish t
    o cache dist-contact-cache
    at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
    at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:348)
    at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.query(InvocationServiceProxy.CDB:6)
    at com.tangosol.coherence.component.net.extend.messageFactory.InvocationServiceFactory$InvocationRequest.onRun(InvocationServiceFactory.CDB:12)
    at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
    at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.onMessage(InvocationServiceProxy.CDB:9)
    at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:39)
    at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.onNotify(Peer.CDB:96)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
    at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:163)
    at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:343)
    ... 9 more
    Caused by: (Wrapped) java.io.StreamCorruptedException: invalid type: 78
    at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService$ConverterKeyToBinary.convert(PartitionedService.CDB:16)
    at com.tangosol.util.ConverterCollections$ConverterInvocableMap.invoke(ConverterCollections.java:2156)
    at com.tangosol.util.ConverterCollections$ConverterNamedCache.invoke(ConverterCollections.java:2622)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.invoke(PartitionedCache.CDB:11)
    at com.tangosol.coherence.component.util.SafeNamedCache.invoke(SafeNamedCache.CDB:1)
    at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:142)
    ... 10 moreCaused by: java.io.StreamCorruptedException: invalid type: 78
    at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2266)
    at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2254)
    at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:74)
    at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2708)
    at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:262)
    ... 16 more
    Passive Server log
    2011-04-01 20:23:20.141/56.925 Oracle Coherence GE 3.6.1.0 <Error> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): Failed to publish EntryOperation{siteName=site1, clusterName=Cluster1, cacheName=dist-contact-cache, operation=Insert, publishableEntry=PublishableEntry{key=Binary(length=12, value=0x154E094D65656E616B736869), value=Binary(length=88, value=0x12813A15A90F00004E094D65656E616
    B736869014E07506C6F74203137024E074368656E6E6169034E0954616D696C4E616475044E06363030303432401A155B014E0524737263244E0E73697465312D436C757374657231), originalValue=Binary(length=0, value=0x)}} to Cache dist-contact-cache because of (Wrapped) java.io.StreamCorruptedException: invalid type: 78 Class:com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher2011-04-01 20:23:20.141/56.925 Oracle Coherence GE 3.6.1.0 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): An exception occurred while processing a InvocationRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache [
    dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
    at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
    at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:348)
    at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.query(InvocationServiceProxy.CDB:6)
    at com.tangosol.coherence.component.net.extend.messageFactory.InvocationServiceFactory$InvocationRequest.onRun(InvocationServiceFactory.CDB:12)
    at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
    at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.onMessage(InvocationServiceProxy.CDB:9)
    at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:39)
    at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.onNotify(Peer.CDB:96)
    at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
    at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:163)
    at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:343)
    ... 9 more
    Caused by: (Wrapped) java.io.StreamCorruptedException: invalid type: 78
    at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService$ConverterKeyToBinary.convert(PartitionedService.CDB:16)
    at com.tangosol.util.ConverterCollections$ConverterInvocableMap.invoke(ConverterCollections.java:2156)
    at com.tangosol.util.ConverterCollections$ConverterNamedCache.invoke(ConverterCollections.java:2622)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.invoke(PartitionedCache.CDB:11)
    at com.tangosol.coherence.component.util.SafeNamedCache.invoke(SafeNamedCache.CDB:1)
    at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:142)
    ... 10 more
    Caused by: java.io.StreamCorruptedException: invalid type: 78
    at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2266)
    at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2254)
    at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:74)
    at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2708)
    at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:262)
    ... 16 more

  • Error Activating Adobe Digital Editions

    I downloaded and installed Adobe Digital Editions but when I open the program I get this message: Error Activating: E_ADEPT_IO ActivationServiceInfo Error%20#2032
    I tried uninstalling the program and then reinstalling it along with rebooting my system. What can I do to fix this problem?
    Thanks!

    Hi,
    Regarding the error message that you are getting you can try following steps:
    1) Open Adobe Digital Editions.
    2) Press Ctrl+Shift+D key of your Keyboard and deauthorize Digital Editions.
    3) Uninstall Adobe Digital Editions from your computer.
         Click start>>Control Panel>>Programs>>Programs and features.
         Select Adobe Digital Editions from the list and Delete.
    4) Also delete following files.
        Click Start>>Run
        Type "regedit" in the box and hit enter.
        Locate the following key "HKEY_CURRENT_USER>Software>Adobe>Digital Editions"
        delete the full folder (Right click on it and click delete).
         Also locate HKEY_CURRENT_USER>Software>Adobe>Adept
         Delete the full folder.
    5) Now open Internet explorer. go to Tools>>Internet  options>>Connections>>Lan settings. Check the “automatically  detect settings” box and uncheck all the other boxes.
    6) Now download and install Adobe Digital Editions from the link given below.
         http://www.adobe.com/products/digitaleditions/.
    7) When asked to authorize computer then please enter same Adobe ID and password which you were using earlier.
    8) Now try to open the books.
    I hope this will help you !!!
    Regards
    Rizwan

  • Publishing error when publishing one section

    I am publishing my material per module and receive the following error when publishing one of the modules:
    Publishing Activity Log:
    Task
    GMT Training Guide / Creating numbering styles in document
    Path
    /49b77e2d-7666-443e-a2fa-edbfc9aa22b2/Parts/pr.oxmlprint.multi.xml     
    Comment
    Processing project failed
    Ref. #
    -1673847682
    All of the other modules publish with no problems.
    Any assistance in this regard would be much appreciated.
    Thanks,
    Angie

    Did you copy the text in there? Could be the following:
    The problem is related to concept frames. Some concept frames have not regular charachters. Those characters aren't visible in the edit mode. The are only visible if you copy the text of the concept frame to word. In word use the button "display unknow characters". It seemed like they will appear if you copy and paste text in the conceptframes.
    You need to copy the text of the editor to Word. Click on the button "display unknown characters" to see all characters in text (including e.g.enter and spacebar). Remove the strange characters such as small circles. Copy the text and paste it back into the editor.
    Save the editor (and publish again).
    Good luck.

  • Recreate site from template - publishing feature

    I have a site with Publishing feature activated and I need to recreate the same site on another server (actually, it is many sites). How can I do that? I don't have "save as template" option, but i have created template through url /_layouts/savetmpl.aspx.
    But, how can I recreate this site on another server (also publishing feature activated)?
    Or is the approach with saving site definition better solution? How do I do that, can I recreate site from site definition??

    You can use the template you created by downloading it from the Site Template Gallery of your current site.  Then take the .stp file and upload it to the site template gallery of the new server where you want to make the template available.  After
    that, the template should become available in your creation dialog.
    A better way to recreate the site exactly as is, on another farm, is to use either Powershell or good old STSADM.
    Execute this from the current server in a SharePoint Powershell window:
    stsadm -o backup -url http://your-site-url-here -filename SiteFileName.bak -nolock
    Then copy the SiteFileName.bak file to a server in the target farm and from a SharePoint Powershell window, execute this:
    stsadm -o restore -url http://new-target-url-to-use -filename C:\Path-to-Backup-file\SiteFileName.bak
    If the site already exists and you wish to overwrite it, simply add the -overwrite switch to the above command.
    I trust that answers your question...
    Thanks
    C
    |
    RSS |
    http://crayveon.com/blog |
    SharePoint Scripts | Twitter |
    Google+ | LinkedIn |
    Facebook | Quix Utilities for SharePoint
    Wher I try to save template to another site, I don't have it available when I want to create new site (because of Publishing feature), I have only two templates from Publishing template, not Custom.
    These Powershell commands are great, but this only works for top level site. Is there similar solution for subsites?

  • Java Desktop System, Release 2 - Error activating XKB configuration

    Hi,
    There is know problem with Java Desktop System, Release 2:
    If you log in using accessibility features on the Java
    Desktop System for the Solaris platform, the following
    error dialog might appear: Error activating XKB configuration.
    How can I solve this problem? Can I disable accessibility features (especially when I log in using NoMachine NX Client)?
    Thanks,
    Rafal

    I have been trying to install Oracle version 10g on Sun Java Desktop System Release 2 (Linux) but unable to do so.Some error message?
    Can I install Oracle on Sun Java Desktop System Release 2 (Linux)? How to do that?As far I know Sun JDS release 2 is based on SuSE so check Suse related installation papers.
    You can find them on http://www.oracle.com/technology/tech/linux/install/index.html
    What version of Oracle ver 10g Release 1 should I download?Depends on architecture (CPU) and installed OS version (32bit, 64bit).

  • Error while publishing enterprise service from ES builder.

    Hi Friends
    I am not able to publish my service from ES builder. I am getting this error after publishing.
    Please let me know if anyone has faced similar problem and has solution for it.
    Thanks
      -Mitesh
    This is the error log generated.
    javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 31 more Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more

    Hi ,
    try to change the ServiceRegistry Logical Port
    In NetWeaver Administrator under SOA Management _Business Administration _Web Services Administration
    Client Proxy Name: ServicesRegistrySi
    Authentication: User name/password
    Role: SERVICES_REGISTRY_READ_WRITE
    Should help u out

  • Failed to commit objects to server. Error while publishing reports from BW

    Hi,
    I am getting below error while publishing reports from BW to BO.
    "0000000001 Unable to commit the changes to Enterprise. Reason: Failed to commit objects to server : #Duplicate object name in the same folder."
    Anyone having any solution for this. Thanks in advance.

    Hi Amit
    It would be great if you could add a little info about how you solved this issue. Others might run into similar situations - I just did:-(
    Thank you:-)

Maybe you are looking for

  • Disc image and mounting question .

    Disc utility - file - new > blank disc image . Save as ( so so ) . Volume name (so so ) . Volume size (4.5 gb dvd-r/dvd-ram. ) . Volume format ( mac os extended journal ) . Encryption ( none ) . Partition (cd dvd ) Image format ( spars bundle disc im

  • Hibernate Error in JDeveloper

    Hi, I am developing a Hibernate based application, and I have been going thru some sample application to understand how to go about it. While running one of the sample applications, I get the following error. I have tried placing the slf4j-api-1.5.2.

  • Image Rady unter Windows 2000

    Hi! Ich benutze Imageready 3.0 und Photoshop 6.0 unter Windows 2000 Pro und Windows ME. Unter Windows ME gibt es auch keine Probleme allerdings unter Windows 2000. Hier sieht es so auch: Wenn ich Photoshop 6 verwende gibt es eine gute Reaktionszeit d

  • Document on Cisco 3845 gateway with both Voice and VXML role

    Dear all, we are using single cisco 3845 gateway as Ingress as well as vxml gateway . Can you provide any documentation regarding the call volume capacity this gateway can handle. We have deployed this gateway in a UCCE parent- child  model.

  • Failed to retrieve data set (roducts) for spry:repeat

    For some reason, I get this error.  Clearly the (roducts) should be (products) however when I do a global search through the entire directory for the word "products" I get 256 results, I then search for "roducts" and I get 256 results.  There is no m