RedHawk v2.1 Device IDL Error - redhawksdr

We have using RedHawk v2.1 on Xynq7035 ARM COretex A9 with Embedded Linux kernel 3.14. Our application is SSB Tx/Rx SDR. So waveforms consist of 3 types, one is SSB RX, two is SSB TX, three is CW TX. The HW device has 6 dataFloat ports and 6 dataUlong ports, each with a total of 12 ports. Start up procedure is below.
#nodeBooter -D &
#nodeBooter -d /usr/lib/redhawk/sdr/dev/nodes/dev_trx_node/DeviceManager.dcd.xml &
#rh_start.py &
rh_start.py code is below.
from ossie.utils import redhawk
import logging
logging.basicConfig()
domain_list = redhawk.scan()
dom = redhawk.attach(domain_list[0])
wave0 = dom.createApplication("/waveforms/rx_waveform/rx_waveform.sad.xml")
dom.devices[1].connect(wave0.comps[0], usesPortName='out_data_rx', providesPortName='in_data' )
The error is occered when connecting the device and waveform port. Error code is
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataFloat:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:BULKIO/dataUlong:1.0
ERROR:ossie.utils.model:Unable to find port description for IDL:CF/Port:1.0
ERROR:ossie.utils.model:Invalid port descriptor in scd for IDL:ExtendedEvent/MessageEvent:1.0enter code here
The error is on all the ports of my device and all ports of GPP. My device is created with RedHawk-IDE v2.1. GPP downloads v2.1 and cross-compiles. GPP.scd.xml has no changed. Is the scd.xml file wrong? our device ports section in scd.xml file is below.
<ports>
<provides repid="IDL:BULKIO/dataFloat:1.0" providesname="in_data_cw">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataFloat:1.0" usesname="out_data_cw">
<porttype type="data"/>
</uses>
<provides repid="IDL:BULKIO/dataFloat:1.0" providesname="in_data_rx">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataFloat:1.0" usesname="out_data_rx">
<porttype type="data"/>
</uses>
<provides repid="IDL:BULKIO/dataFloat:1.0" providesname="in_data_tx">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataFloat:1.0" usesname="out_data_tx">
<porttype type="data"/>
</uses>
<provides repid="IDL:BULKIO/dataUlong:1.0" providesname="in_cnt_cw">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataUlong:1.0" usesname="out_cnt_cw">
<porttype type="data"/>
</uses>
<provides repid="IDL:BULKIO/dataUlong:1.0" providesname="in_cnt_rx">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataUlong:1.0" usesname="out_cnt_rx">
<porttype type="data"/>
</uses>
<provides repid="IDL:BULKIO/dataUlong:1.0" providesname="in_cnt_tx">
<porttype type="data"/>
</provides>
<uses repid="IDL:BULKIO/dataUlong:1.0" usesname="out_cnt_tx">
<porttype type="data"/>
</uses>
</ports>
The application itself works, but could you tell us the cause of the error and the workaround?

it seems IDL:BULKIO/dataFloat:1.0 is not present in the IDL library according to the line 1266 of model module init. Check if IDL library exists in the path: $OSSIEHOME/share/idl. also check if your scd file has something like:
<interface name="ProvidesPortStatisticsProvider" repid="IDL:BULKIO/ProvidesPortStatisticsProvider:1.0"/>
<interface name="updateSRI" repid="IDL:BULKIO/updateSRI:1.0"/>
<interface name="dataFloat" repid="IDL:BULKIO/dataFloat:1.0">
<inheritsinterface repid="IDL:BULKIO/ProvidesPortStatisticsProvider:1.0"/>
<inheritsinterface repid="IDL:BULKIO/updateSRI:1.0"/>
</interface>
inside the interfaces tag.
a tip: ports can use core-framework IDLs, besides IDL:BULKIO, you can use IDL:CF/Resource to control a component, IDL:CF/Device to control a Device. you are even able to get a reference of the Domain using ports. This way, you can create a single waveform for the SSB (TX and RX) implemeting a proper Assembly controller, to dictate the way your waveform works.
Are you using a ADRV9361 (picozed sdr)? if so... you could evaluate my FrontEnd Device AD936X_LIBIIO... how did you embed (cross compiled) in Zynq REDHAWK?

IDL Library exists in /usr/share/idl/ossie/BULKIO Is not $OSSIEHOME/share/idl, but bio_daraUlog_idl.py and bio_dataFloat_idl.py are in $OSSIEHOME/lib/python/bulkio/bulkioInterface . I'm sorry to forgot discribe "from bulkio.bulkioInterface import BULKIO" . however above errors are occuerd without this import description.
My scd file's interface tags are:
<interfaces>
...............
<interface name="dataFloat" repid="IDL:BULKIO/dataFloat:1.0">
<inheritsinterface repid="IDL:BULKIO/ProvidesPortStatisticsProvider:1.0"/>
<inheritsinterface repid="IDL:BULKIO/updateSRI:1.0"/>
</interface>
<interface name="ProvidesPortStatisticsProvider" repid="IDL:BULKIO/ProvidesPortStatisticsProvider:1.0"/>
<interface name="updateSRI" repid="IDL:BULKIO/updateSRI:1.0"/>
<interface name="dataUlong" repid="IDL:BULKIO/dataUlong:1.0">
<inheritsinterface repid="IDL:BULKIO/ProvidesPortStatisticsProvider:1.0"/>
<inheritsinterface repid="IDL:BULKIO/updateSRI:1.0"/>
</interface>
</interfaces>
I think that included your pointed out.

Related

AZ Migrated server, DCOM error of VM Agent: unable to communicate with the computer .... using any of the configured protocols

Migrated a Win 2008 R2 VM from on premise to Azure. (via Azure SiteRecovery tool)
Now the VM Win Event spam every few seconds a:
DCOM was unable to communicate with the computer YTO231080216052 using any of the configured protocols.
The string: YTO231080216052 I found in the registry under the Azure Agent (same as Hyper V integration services):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters]
"HostName"="YTO231080216052"
"PhysicalHostName"="YTO231080216052"
"PhysicalHostNameFullyQualified"="YTO231080216052"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtual Machine\Guest]
"WireServerStatus"="Succeeded"
"GuestAgentVersion"="2.7.41491.1044"
"OsVersion"="Windows:Windows Server 2008 R2 Enterprise-Microsoft Windows NT 6.1.7601 Service Pack 1"
Full Event log XML
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 23/03/2022 11:06:04 AM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: myVM123
Description:
DCOM was unable to communicate with the computer YTO231080216052 using any of the configured protocols.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10009</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-03-23T17:06:04.000000000Z" />
<EventRecordID>82659</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>myVM123</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">YTO231080216052</Data>
<Binary>3C52656--removed--31363035327D3E</Binary>
</EventData>
</Event>
My Questions is how to solve this? Does the VM try to communicate (DCOM) with the host?
Notice in the device manger an unknown device:
VMBUS\{c376c1c3-d276-48d2-90a9-c04748072c60}
VMBUS\{c4e5e7d1-d748-4afc-979d-683167910a55}
MS claims "The unknown devices are harmless and can be safely ignored."
Does this related to the error message?

WebSphere v7.0 doesn't start CREATE_LISTENER_FAILED_4

I work with WebSphere v7.0. When I tried to start the server, I get the following error on the console.
[26/08/19 10:02:35:224 CEST] 00000000 WsServerImpl E WSVR0009E: Se ha producido un error durante el inicio
com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:439)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:502)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:341)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:867)
at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:605)
at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:157)
at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1303)
at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1690)
at org.omg.CORBA.ORB.init(ORB.java:364)
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:102)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:55)
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:432)
... 29 more
[26/08/19 10:02:35:135 CEST] 00000000 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvid
I checked the port BOOTSTRAP_ADDRESS in the file serverindex.xml
<specialEndpoints xmi:id="NamedEndPoint_1183122129640" endPointName="BOOTSTRAP_ADDRESS">
<endPoint xmi:id="EndPoint_1183122129640" host="F120000.cargas02.sir" port="2809"/>
</specialEndpoints>
The output command netstat -ano is
TCP 0.0.0.0:2809 0.0.0.0:0 LISTENING 4072
How can I fix this error?
Usually an ORB Listener Thread creation failure occurs because either:
Another process is already listening on the port in question (in this case 2809).
The ephemeral port range has been expanded on the OS such that the WebSphere server port ranges (2800 - ~10000) are now included in that range, increasing the possibility of a WAS server port number being assigned to another process as an ephemeral port.
For scenario #1: use netstat -ano or lsof -i :<port#> commands and search for the port to find the process using the port. If a conflicting process is found, change the config/port ussage of that process. Or edit the WebSphere serverindex.xml file in dmgr-profile-root/config/cells/cellName/nodes/nodename (make sure to take a backup beforehand). Change the 2809 port to another port not in use. Save and sync the changes.
For scenario #2: Check the ephemeral port range on the server box (internet search based on the OS will give specific instructions for this). Make sure the low end of the port range is sufficiently greater than the highest WebSphere server ports found in the serverindex.xml file.
Finally, it's also possible the WebSphere server did not properly shutdown and close all ports from its previous run. An OS reboot may be needed to release the port(s).

How to access an application deployed in tomcat via domain name in URL instead of IP

I installed tomcat 9.0.7 in my Linux Debian 9 machine. I want to access the application in the tomcat server via domain name.
For example: I want to use www.standoutjava.com/manager/html instead of localhost:8080/manager/html
I have changed my Connector setting in server.xml as follows so that I'm able to use the URL without port number.
<Connector port="80" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" address="0.0.0.0"/>
Now i can access the applications like localhost/manager/html or 192.168.40.29/manager/html
But its not enough I want to replace the IP portion with a certain domain name. So the URL will look like http://www.standoutjava.com/manager/html
I have changed my server.xml as follows.
GNU nano 2.7.4 File: server.xml
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
-->
<Connector port="80" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" address="0.0.0.0"/>
<!-- A "Connector" using the shared thread pool-->
<!--
<Connector executor="tomcatThreadPool"
port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
-->
<!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
This connector uses the NIO implementation. The default
SSLImplementation will depend on the presence of the APR/native
library and the useOpenSSL attribute of the
AprLifecycleListener.
Either JSSE or OpenSSL style configuration may be used regardless of
the SSLImplementation selected. JSSE style configuration is used below.
-->
<!--
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true">
<SSLHostConfig>
<Certificate certificateKeystoreFile="conf/localhost-rsa.jks"
type="RSA" />
</SSLHostConfig>
</Connector>
-->
<!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443 with HTTP/2
This connector uses the APR/native implementation which always uses
OpenSSL for TLS.
Either JSSE or OpenSSL style configuration may be used. OpenSSL style
-->
<!--
<Connector port="8443" protocol="org.apache.coyote.http11.Http11AprProtocol"
maxThreads="150" SSLEnabled="true" >
<UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
<SSLHostConfig>
<Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
certificateFile="conf/localhost-rsa-cert.pem"
certificateChainFile="conf/localhost-rsa-chain.pem"
type="RSA" />
</SSLHostConfig>
</Connector>
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host).
Documentation at /docs/config/engine.html -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
-->
<Engine name="Catalina" defaultHost="localhost">
<!--For clustering, please take a look at documentation at:
/docs/cluster-howto.html (simple how to)
/docs/config/cluster.html (reference documentation) -->
<!--
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
-->
<!-- Use the LockOutRealm to prevent attempts to guess user passwords
via a brute-force attack -->
<Realm className="org.apache.catalina.realm.LockOutRealm">
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
</Realm>
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
</Host>
<Host name="www.standoutjava.com" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- SingleSignOn valve, share authentication between web applications
Documentation at: /docs/config/valve.html -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all example.
Documentation at: /docs/config/valve.html
Note: The pattern used is equivalent to using pattern="common" -->
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="www.standoutjava.com_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
</Host>
</Engine>
</Service>
</Server>
Also I changed the hosts file (etc/hosts) in the machine as follows.
127.0.0.1 localhost
127.0.1.1 debian
192.168.40.29 www.standoutjava.com
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Now I'm able to access the URL as http://www.standoutjava.com/manager/html from the same computer where the tomcat get installed. But i can't access the URL from another computer in my network.
So what should i do to access the URL over the network?

jboss fuse 6.2.1 mq in fabric

i have jboss fuse 6.2.1 on linux server in a fabric mode with two child container. I created mq with this command
fabric:mq-create --group mur --assign-container risng1,risng2 --port tcp=61617 mur-broker
MQ profile mq-broker-mur.mur-broker ready
but i expect transport protocol will be configured with static port 61617 but it is dynamic.
In fuse 6.1 i modifed base template broker.xml
<transportConnector name="openwire" uri="tcp://0.0.0.0:${bindPort}"/>
bind port is configured in properties in profile. In fuse 6.2 does not work. My question is how to configured static port in fabric mode on jms broker?
I found closed issue https://issues.jboss.org/browse/FABRIC-1237
solved,
you can use custom template in your profile
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:amq="http://activemq.apache.org/schema/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
<!-- Allows us to use system properties and fabric as variables in this configuration file -->
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="properties">
<bean class="io.fabric8.mq.fabric.ConfigurationProperties"/>
</property>
</bean>
<broker xmlns="http://activemq.apache.org/schema/core" brokerName="${broker-name}" dataDirectory="${data}" start="false" restartAllowed="false">
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="true">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
<managementContext>
<managementContext createConnector="false"/>
</managementContext>
<persistenceAdapter>
<kahaDB directory="${data}/kahadb"/>
</persistenceAdapter>
<plugins>
<jaasAuthenticationPlugin configuration="karaf" />
</plugins>
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage percentOfJvmHeap="70"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="500 mb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="500 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<transportConnectors>
<transportConnector name="openwire" uri="tcp://${bindAddress}:61617"/>
</transportConnectors>
</broker>
</beans>
and the edit properties
group = mur
broker-name = mur-broker
connectors=openwire
kind = MasterSlave
data = ${runtime.data}mur-broker
config=profile\:broker-mur.xml
config.checksum=${checksum:profile\:broker-mur.xml}
standby.pool=default
bindAddress=0.0.0.0
bindPort=61617

NetworkConfiguration cause web roles to recycle

Adding NetworkConfiguration to ServiceConfiguration cause our web roles to recycle:
-Busy (Waiting for role to start... System startup tasks are running
-Restarting (Role has encountered an error and has stopped. System startup task failed with exit code -532462766
Without NetworkConfiguration everything runs ok. We need roles visibility to a SQL VM in the same azure virtual network (http://msdn.microsoft.com/en-us/library/azure/jj823135.aspx).
<NetworkConfiguration>
<Dns>
<DnsServers>
<DnsServer name="TestDNS" IPAddress="10.1.0.4" />
</DnsServers>
</Dns>
<VirtualNetworkSite name="TestNetWork" />
<AddressAssignments>
<InstanceAddress roleName="Role1">
<Subnets>
<Subnet name="TestSubnet" />
</Subnets>
</InstanceAddress>
<InstanceAddress roleName="Role2">
<Subnets>
<Subnet name="TestSubnet" />
</Subnets>
</InstanceAddress>
<InstanceAddress roleName="Role3">
<Subnets>
<Subnet name="TestSubnet" />
</Subnets>
</InstanceAddress>
</AddressAssignments>
</NetworkConfiguration>
Problem solved.
We have set an Affinity Group, and the Cloud Service within.
If you depend on a other service outside the Affinity Group (for ex storage, virtual network, cache, etc) the roles won't start.

Resources