Remote panels - Client Crashes Situation

Hello,
I would like to ask if someone can help me with the following situation.
I have an application which contains a top level VI and several other dialog VIs. This application can be accessed by a remote client via Remote Panels. From the top level VI (contains the menu - while loop and event structure) the client selects what he want to run. Then the front panel of his choice opens on his computer. It all runs ok.
However, if the client computer suddenly loses internet connectivity, then the Run Time Engine reports a plugin crash in the browser.
On the server side, all opened apps seem to freeze. I can turn them off one by one and then restart everything again.
Could anyone let me know how to approach this issue? I would like the client, in case a crash happens, to be able to reconnect to the application.
Thank you and have a nice day.
Solved!
Go to Solution.

Hello and thank you for the reply,
On the server side I am using Labview2011 with SP1, under WinXP.
On the client computer, Run Time Engine 2011, Chrome under WinXP.
The server is situated in a laboratory and it should work on its own, 24/7, without my intervention for taking control of the app.
So now, I have considered the scenario when a client connects to the application, starts running it and after a while he will use the Windows Task Manager to end the application, without considering the normal options which are available in the menu. In this case, in the browser I would get Image1. Basically the client will have to connect again to the server. On the server side, I have inserted a state where I check to see if there are any remote clients connected to my application. If no client are connected, then it closes. So as the client kills the task, imediatelly my server stops the application. So this is solved and works fine.
The second scenario is when a client does not close the application even when his time allocation has reached 0 minutes. Again, the server checks this time limit and it closes the client connection. For this, I have used in a case, the code presented as Image2. If this situation occurs, the client is disconnected and he
gets the Image 3 message on the browser. This error appears twice and each time the client presses Continue. In the end the server takes control and it is all ok.
However, what might cause this error? Is there a chance to fix it? I couldn't find any reference to it and the Remote Panels.
Thank you and have a nice day.
Attachments:
IMAGE1.jpg ‏38 KB
IMAGE2.jpg ‏75 KB
IMAGE3.jpg ‏62 KB

Similar Messages

Remote Panel & client-server model

Hii..
I am working on image processing. I have developed a VI and web published it, It was working well. But, I was unable to give my own input image from remote panel. I can give various inputs which are kept in library only. But, I could not upload my own input image.
For that purpose, i created Client- Server model. This is not web publishing. Client VI will have same front panel as Server VI. Using this model, i can give my own input image. Whatever input and controls in Client VI will be sent to server VI using shared variable. I tested it on LAN connection, it was working well.
But, when I run through internet, it became very slow...... There may be two reasons 1. Bandwidth for our public IP is less and 2. slow internet connection..
Are there any other ways to speed up the Client-Server model.............
As compared to remote panel, Client-Server model on internet is very slow.......
Give me ur suggestions, ideas to speed up this model..
thanks
Prashh

Hola
Si puedes monitorear/controlar un ejecutable en remoto.
Te adjunto algunos enlaces del foro de NI sobre la materia.
You need start the web server to have access at your executable, see below links with information about this :
http://digital.ni.com/public.nsf/websearch/862567530005F09C862567710044C3E2?OpenDocument
http://digital.ni.com/public.nsf/websearch/862567530005F09C8025673000529121?OpenDocument
http://digital.ni.com/public.nsf/websearch/3B2160B128EE09A886256B60006FFA66?OpenDocument
http://digital.ni.com/public.nsf/websearch/A2A5ACDEEFA448E686256D9800629227?OpenDocument
Saludos
Alipio
"Qod natura non dat, Salmantica non praestat"

Why do remote panel server crash/stop when subvi call is done

My application crash/stops when I tries to call a subvi with remotepanel. The application isn't hevy so I can't understand why. Tried it on several computer with same result. Use Lv8.0
Grateful for some feedback on this.

Patience you have already started a new thread. Please dont dig old threads and that too unanswered ones....

Open url in a remote panel

HI.
I want to put a button that launch a webpage. I works fine locally, when I click OK button, a new internet window browser is open with the URL.
But if I take the control in other PC client (using Web Publishing Tool) and I click OK button a internte window browser is open in THE HOST. I want to open the new window in the Client.
Thanks.
I attach the VI (open_google.vi) and the HTML file created by WPT (test.txt)
Raymundo Cassani
Attachments:
open_google.vi ‏11 KB
test.txt ‏2 KB

Hello,
When you view or control a VI using Remote Panels that VI is executing on the host side. The VI will not be able to interact with the operating system on a remote panel client. This means that it will not be possible to use this approach to open a browser window on the client side.
You could take another approach- at least the way I would do it is thusly:
Instead of putting the button that launches the page in the VI you could put it in the html file that the remote panel is hosted in.
Using javascript you could pop up a new browser window with the URL you need.
If you need to control what URL is viewed from within the VI you could make the button point to a URL that will be handled by your VI that can redirect to the URL you need. This would be easy to do in 8.6 as you could simply export the VI as a web service. Pre-8.6 you would either have to use the G web server or build a minimal web server yourself (this would be easier than it sounds since the server would have to do nothing but redirect).
I should add that this approach would require some knowledge of HTTP/HTML/JavaScript.
Let me know how it goes.
Nathan
Message Edited by NathanK on 10-15-2008 11:07 AM

Why crashes LV 8.0.1 when opening remote panel

Hi everybody,
everytime I try to open a remote panel to my vi from another VI Labview (remote client) crashes completely. It worked fine with LV 8.0 but not with LV 8.0.1 on a linux machine (Suse 10.0). When I try to open the panel in a browser it says that the run time engine is missing. But installing the rte doesn't work because the script says it's already installed. There is no difference if I try it locally or on a remote machine, both running LV 8.0.1 on Suse linux 10.0.
I'd appreciate any tip, thanks
Clemens

Hi Robert,
I just gave up using Lv 8.0.1 because I had nothing but problems with it and the original problem I instellad it for wasn't solved and in the meantime I was told I had to live with it. The strange thing with the RTE was that it worked with some vi's but not with all. But it worked with all vi's usting LV 80. The migration form LV 7.1 to 8.xx took so much time that I'll stay as long as possible with it ignoring all further updates.
Regards Clemens

Labview Remote Panel and Client Aspect Ratio

Dear all professionals,
I had create an application with remote panel (webserver) enabled. I found that there is relationship between aspect ratio of client device display and the remote panel screen size. Here i attached two images of remote panel in browser which both remote panel are opened using different aspect ratio of client device.
The left 1 is the device with 1.5 aspect ratio while the right 1 is the device with 1.78 aspect ratio.
As you can seen from the images, both remote panel are shown in different size. May i ask do i miss something in the remote panel configuration?

Hi Michel,
Thank you for your reply. I also notice that the zoom % of browser is one of the issue that caused this behaviour. In the same aspect ratio with server computer( where the application running), changing zoom to 100% will help to fit remote panel that I already set when I developing the remote panel vi. But if for different aspect ratio, no matter how u change the zoom % , it won't fit the frame. I just wondering whether got another solution for this issue or not :-(

Since the Remote desktop client update 3.8.2 V1.1 my Indesign CS4 crashes when I try to print. Does anyone else have this problem?

Problem with remote desktop client update

I find it interesting that since Screen Sharing is available, and works "just fine" that a Remote Desktop Client would be needed to be installed.
I installed it, but I'm not sure why.
I found the updated application in /System/Library/Core Services/RemoteManagement/ARDAgent
Which is also where the screen sharing and vnc bundles live. I clicked on it to see what would happen -- nothing.
I found these ports in another discussion
TCP and UDP port 3283
TCP and UDP port 5900. (Also used for Screen Sharing in OSX 10.5 and later)
port 22
This page confirms their use along with the use of other ports:
TCP and UDP ports used by Apple software products - Apple Support
Additionally TCP port 5432 is used by ARD
Having recently noticed (through "network utility" that my computers have had a "ton" of open connections.
This severely hurt system performance.
I note that neither my Airport Express nor my Mac can set up a firewall on these ports.
While I haven't noticed the ARD ports being used, I cannot help but wonder if this is set up for a CIA/NSA backdoor into my computers.
On a less paranoid level, perhaps Apple is planning on adding on-line help to debug our problems in "real-time". ;-)

Downloading remote panels

I am working on an application suited to work with Remote Panels. Its total size according to the VI Properties is about 2 Mb. From what I read in "LabVIEW User Manual" I thought that when I loaded the VI from the remote client only the Front Panel would be sent (200 Kb aproximately in this case). However the slider that appears in the client informing the bytes remainding to complete the download indicates 2 Mb total instead of 200 Kb, just as if all the components of the VI (Front Panel, Diagram Block, Code and Data) were sent. Does anyone know what is happening?
Thanks in advance,
spj

Ok thanks for the reply. I thought I had isolated the issue as being only when closing the browser before releasing control did it crash. But after trying it a few more times, eventually it crashes even if control is released first. To be clear, it seems perfectly stable while operating, but rather *after* disconnecting, closing browser, then when trying to reconnect, the front panel will come up for a second or two, then the server Labview crashes. Also it seems if I leave the LV application running too long (a few min.?) I can't connect to it. So I have to make a client connection early on for it to work. It might be network related? I think the client PC is on a VPN and the server isn't but I'm not sure.
I looked at Web services but that seems like a lot of development when all I need is to see the front panel remotely.

Large(ish) Remote Panel Applications?

I'm just wondering if anyone has had any luck developing Medium to Large scale remote panel applications and would be willing to share their experiences.
I ask because I'm in the process of developing an application that I intend to be deployed remotely, and have already run in to two major bugs (that got sent to NI R&D) requiring workarounds, and one plugin (the LAVA GUI plugin) that just causes LabVIEW on the client computer to hard crash... and I'm 30% done with the application. At this point in time, I am seriously considering bailing on the remote panels and trying to come up with an alternate way to deploy the app.
Thoughts?

You could access the remote application via VI Server. This is a little higher level access than TCP/IP and wouldn't constrain your interface to what you happen to have running on the remote computer.
This may be just me, but I don't think I would want to be running to a remote location because the GUI for my local system needed to change.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How can I disable messages generated by Remote Panel?

I created an application (EXE) to server its panel to other network clients.
I used the Tools > Web Publishing Tool to generate a HTML code to create two different web pages to access this application using Web server:
- Embedded (for some users who need visualize the panel in real time).
- Monitor (to display panel snapshots to users updated every 1 second).
I don't need anyone controlling the remote panel, so I used this option:
Tools > Options > Web Server: Browser Access and checked Allow Viewing (not controlling) for every client connected.
Ok, both are working fine. But it a user try to Request control of VI on the Embedded page (right click in the remote panel), the application running in the server displays a message: Denied control request from XXX: Check permissions.
The embedded page stills working fine, but in the Monitor page that message appears in a box (see attached picture below)..
Is there a way to disable all messages in the remote panel? I realized that I need to access the computer where the application EXE is running to close the message.
I'm thinking in two solutions:
- Unable the right click menu in the embedded page to avoid clients request control of the remote panel.
- Run a code in the application to erase messages generated.
Has anyone an idea how to solve this?
Thanks in advance,
Klein
Message Edited by Klein on 08-06-2008 12:54 PM
Attachments:
Remote Panel message.jpg ‏10 KB

Hi Dpcamargo,
I'm already using monitor with a delay of 1 second and this doesn't seems real time like remote panel visualization.
But you sent me a good tip: use java code to cancel right clicks at all....
I will try this solution.
Hey, we are both brazilians! So, thank you so much, Dpcamargo.

Remote panel and selective control access through Security with DSC

Hi Everyone,
I looked around to see what labview had to offer concerning security of remote panel and all the solutions I've found only propose full access to a remote panel, or none. The login page is not an option for me as everyone on the intranet can access the remote panel for monitoring but not everyone can have control to the buttons on it.
With the DSC module, I can give securities to the different controls and it works great with the exe, if I log in or out, the controls appears or disapears. Unfortunately, with remote panels, those controls are always visibles. Furthermore, when I log in from a remote panel, all the other remote panels get logged in with the same username and priviledges. When I log out, same thing, it logs out all the other remote panels. So the last guy who logs in gives its priviledges to every one else who is monitoring the remote panel at that time. when he logs out, he logs everyone out. I used a reentrant vi hoping that this would solve the problem but it didnt.
I would like to do what my colleague does with Advantech without any problem. He has only 1 .exe is running on the server and whoever connects to it through webserver, just needs to log in and he has all the priviledges of an guest, operator, admin, etc.. with access to controls and features accordingly. All this without interfering with the other people using the remote panels. This colleague has always been doubtful about the capabilities of labview to do SCADA systems and uptil now, I've been able to prove him wrong.. please help me continue
There are workarounds, using remote desktop to the server instead of webserver but it definitely is not as practical for the client and it will need quite some work to to synchronise all the exes open from the differents sessions, through the use of shared variables, binding and securities.
Thank you for your help.
Solved!
Go to Solution.

Thank you very much for your reply Jordan.
The NI security info is on the server (local domain with groups and users), and the running exes as well. The remote panel is not supposed to be accessed by internet, at least not yet, but just by the computers on the network and thinkline computers who are directly connected to the servers. the remote panel is accessed through the simple url: http://serverip/Application.html
There is no problem with accessing the remote panel of the exes on the server from another computer on the network. But there are several security issues when logging in and out with the NI Security Programmatic Login and logout VIs through the remote panel..
The 1st problem occurs when several people access the remote panel at the same time. In my setup, everyone is allowed to check what's happening on the front panel of the running exe, go through the tabs, check the graphs, the tables, etc.. , but only the administrators and the operators can send commands to the machines and the production line through this remote panel. Hence some buttons are accessible to all users, while others are only accessible depending on the privileges of the person logged in.
So like I said in the 1st post, I configured some buttons to be accessible only by the users of the admin group. When the exe runs, it's perfect, if I log in and out with an admin account, the buttons appears and disappear accordingly. But when I check the remote panel, those admin buttons are always visible, even if I am logged in as a guest or even logged out. Is it because the remote panel only needs minimum runtime engine and doesnt use the dsc runtime engine? if so, any work around?
Furthermore, another big problem is that if I login as an admin in one remote panel, then login as an guest in another remote panel, and then logout back from the first remote panel, it says: "User Domain/Guest logged out". Hence, my second login logged out my first user. I can actually see the admin buttons appearing and disappearing on the exe when login as admin and guest from the different remote panels.
So that's it, I would like my remote panel to behave like a normal scada system, with one exe running in the back (on the server) and with all the users accessing it through web server. Several users might/will access the remote panel at the same time and each of the users have a login/password that grant some of them the privileges to take some actions while giving the others only monitoring rights.
I hope that I have been more clear in this 2nd post,
Thank you again for your time.
Best Regards,
Tom.

Detect remote panel connections?

Is there a way for my VI to 'detect' when someone has connected to it with a Remote Panel and requested control?
I have an issue (due to the size/complexity of my VI I'm sure) that when a RP gains control, after a period of time, the main VI begins to slow down and starts to lose data (it's coming from a TCP connection)!
I'd like to be able to see when a RP gains control, and automatically log them off after a period of time (5 min?). I know that there is a connection time-out on the web publishing page, but it appears to only come into play if 1 RP has control and another requests it. I need to be able to limit the control time of a single RP.
Solved!
Go to Solution.

Cory,
Well, it almost worked...
I'm attaching my little test program 'RP Control.vi'. I've compiled this into an executable that's in my server path, so I can get to it from my laptop (on my network). When I run it from my server, I can press my 'Start' button and nothing happens--no client RP's are connected, so this is as expected.
When I connect via my laptop to the server, my laptop is now the remote client, but it's hasn't requested control -- again, nothing happens when I press my 'Start' button.
When the laptop requests control of the VI, and I press the 'Start' button from the laptop, I see all my data fields filled in, and I show my calculated 'End Time?' which is 1 minute after the laptop got control.
I can then keep pressing my 'Start' button, and see the 'Time Now' update, and when 1 minute elapses, I see my 'Close' LED turn on, indicating I should have activated the 'Close Connection To Client'.
However, the laptop still has control of the VI...it hasn't returned to the server.
Any suggestions as to what I may be doing wrong, or does the 'Close Connection To Client' work differently?
<edited>
Looking at the Method - 'RP.Close Connection To Client' does this return control of the VI to the server copy (which is what I want to do), or does it try to completely disconnect the Remote Panel (which is not what I'm looking for)?
Message Edited by Steve257 on 09-17-2009 02:47 PM
Attachments:
RP Control.vi ‏22 KB

How to Detect LV runtime engine prior to showing Remote panel in browser?

I work on a web server that delivers remote panels embedded in browser windows. On new machines, the labview runtime engine needs to be downloaded and installed.
Currently, when a new user 'hits' the remote panel, the user is prompted and then downloads the component. However, the user experiences some errors that can be confusing. The first time, the remote panel is not embedded properly and the user must go 'BACK' then reload the page.
We would like to check and detect whether the LVRT engine is installed prior to posting a webpage that contains a remote panel.
What is the best way to detect whether the LVRT engine is installed on a remote computer?
Jim West

Jim West wrote:
My brain is swimming... I haven't had enough coffee this morning... There is a chicken and egg issue. As soon as I post the page, the client knows it needs to install the Labview runtime engine. However, my Labview process has already attempted to place the remote panel in the page. I get an error. I'll admit that I haven't delved into my software since there are two spawned processes involved. One process responds to the request and another lingers in memory running the remote panel until the user finishes.
From my perspective my lingering process should be sufficient to get the remote panel displayed when the RTE in finished installing but here is the catch. Installing the RTE requires a reboot, therefore the server process would need to linger in memory a long time and then would need to recoginize that a user from the same computer and login is looking for the page. Not really the way to go. I can't have a process on the server lingering waiting for a user to reboot his computer and then do something when they start running again. That process needs to die right away if the RTE is not available.
Jim
Would it be possible for this lingering process to check to see if the web server read has timed out? The default is 60 seconds, and you can change it by going to Tools>>Options>>Web Server: Configuration.
Trey B
Applications Engineering
National Instruments

IPad Air + iOS 8 GM -- RD Client Crash

Hello, I am an iOS Developer and I'm running into an issue with the iPad Air + iOS 8 and the iPad's Microsoft RD Client.
Whenever I click the "+" in the upper-right hand corner, and click "Add PC or Server" the client crashes.
iPad Information:
Device: iPad Air (A1474)
Model: MD788LL/A
Version: 8.0 (12A365)
The remote desktop information:
Version: 8.1.0.140902.3.0
Here's the crash log generated from from Xcode:
Incident Identifier: 40933394-D6A7-4EF4-8354-9C26690AB5B7
CrashReporter Key: 57246288c66b4cff81780eb31982d743c09097a8
Hardware Model: iPad4,1
Process: Microsoft Remote Desktop [582]
Path: /private/var/mobile/Containers/Bundle/Application/BCA3CEAD-6A01-4D3E-B0C6-D201BCF7EEC8/Microsoft Remote Desktop.app/Microsoft Remote Desktop
Identifier: com.microsoft.rdc.ios
Version: 8.1.0 (8.1.0)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2014-09-12 08:16:25.257 -0700
Launch Time: 2014-09-12 08:16:22.224 -0700
OS Version: iOS 8.0 (12A365)
Report Version: 105
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Last Exception Backtrace:
0 CoreFoundation
0x29014e3f __exceptionPreprocess + 127
1 libobjc.A.dylib
0x36989c8b objc_exception_throw + 38
2 CoreFoundation
0x29014d85 +[NSException raise:format:] + 112
3 UIKit
0x2c6e3cbd -[UIPopoverController dealloc] + 156
4 libobjc.A.dylib
0x369a3d5f objc_object::sidetable_release(bool) + 166
5 Microsoft Remote Desktop
0x00110429 0xc7000 + 300073
6 UIKit
0x2c5c87c7 -[UITableView _selectRowAtIndexPath:animated:scrollnbsp; UIKit
0x2c67a0df -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 194
8 UIKit
0x2c52c1bd _applyBlockToCFArrayCopiedToStack + 308
9 UIKit
0x2c4a810b _afterCACommitHandler + 458
10 CoreFoundation
0x28fdb5cd __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 20
11 CoreFoundation
0x28fd8c8b __CFRunLoopDoObservers + 278
12 CoreFoundation
0x28fd9093 __CFRunLoopRun + 914
13 CoreFoundation
0x28f27621 CFRunLoopRunSpecific + 476
14 CoreFoundation
0x28f27433 CFRunLoopRunInMode + 106
15 GraphicsServices
0x3026c0a9 GSEventRunModal + 136
16 UIKit
0x2c511809 UIApplicationMain + 1440
17 Microsoft Remote Desktop
0x000d2f73 0xc7000 + 49011
18 libdyld.dylib
0x36f09aaf start + 2
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib
0x36fcfdfc __pthread_kill + 8
1 libsystem_pthread.dylib
0x3704dd33 pthread_kill + 59
2 libsystem_c.dylib
0x36f6f905 abort + 73
3 libc++abi.dylib
0x362ad9c5 abort_message + 85
4 libc++abi.dylib
0x362c766d default_terminate_handler() + 265
5 libobjc.A.dylib
0x36989f23 _objc_terminate() + 191
6 libc++abi.dylib
0x362c4de1 std::__terminate(void (*)()) + 77
7 libc++abi.dylib
0x362c48ab __cxa_rethrow + 99
8 libobjc.A.dylib
0x36989dcf objc_exception_rethrow + 39
9 CoreFoundation
0x28f276b9 CFRunLoopRunSpecific + 629
10 CoreFoundation
0x28f2742f CFRunLoopRunInMode + 103
11 GraphicsServices
0x3026c0a5 GSEventRunModal + 133
12 UIKit
0x2c511805 UIApplicationMain + 1437
13 Microsoft Remote Desktop
0x000d2f6f 0xc7000 + 49007
14 libdyld.dylib
0x36f09aad start + 1
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib
0x36fbc2a0 kevent64 + 24
1 libdispatch.dylib
0x36ef59fd _dispatch_mgr_invoke + 277
2 libdispatch.dylib
0x36eeb31f _dispatch_mgr_thread + 35
Thread 2:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 3:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 4:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 5:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 6:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 7:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 0 crashed with ARM Thread State (32-bit):
r0: 0x00000000 r1: 0x00000000 r2: 0x00000000 r3: 0x00000003
r4: 0x00000006 r5: 0x394189dc r6: 0x39404840 r7: 0x00e843b8
r8: 0x146dc430 r9: 0x00000000 r10: 0x39403074 r11: 0x146dc454
ip: 0x00000148 sp: 0x00e843ac lr: 0x3704dd37 pc: 0x36fcfdfc
cpsr: 0x00000010
Binary Images:
0xc7000 - 0x6a2fff Microsoft Remote Desktop armv7 <b852e7357e0131f6b64799903120ca37> /var/mobile/Containers/Bundle/Application/BCA3CEAD-6A01-4D3E-B0C6-D201BCF7EEC8/Microsoft Remote Desktop.app/Microsoft Remote Desktop
0x1fe34000 - 0x1fe57fff dyld armv7s <fd3fef9c43c9382e8e46d5d59fb52f86> /usr/lib/dyld
0x27ab3000 - 0x27c1ffff AVFoundation armv7s <291c7a621b65396491697e7a7f728b16> /System/Library/Frameworks/AVFoundation.framework/AVFoundation
0x27c20000 - 0x27c7efff libAVFAudio.dylib armv7s <1b452a7a75513cf9aa82e59feb7eef33> /System/Library/Frameworks/AVFoundation.framework/libAVFAudio.dylib
0x27cb8000 - 0x27cb8fff Accelerate armv7s <3b40c742a7323214a5eb836630536bd1> /System/Library/Frameworks/Accelerate.framework/Accelerate
0x27cc9000 - 0x27ee4fff vImage armv7s <844c5a129a2f3dbe9c0b23824f3254f6> /System/Library/Frameworks/Accelerate.framework/Frameworks/vImage.framework/vImage
0x27ee5000 - 0x27fcbfff libBLAS.dylib armv7s <aaaefc0f51f23049871f65ea9c4c7151> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libBLAS.dylib
0x27fcc000 - 0x28290fff libLAPACK.dylib armv7s <ba74aac653423b3b9bae4122d84935d8> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libLAPACK.dylib
0x28291000 - 0x282a2fff libLinearAlgebra.dylib armv7s <3df96b6a86303adea6abea68b7b610ac> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libLinearAlgebra.dylib
0x282a3000 - 0x2831ffff libvDSP.dylib armv7s <fb3e0b030cc5346c89af71af2d17bc27> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libvDSP.dylib
0x28320000 - 0x28332fff libvMisc.dylib armv7s <abd4670b295c3f50a2658d0f3f86d78c> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libvMisc.dylib
0x28333000 - 0x28333fff vecLib armv7s <9495c9829e28344fb1820d2140fcaf35> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/vecLib
0x28334000 - 0x2835afff Accounts armv7s <cf7ceabb9af233f0b657f23423988703> /System/Library/Frameworks/Accounts.framework/Accounts
0x2835c000 - 0x283ccfff AddressBook armv7s <eeeabdf6b9703b4f846b672d0bb50eeb> /System/Library/Frameworks/AddressBook.framework/AddressBook
0x283cd000 - 0x284f1fff AddressBookUI armv7s <6fe5557b059b3ff38179c43183cfe8c3> /System/Library/Frameworks/AddressBookUI.framework/AddressBookUI
0x28689000 - 0x288fcfff AudioToolbox armv7s <5cf7594c3e8e33a889f26f9d2b8f74b7> /System/Library/Frameworks/AudioToolbox.framework/AudioToolbox
0x28a64000 - 0x28bebfff CFNetwork armv7s <79b211df401f377fb05acc07a57db3ea> /System/Library/Frameworks/CFNetwork.framework/CFNetwork
0x28bec000 - 0x28c6cfff CloudKit armv7s <aa1d623f3be434a6a75d2e49b41d26b6> /System/Library/Frameworks/CloudKit.framework/CloudKit
0x28c6d000 - 0x28cccfff CoreAudio armv7s <5b3129e5e3c23c4fb1052346c18e63b9> /System/Library/Frameworks/CoreAudio.framework/CoreAudio
0x28ce5000 - 0x28d02fff CoreBluetooth armv7s <2040fbe8e91833e5a14c2e4961b5995b> /System/Library/Frameworks/CoreBluetooth.framework/CoreBluetooth
0x28d03000 - 0x28f0efff CoreData armv7s <db7e2287362438249bb753788c64a2b1> /System/Library/Frameworks/CoreData.framework/CoreData
0x28f0f000 - 0x2923bfff CoreFoundation armv7s <a76fd43513ee3af9af444082a92ad639> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x2923c000 - 0x29366fff CoreGraphics armv7s <a3d08c6b246236fd9a078619f6c2010b> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x293a6000 - 0x293a8fff libCGXType.A.dylib armv7s <8c8f282d69573460983d78cbaebfd8cf> /System/Library/Frameworks/CoreGraphics.framework/Resources/libCGXType.A.dylib
0x293a9000 - 0x293b3fff libCMSBuiltin.A.dylib armv7s <795fcab613223b6d833937453beb1048> /System/Library/Frameworks/CoreGraphics.framework/Resources/libCMSBuiltin.A.dylib
0x2959b000 - 0x295b6fff libRIP.A.dylib armv7s <ae6bf33909b531b6abae4b007d9dd46b> /System/Library/Frameworks/CoreGraphics.framework/Resources/libRIP.A.dylib
0x295b7000 - 0x296c5fff CoreImage armv7s <0dd5152defdf3200b22c29876b05e34b> /System/Library/Frameworks/CoreImage.framework/CoreImage
0x296c6000 - 0x2971dfff CoreLocation armv7s <1153f2e6bde036f4b611833aa85dd9ac> /System/Library/Frameworks/CoreLocation.framework/CoreLocation
0x2974f000 - 0x297e9fff CoreMedia armv7s <b3e1c2a8262b38a697b5fd5478376e97> /System/Library/Frameworks/CoreMedia.framework/CoreMedia
0x297ea000 - 0x298aafff CoreMotion armv7s <0e91543dde123205bbfb0eec336f82e4> /System/Library/Frameworks/CoreMotion.framework/CoreMotion
0x298ab000 - 0x29909fff CoreTelephony armv7s <32757860a7b23ee6b10cdfb2bcb5e5b9> /System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x2990a000 - 0x299d1fff CoreText armv7s <4be50da4f4d13b59b32ca55d4660e5c5> /System/Library/Frameworks/CoreText.framework/CoreText
0x299d2000 - 0x299e7fff CoreVideo armv7s <b1d41cec8ddc3c27be6f5459e17f1d2d> /System/Library/Frameworks/CoreVideo.framework/CoreVideo
0x299e8000 - 0x29addfff EventKit armv7s <af7bcad4baa7326eb020d805b49df854> /System/Library/Frameworks/EventKit.framework/EventKit
0x29c53000 - 0x29e55fff Foundation armv7s <fadfe1d878803b27a0683288c1c7948b> /System/Library/Frameworks/Foundation.framework/Foundation
0x29e82000 - 0x29ea1fff GSS armv7s <a384f737744b3e67be4b006612b27b58> /System/Library/Frameworks/GSS.framework/GSS
0x29f35000 - 0x29f8bfff IOKit armv7s <df1bb671b5d5392cbb95b89ed6341e78> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x29f8c000 - 0x2a1cdfff ImageIO armv7s <5cd6989e5626302aa49787b87e78ce32> /System/Library/Frameworks/ImageIO.framework/ImageIO
0x2a1ce000 - 0x2a51cfff JavaScriptCore armv7s <0041abdf36ff318981798e691a194dda> /System/Library/Frameworks/JavaScriptCore.framework/JavaScriptCore
0x2a7ef000 - 0x2a7f7fff MediaAccessibility armv7s <5c1cbb4f664b3d049bc5c0ac98cb8a90> /System/Library/Frameworks/MediaAccessibility.framework/MediaAccessibility
0x2a7f8000 - 0x2a9d1fff MediaPlayer armv7s <2fbb4a5dc62938f999bd72c93b9f5a50> /System/Library/Frameworks/MediaPlayer.framework/MediaPlayer
0x2a9d2000 - 0x2ad49fff MediaToolbox armv7s <47c440c3064b3b9194c8ffe6a096c37c> /System/Library/Frameworks/MediaToolbox.framework/MediaToolbox
0x2ad4a000 - 0x2ae08fff MessageUI armv7s <6c45faa0e6fe34d399021095392d0f63> /System/Library/Frameworks/MessageUI.framework/MessageUI
0x2ae09000 - 0x2ae75fff Metal armv7s <2c1c274d748d330c81520ccdf07a8be1> /System/Library/Frameworks/Metal.framework/Metal
0x2ae76000 - 0x2af05fff MobileCoreServices armv7s <5e571169affe3b1f97863142d3438da5> /System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x2b9e0000 - 0x2b9e8fff OpenGLES armv7s <b0df2c3e1d583413b2babe8e95a7e099> /System/Library/Frameworks/OpenGLES.framework/OpenGLES
0x2b9ea000 - 0x2b9eafff libCVMSPluginSupport.dylib armv7s <ab28723da4e234fd87a6e12dae52c3a2> /System/Library/Frameworks/OpenGLES.framework/libCVMSPluginSupport.dylib
0x2b9eb000 - 0x2b9edfff libCoreFSCache.dylib armv7s <f073564b5746376a945531dcb28ebdb9> /System/Library/Frameworks/OpenGLES.framework/libCoreFSCache.dylib
0x2b9ee000 - 0x2b9f1fff libCoreVMClient.dylib armv7s <70abd418d5523929a02f9f22f834962e> /System/Library/Frameworks/OpenGLES.framework/libCoreVMClient.dylib
0x2b9f2000 - 0x2b9fafff libGFXShared.dylib armv7s <2cbde78e8e6c3d9da3a7271b053294bc> /System/Library/Frameworks/OpenGLES.framework/libGFXShared.dylib
0x2b9fb000 - 0x2ba3dfff libGLImage.dylib armv7s <a418f2754f373d3395a6aad59e50c371> /System/Library/Frameworks/OpenGLES.framework/libGLImage.dylib
0x2becb000 - 0x2c01dfff QuartzCore armv7s <4a753d93b6033495b66178dd7535fd96> /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x2c01e000 - 0x2c071fff QuickLook armv7s <593a3c45e1693456bfc917526490e399> /System/Library/Frameworks/QuickLook.framework/QuickLook
0x2c260000 - 0x2c2a0fff Security armv7s <52c6a10cc12c33cda98ce09e002c6a35> /System/Library/Frameworks/Security.framework/Security
0x2c444000 - 0x2c4a0fff SystemConfiguration armv7s <0dfa14680b583dd2994e2cc0563ebd53> /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x2c4a3000 - 0x2cd3bfff UIKit armv7s <5e0a38c7a0a33afc9e0e51edbdc2e8f3> /System/Library/Frameworks/UIKit.framework/UIKit
0x2cd3c000 - 0x2cda3fff VideoToolbox armv7s <d19c7c7e97533cde961652039bbcc310> /System/Library/Frameworks/VideoToolbox.framework/VideoToolbox
0x2cda4000 - 0x2cf89fff WebKit armv7s <4e6d38f557ea3c2cb906c580d58723d5> /System/Library/Frameworks/WebKit.framework/WebKit
0x2d23a000 - 0x2d245fff AOSNotification armv7s <30ac6892bcf1347383b6ca73b0c447be> /System/Library/PrivateFrameworks/AOSNotification.framework/AOSNotification
0x2d39a000 - 0x2d3e6fff AccountsDaemon armv7s <440e21ee4a4e3ee9b1891b016268b59e> /System/Library/PrivateFrameworks/AccountsDaemon.framework/AccountsDaemon
0x2d3e7000 - 0x2d408fff AccountsUI armv7s <a85ce8aa63ef349f90b9fbf16a040a6e> /System/Library/PrivateFrameworks/AccountsUI.framework/AccountsUI
0x2d409000 - 0x2d40dfff AggregateDictionary armv7s <7cb2e7f3daac30dbba7a9cf452850eb8> /System/Library/PrivateFrameworks/AggregateDictionary.framework/AggregateDictionary
0x2d5d6000 - 0x2d601fff AirPlaySupport armv7s <10dd1721d0ac327f8f8714bb749de10a> /System/Library/PrivateFrameworks/AirPlaySupport.framework/AirPlaySupport
0x2d7fb000 - 0x2d839fff AppSupport armv7s <85ae995cc0083b8f861e9af66f426b8b> /System/Library/PrivateFrameworks/AppSupport.framework/AppSupport
0x2d83a000 - 0x2d880fff AppleAccount armv7s <c8d7c7cc33873ca184d666626d1e2e49> /System/Library/PrivateFrameworks/AppleAccount.framework/AppleAccount
0x2d968000 - 0x2d9a5fff AppleJPEG armv7s <9d28d8b8c27e3b4d9af820fe71478279> /System/Library/PrivateFrameworks/AppleJPEG.framework/AppleJPEG
0x2d9b0000 - 0x2d9c2fff ApplePushService armv7s <9019b7f0259b32e2bf08eb9e3e61b315> /System/Library/PrivateFrameworks/ApplePushService.framework/ApplePushService
0x2d9c3000 - 0x2d9c9fff AppleSRP armv7s <2bc7687cb4ea3b258e7412e03765e14c> /System/Library/PrivateFrameworks/AppleSRP.framework/AppleSRP
0x2d9fe000 - 0x2da07fff AssertionServices armv7s <5a349cdba4e63bb6a4d15bb6ed3266af> /System/Library/PrivateFrameworks/AssertionServices.framework/AssertionServices
0x2da08000 - 0x2da20fff AssetsLibraryServices armv7s <7419fc839e043757a22253d762c0a6fc> /System/Library/PrivateFrameworks/AssetsLibraryServices.framework/AssetsLibraryServices
0x2da21000 - 0x2da45fff AssistantServices armv7s <c1333e5e6c663276bc90f9a951c01cf8> /System/Library/PrivateFrameworks/AssistantServices.framework/AssistantServices
0x2da74000 - 0x2da78fff BTLEAudioController armv7s <2dcdae1d597e3f0fbf940c6df8a8ef27> /System/Library/PrivateFrameworks/BTLEAudioController.framework/BTLEAudioController
0x2da79000 - 0x2da90fff BackBoardServices armv7s <ffee59ef60f9330a9bdb28d8741b1b02> /System/Library/PrivateFrameworks/BackBoardServices.framework/BackBoardServices
0x2da93000 - 0x2dac8fff BaseBoard armv7s <f0482a734fba3477bd24881eb35f8dbe> /System/Library/PrivateFrameworks/BaseBoard.framework/BaseBoard
0x2dac9000 - 0x2dacffff BluetoothManager armv7s <fc99330ba35934c1b14610b4d86b7471> /System/Library/PrivateFrameworks/BluetoothManager.framework/BluetoothManager
0x2dad0000 - 0x2daf6fff Bom armv7s <554f954a2ece30fbbb343a1ad991af68> /System/Library/PrivateFrameworks/Bom.framework/Bom
0x2dbc1000 - 0x2dbeafff CalendarFoundation armv7s <6664e18ccf0d3b509037b2aa3e957b25> /System/Library/PrivateFrameworks/CalendarFoundation.framework/CalendarFoundation
0x2dcf6000 - 0x2dcfefff CaptiveNetwork armv7s <9a9f451fee273d698cb4497668b931a8> /System/Library/PrivateFrameworks/CaptiveNetwork.framework/CaptiveNetwork
0x2dcff000 - 0x2de21fff Celestial armv7s <00f08339e5a53f9c954529a1f5b2e124> /System/Library/PrivateFrameworks/Celestial.framework/Celestial
0x2de2f000 - 0x2de47fff CertInfo armv7s <cae40259896d3df8a24ef147a5676ffb> /System/Library/PrivateFrameworks/CertInfo.framework/CertInfo
0x2de48000 - 0x2de4dfff CertUI armv7s <3a27c29611f53011ad3379d387bb901b> /System/Library/PrivateFrameworks/CertUI.framework/CertUI
0x2df77000 - 0x2df98fff ChunkingLibrary armv7s <44b4f99b47dd3f0aa9619b8064a3e828> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/ChunkingLibrary
0x2e431000 - 0x2e433fff CommonAuth armv7s <b00c1e8033303eb7a93fdf90e0a7a7e9> /System/Library/PrivateFrameworks/CommonAuth.framework/CommonAuth
0x2e434000 - 0x2e444fff CommonUtilities armv7s <06ffdaa9898d33ef816625bb3d93a92a> /System/Library/PrivateFrameworks/CommonUtilities.framework/CommonUtilities
0x2e445000 - 0x2e449fff CommunicationsFilter armv7s <60c2b30976e233299838015899c1ee13> /System/Library/PrivateFrameworks/CommunicationsFilter.framework/CommunicationsFilter
0x2e4b8000 - 0x2e4bcfff ConstantClasses armv7s <4b75b37195373a25ba38dca9b89e0e30> /System/Library/PrivateFrameworks/ConstantClasses.framework/ConstantClasses
0x2e4bd000 - 0x2e4f5fff ContentIndex armv7s <b8347f219df332a196a99e4ba397f7cd> /System/Library/PrivateFrameworks/ContentIndex.framework/ContentIndex
0x2e4f6000 - 0x2e4f9fff CoreAUC armv7s <c9d48abb96d6376c8778513f14f25180> /System/Library/PrivateFrameworks/CoreAUC.framework/CoreAUC
0x2e51d000 - 0x2e571fff CoreDAV armv7s <a7606dc393b039cf8560773d71df1b7f> /System/Library/PrivateFrameworks/CoreDAV.framework/CoreDAV
0x2e572000 - 0x2e58bfff CoreDuet armv7s <dadc8ae1a88f3d75b0d6c244dae2a71a> /System/Library/PrivateFrameworks/CoreDuet.framework/CoreDuet
0x2e590000 - 0x2e59ffff CoreDuetDaemonProtocol armv7s <cb3e7b1fe32a33b09abac1342eb48f99> /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/CoreDuetDaemonProtocol
0x2e5a6000 - 0x2e5a8fff CoreDuetDebugLogging armv7s <17818c8f932336769943c9e74254af3d> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/CoreDuetDebugLogging
0x2e7f6000 - 0x2e891fff CorePDF armv7s <d4837a0178783c03b805e48fa08507ee> /System/Library/PrivateFrameworks/CorePDF.framework/CorePDF
0x2e8f2000 - 0x2e8fcfff CoreRecents armv7s <92a8ed6e10123437b685c544c7be89af> /System/Library/PrivateFrameworks/CoreRecents.framework/CoreRecents
0x2e974000 - 0x2e992fff CoreServicesInternal armv7s <4bf749d6d95030cba3a88850e33e7514> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/CoreServicesInternal
0x2eb90000 - 0x2ec10fff CoreUI armv7s <6ca97dfeeebe37a1b74f651e56bbe561> /System/Library/PrivateFrameworks/CoreUI.framework/CoreUI
0x2ec11000 - 0x2ec7bfff CoreUtils armv7s <68e3551ba2023eeaa187682a19cfc6a4> /System/Library/PrivateFrameworks/CoreUtils.framework/CoreUtils
0x2ec7c000 - 0x2ec81fff CrashReporterSupport armv7s <a1d95e4d2034382e912ab4884d6a1157> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/CrashReporterSupport
0x2ec82000 - 0x2ec88fff DAAPKit armv7s <a2479886e0bd3d7eb30a927bd06a2752> /System/Library/PrivateFrameworks/DAAPKit.framework/DAAPKit
0x2ec94000 - 0x2ecd9fff DataAccess armv7s <6dbf6d1637103f7d990accda11d76908> /System/Library/PrivateFrameworks/DataAccess.framework/DataAccess
0x2eece000 - 0x2eeeffff DataAccessExpress armv7s <4d78edc22bb430d19f8f513d779ebce7> /System/Library/PrivateFrameworks/DataAccessExpress.framework/DataAccessExpress
0x2eefa000 - 0x2ef11fff DataDetectorsCore armv7s <11248bce6d423839a1070b9dd1e8244f> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/DataDetectorsCore
0x2ef13000 - 0x2ef2cfff DataDetectorsUI armv7s <747fdf85e19f3ca188b89bba7675181e> /System/Library/PrivateFrameworks/DataDetectorsUI.framework/DataDetectorsUI
0x2ef2d000 - 0x2ef33fff DataMigration armv7s <0d1c7a082dd23f5688c0af73bd52db7e> /System/Library/PrivateFrameworks/DataMigration.framework/DataMigration
0x2ef3d000 - 0x2ef3efff DiagnosticLogCollection armv7s <52071b4701ed3b2fa60d71a63efdc0ea> /System/Library/PrivateFrameworks/DiagnosticLogCollection.framework/DiagnosticLogCollection
0x2ef3f000 - 0x2ef59fff DictionaryServices armv7s <f087472c432733c9b0027e22a2fb8593> /System/Library/PrivateFrameworks/DictionaryServices.framework/DictionaryServices
0x2ef78000 - 0x2ef97fff EAP8021X armv7s <47b5191fd8d83584b7deaa2684e94a3a> /System/Library/PrivateFrameworks/EAP8021X.framework/EAP8021X
0x2f097000 - 0x2f099fff FTClientServices armv7s <134ad7a59577395caf7d96bfcf4422eb> /System/Library/PrivateFrameworks/FTClientServices.framework/FTClientServices
0x2f09a000 - 0x2f0cafff FTServices armv7s <9d002bd6316d3d499bfe9423c5cb3483> /System/Library/PrivateFrameworks/FTServices.framework/FTServices
0x2f0cb000 - 0x2f4eefff FaceCore armv7s <9b9520176ba23d5dabfb6a5a9c6b2646> /System/Library/PrivateFrameworks/FaceCore.framework/FaceCore
0x2f513000 - 0x2f513fff FontServices armv7s <ec4f36707bfa3ba28b63332e3cfcc4c0> /System/Library/PrivateFrameworks/FontServices.framework/FontServices
0x2f514000 - 0x2f5e7fff libFontParser.dylib armv7s <af8324e660b33765b5a52b10fea79492> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib
0x2f5e8000 - 0x2f5f4fff libGSFontCache.dylib armv7s <fbca918852ed353faa45c4087a2f915f> /System/Library/PrivateFrameworks/FontServices.framework/libGSFontCache.dylib
0x2f6d7000 - 0x2f6f2fff FrontBoardServices armv7s <d4e89c7da75d38228c4e321cf076717e> /System/Library/PrivateFrameworks/FrontBoardServices.framework/FrontBoardServices
0x2ffda000 - 0x2fff0fff GenerationalStorage armv7s <e4701d31f30e30d19afa0fb211399f5c> /System/Library/PrivateFrameworks/GenerationalStorage.framework/GenerationalStorage
0x2fff1000 - 0x30262fff GeoServices armv7s <6276f6d9bc98380da0fab1f85a5138b5> /System/Library/PrivateFrameworks/GeoServices.framework/GeoServices
0x30263000 - 0x30273fff GraphicsServices armv7s <06eeafe698713fd79424f8fdf249bf52> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x30310000 - 0x3035ffff Heimdal armv7s <87944068c3eb337ea606facaf6696c67> /System/Library/PrivateFrameworks/Heimdal.framework/Heimdal
0x303f2000 - 0x30472fff HomeSharing armv7s <32297e3cffff3fe0a28b70ee1bb09187> /System/Library/PrivateFrameworks/HomeSharing.framework/HomeSharing
0x304d1000 - 0x30527fff IDS armv7s <0edb980bee7d316fa0bb4832efbcfccb> /System/Library/PrivateFrameworks/IDS.framework/IDS
0x30528000 - 0x30549fff IDSFoundation armv7s <f6dfe45534aa34a6b8c5f74acee1cc72> /System/Library/PrivateFrameworks/IDSFoundation.framework/IDSFoundation
0x305b1000 - 0x3065ffff IMCore armv7s <51aec7ae856139079e6b39c804bad76e> /System/Library/PrivateFrameworks/IMCore.framework/IMCore
0x306f7000 - 0x3075efff IMFoundation armv7s <54a1298efd8a3a0ab968d7c513b0ee59> /System/Library/PrivateFrameworks/IMFoundation.framework/IMFoundation
0x30766000 - 0x30769fff IOAccelerator armv7s <b81286ef987d31bd9ae83f8322d94c6c> /System/Library/PrivateFrameworks/IOAccelerator.framework/IOAccelerator
0x3076c000 - 0x30772fff IOMobileFramebuffer armv7s <4ac5dd54ca853930aa6003839254ac1f> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/IOMobileFramebuffer
0x30773000 - 0x30778fff IOSurface armv7s <1bb65b18a65936d3a3d8a28b7a7d5bf1> /System/Library/PrivateFrameworks/IOSurface.framework/IOSurface
0x30779000 - 0x3077afff IOSurfaceAccelerator armv7s <8765e45debb9384aa1f1f7cbbbde8b59> /System/Library/PrivateFrameworks/IOSurfaceAccelerator.framework/IOSurfaceAccelerator
0x30816000 - 0x3081cfff IntlPreferences armv7s <9d8c3e2813e53148a4a104e918dc640d> /System/Library/PrivateFrameworks/IntlPreferences.framework/IntlPreferences
0x3081d000 - 0x30853fff LanguageModeling armv7s <2787f19f6449349291859b40dfb88ff1> /System/Library/PrivateFrameworks/LanguageModeling.framework/LanguageModeling
0x3088f000 - 0x308cbfff MIME armv7s <f41ebcfe27ba37d295fb0143e08e45bb> /System/Library/PrivateFrameworks/MIME.framework/MIME
0x3096f000 - 0x3097bfff MailServices armv7s <1b6ef0ab8a0535ccb7281874d8f2f6f3> /System/Library/PrivateFrameworks/MailServices.framework/MailServices
0x309af000 - 0x30a4efff ManagedConfiguration armv7s <6b2a389e13373470952a4a94e2f451d1> /System/Library/PrivateFrameworks/ManagedConfiguration.framework/ManagedConfiguration
0x30a59000 - 0x30a5afff Marco armv7s <de1fa71308ac3a14b19c1ef2a8367ca6> /System/Library/PrivateFrameworks/Marco.framework/Marco
0x30a5b000 - 0x30ad3fff MediaControlSender armv7s <204933b2eecc3eb2a97550fa9a4d5238> /System/Library/PrivateFrameworks/MediaControlSender.framework/MediaControlSender
0x30b72000 - 0x30b84fff MediaRemote armv7s <8583c7eb810a35f392d0aa99daea5dcf> /System/Library/PrivateFrameworks/MediaRemote.framework/MediaRemote
0x30b85000 - 0x30b94fff MediaServices armv7s <4503fa3dbb5c3972b04811c5af18c873> /System/Library/PrivateFrameworks/MediaServices.framework/MediaServices
0x30c12000 - 0x30ceffff Message armv7s <d43361cd4d7b3cc6b0d5abda7e2e53b1> /System/Library/PrivateFrameworks/Message.framework/Message
0x30cf5000 - 0x30cf7fff MessageSupport armv7s <b4f04a3a3fc237d094c4b572f77cc10c> /System/Library/PrivateFrameworks/MessageSupport.framework/MessageSupport
0x30d09000 - 0x30d16fff MobileAsset armv7s <fec17b7104b732798ec0cda1e47a940c> /System/Library/PrivateFrameworks/MobileAsset.framework/MobileAsset
0x30d3d000 - 0x30d46fff MobileBluetooth armv7s <e5ee20534ea739e7bb01464e0e891cfc> /System/Library/PrivateFrameworks/MobileBluetooth.framework/MobileBluetooth
0x30d62000 - 0x30d69fff MobileIcons armv7s <605d7447b21a339bbb6fa67458c9a870> /System/Library/PrivateFrameworks/MobileIcons.framework/MobileIcons
0x30d6a000 - 0x30d71fff MobileInstallation armv7s <1bfe7b98d7aa306ea1df0dd42a4b56ce> /System/Library/PrivateFrameworks/MobileInstallation.framework/MobileInstallation
0x30d72000 - 0x30d7efff MobileKeyBag armv7s <9c010e348a7b3a148a60f7252d05084a> /System/Library/PrivateFrameworks/MobileKeyBag.framework/MobileKeyBag
0x30dab000 - 0x30daefff MobileSystemServices armv7s <ddb6afac1c233f5daab60a666ece59b2> /System/Library/PrivateFrameworks/MobileSystemServices.framework/MobileSystemServices
0x30dd0000 - 0x30dddfff MobileWiFi armv7s <7537e6cfb3b33b669c3d0c22b01f55fe> /System/Library/PrivateFrameworks/MobileWiFi.framework/MobileWiFi
0x30e1c000 - 0x30fbbfff MusicLibrary armv7s <9cc281ea71403e9587ccc5982e7c16f3> /System/Library/PrivateFrameworks/MusicLibrary.framework/MusicLibrary
0x31054000 - 0x31059fff Netrb armv7s <a56f447a04c834a3b2f37a34b13e4fa4> /System/Library/PrivateFrameworks/Netrb.framework/Netrb
0x3105a000 - 0x31060fff NetworkStatistics armv7s <7fbbf8e9b610335aadc96eeb658dcacc> /System/Library/PrivateFrameworks/NetworkStatistics.framework/NetworkStatistics
0x31061000 - 0x3107efff Notes armv7s <43297712e4a93338910ff622842273ab> /System/Library/PrivateFrameworks/Notes.framework/Notes
0x31084000 - 0x31086fff OAuth armv7s <0c2849dabc57305baa7b8605cab0eafd> /System/Library/PrivateFrameworks/OAuth.framework/OAuth
0x317e1000 - 0x3181dfff OpenCL armv7s <fb56731bf6b03180a163fab3ca15ddad> /System/Library/PrivateFrameworks/OpenCL.framework/OpenCL
0x31903000 - 0x3192afff PersistentConnection armv7s <2a02604fc4ba37c3ac46323f48df3082> /System/Library/PrivateFrameworks/PersistentConnection.framework/PersistentConnection
0x31cfa000 - 0x31d44fff PhysicsKit armv7s <abc65981a5243535be8f8b2bea0db902> /System/Library/PrivateFrameworks/PhysicsKit.framework/PhysicsKit
0x31d45000 - 0x31d5bfff PlugInKit armv7s <3ec17a1ff2cd3a70b88c2b9de8964b5a> /System/Library/PrivateFrameworks/PlugInKit.framework/PlugInKit
0x31d5c000 - 0x31d63fff PowerLog armv7s <a7ccb43187613877946faee1079b4c3e> /System/Library/PrivateFrameworks/PowerLog.framework/PowerLog
0x31f5d000 - 0x32004fff Preferences armv7s <4ad19193fb72316bba48d6d9073d1a60> /System/Library/PrivateFrameworks/Preferences.framework/Preferences
0x32005000 - 0x32042fff PrintKit armv7s <9195e5878ba23aaeabbbcf380cf76f02> /System/Library/PrivateFrameworks/PrintKit.framework/PrintKit
0x32047000 - 0x320dbfff ProofReader armv7s <b6934340f1c837e2b921785474d9b380> /System/Library/PrivateFrameworks/ProofReader.framework/ProofReader
0x320ec000 - 0x320f8fff ProtocolBuffer armv7s <e850daf92889358fb2a3ecaf3629a97f> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/ProtocolBuffer
0x3212b000 - 0x3219afff Quagga armv7s <8ee67622284038ae9cd333b4f7220ede> /System/Library/PrivateFrameworks/Quagga.framework/Quagga
0x32387000 - 0x32413fff SAObjects armv7s <e061cf980a8936edbda44d4293c4907c> /System/Library/PrivateFrameworks/SAObjects.framework/SAObjects
0x3257a000 - 0x32594fff SpringBoardServices armv7s <f9f6add53c76327a8d73a55918c26ed7> /System/Library/PrivateFrameworks/SpringBoardServices.framework/SpringBoardServices
0x328ff000 - 0x32a17fff StoreServices armv7s <d1a60fa363623bf08dab5072d7b8f4fe> /System/Library/PrivateFrameworks/StoreServices.framework/StoreServices
0x32ae8000 - 0x32aeafff TCC armv7s <b8313eb23a6537a8861716ac21ecbc9e> /System/Library/PrivateFrameworks/TCC.framework/TCC
0x32b31000 - 0x32b6efff TelephonyUtilities armv7s <b28ce5ba7cca391691a32106911ebd66> /System/Library/PrivateFrameworks/TelephonyUtilities.framework/TelephonyUtilities
0x339b5000 - 0x339dcfff TextInput armv7s <d183b563c21438a6bbbc915d589ab962> /System/Library/PrivateFrameworks/TextInput.framework/TextInput
0x33a8f000 - 0x33b50fff UIFoundation armv7s <7562389936d635fab4dc251b290fabfb> /System/Library/PrivateFrameworks/UIFoundation.framework/UIFoundation
0x33b72000 - 0x33b75fff UserFS armv7s <c044878c4cd43943bb55f355b882bb67> /System/Library/PrivateFrameworks/UserFS.framework/UserFS
0x342f9000 - 0x34317fff VoiceServices armv7s <a552fc9f06473b49b98cccb119d71d0a> /System/Library/PrivateFrameworks/VoiceServices.framework/VoiceServices
0x343a1000 - 0x343c7fff WebBookmarks armv7s <89c6195615a531e4abb72a5e744ee219> /System/Library/PrivateFrameworks/WebBookmarks.framework/WebBookmarks
0x343dd000 - 0x34f60fff WebCore armv7s <723ae76958093166ba7762e96663bf00> /System/Library/PrivateFrameworks/WebCore.framework/WebCore
0x34f61000 - 0x3501ffff WebKitLegacy armv7s <dfc480439ce537ce8292eceb6c34b16d> /System/Library/PrivateFrameworks/WebKitLegacy.framework/WebKitLegacy
0x351bf000 - 0x351c7fff XPCObjects armv7s <69caaf09b0ee3596a7b420e092a5c482> /System/Library/PrivateFrameworks/XPCObjects.framework/XPCObjects
0x353b5000 - 0x353d9fff iCalendar armv7s <05eb09ddf7483831a7107a32f7ed31fb> /System/Library/PrivateFrameworks/iCalendar.framework/iCalendar
0x355cd000 - 0x35608fff iTunesStore armv7s <7a7a1cdae7dd305e816183c504382c88> /System/Library/PrivateFrameworks/iTunesStore.framework/iTunesStore
0x35d56000 - 0x35d5efff libAccessibility.dylib armv7s <094547582d723c27b8150d539f0eaf4e> /usr/lib/libAccessibility.dylib
0x35e90000 - 0x35ea6fff libCRFSuite.dylib armv7s <9c29786bd63f341f916aa6f6662ca675> /usr/lib/libCRFSuite.dylib
0x35ed8000 - 0x35fdcfff libFosl_dynamic.dylib armv7s <0052248414073cc78819925a431dd2fe> /usr/lib/libFosl_dynamic.dylib
0x35ff6000 - 0x3600dfff libMobileGestalt.dylib armv7s <16db2870e9443a669790f8bb678f572a> /usr/lib/libMobileGestalt.dylib
0x36033000 - 0x36034fff libSystem.B.dylib armv7s <916c64d9cab33b2a9bbb355f4be13a76> /usr/lib/libSystem.B.dylib
0x360a5000 - 0x360e9fff libTelephonyUtilDynamic.dylib armv7s <2a798667e6d1311ab5d20ce7640d856e> /usr/lib/libTelephonyUtilDynamic.dylib
0x361f9000 - 0x3621bfff libarchive.2.dylib armv7s <527e8c0122073f578d895580df8169f4> /usr/lib/libarchive.2.dylib
0x3621c000 - 0x3621cfff libassertion_extension.dylib armv7s <536e1abbba3b31d8a6560c6d5c7c99e2> /usr/lib/libassertion_extension.dylib
0x3624b000 - 0x36257fff libbsm.0.dylib armv7s <ae0d4a27677f3f318d5994bd5a299009> /usr/lib/libbsm.0.dylib
0x36258000 - 0x36261fff libbz2.1.0.dylib armv7s <cdff2930a8333bb689793675dee50df4> /usr/lib/libbz2.1.0.dylib
0x36262000 - 0x362acfff libc++.1.dylib armv7s <8fad3aace328348da9c59ce042a8f764> /usr/lib/libc++.1.dylib
0x362ad000 - 0x362c8fff libc++abi.dylib armv7s <7b486834c946373e8880760a56965ca5> /usr/lib/libc++abi.dylib
0x362ca000 - 0x362d7fff libcmph.dylib armv7s <361b1fe8b4673926b7116829e02d0b02> /usr/lib/libcmph.dylib
0x362d8000 - 0x362e0fff libcupolicy.dylib armv7s <e937a5f056543f0f85fc140f6c51a188> /usr/lib/libcupolicy.dylib
0x36307000 - 0x3631ffff libextension.dylib armv7s <bff08d045d4a318d863941427db9f018> /usr/lib/libextension.dylib
0x3633e000 - 0x36341fff libheimdal-asn1.dylib armv7s <c11a6c53a6ed39cc942b2534ca2d4f1a> /usr/lib/libheimdal-asn1.dylib
0x36342000 - 0x3642ffff libiconv.2.dylib armv7s <747ef3a673c63868af6c67855f7fbd44> /usr/lib/libiconv.2.dylib
0x36430000 - 0x3659efff libicucore.A.dylib armv7s <a9bb4dc7760e3184bec94e62a99ce135> /usr/lib/libicucore.A.dylib
0x365ab000 - 0x365abfff liblangid.dylib armv7s <c039470cbe2b39f2b7f5f80676b7b6d0> /usr/lib/liblangid.dylib
0x365ac000 - 0x365b6fff liblockdown.dylib armv7s <5c2434e5bec830ccb88db1fb9c139bd6> /usr/lib/liblockdown.dylib
0x365b7000 - 0x365ccfff liblzma.5.dylib armv7s <d9f0e9bc84273d28bb36dea3e8f362aa> /usr/lib/liblzma.5.dylib
0x36945000 - 0x36959fff libmis.dylib armv7s <02e6bf70c6bf376793e2c631a6f9807d> /usr/lib/libmis.dylib
0x36983000 - 0x36b7dfff libobjc.A.dylib armv7s <f6ae15f5da4a3ee1aa1a080c069e3a1c> /usr/lib/libobjc.A.dylib
0x36c32000 - 0x36c48fff libresolv.9.dylib armv7s <6f5e721723f73e079cad07f800ce7c16> /usr/lib/libresolv.9.dylib
0x36c73000 - 0x36d19fff libsqlite3.dylib armv7s <463044a8a4543b11ac70cdd88a6a4a54> /usr/lib/libsqlite3.dylib
0x36d67000 - 0x36d8dfff libtidy.A.dylib armv7s <ce3364e915d23d74ae1564c2f9532f7d> /usr/lib/libtidy.A.dylib
0x36d8e000 - 0x36d96fff libtzupdate.dylib armv7s <c23ed5e6c3b93a33afac2d1496094825> /usr/lib/libtzupdate.dylib
0x36d9a000 - 0x36e50fff libxml2.2.dylib armv7s <3c08bca3a51231749b43e35d4e627cdc> /usr/lib/libxml2.2.dylib
0x36e51000 - 0x36e72fff libxslt.1.dylib armv7s <f4c65edfeb6032e88ce570e92f5f9d24> /usr/lib/libxslt.1.dylib
0x36e73000 - 0x36e7ffff libz.1.dylib armv7s <b261d154b0633244af8249c457f13def> /usr/lib/libz.1.dylib
0x36e80000 - 0x36e84fff libcache.dylib armv7s <7f2ac0c12ea6341ab3fb0a9b20400244> /usr/lib/system/libcache.dylib
0x36e85000 - 0x36e8efff libcommonCrypto.dylib armv7s <de40d2d23c6f36ac88bf74e6551e22f8> /usr/lib/system/libcommonCrypto.dylib
0x36e8f000 - 0x36e93fff libcompiler_rt.dylib armv7s <da89cd909a9a3678b531951a88ba5519> /usr/lib/system/libcompiler_rt.dylib
0x36e94000 - 0x36e9afff libcopyfile.dylib armv7s <48cc5f26af163b4d9dca2ea06373c724> /usr/lib/system/libcopyfile.dylib
0x36e9b000 - 0x36ee7fff libcorecrypto.dylib armv7s <f1d32ffeb2c1366ebe631cb906a79737> /usr/lib/system/libcorecrypto.dylib
0x36ee8000 - 0x36f07fff libdispatch.dylib armv7s <7106cbb58b94372d9a4ae63f6dc39e1e> /usr/lib/system/libdispatch.dylib
0x36f08000 - 0x36f09fff libdyld.dylib armv7s <bf125933f7c33a63999c21ae82e4223c> /usr/lib/system/libdyld.dylib
0x36f0a000 - 0x36f0afff libkeymgr.dylib armv7s <00e2af5454d73aef9254cd299247d537> /usr/lib/system/libkeymgr.dylib
0x36f0b000 - 0x36f0bfff liblaunch.dylib armv7s <9dbb42926564306cb61af50e6f3fe65a> /usr/lib/system/liblaunch.dylib
0x36f0c000 - 0x36f0ffff libmacho.dylib armv7s <ffcab8e9628a3c93823adce1717ead38> /usr/lib/system/libmacho.dylib
0x36f10000 - 0x36f11fff libremovefile.dylib armv7s <741688071e8c3f54a2ffa7d5bbf0ad0f> /usr/lib/system/libremovefile.dylib
0x36f12000 - 0x36f23fff libsystem_asl.dylib armv7s <fde71151f3633b19897377baab64b521> /usr/lib/system/libsystem_asl.dylib
0x36f24000 - 0x36f24fff libsystem_blocks.dylib armv7s <28477932f242360c892f12c609f95419> /usr/lib/system/libsystem_blocks.dylib
0x36f25000 - 0x36f88fff libsystem_c.dylib armv7s <5d0717641c5e339da3ca1f21faa448e1> /usr/lib/system/libsystem_c.dylib
0x36f89000 - 0x36f8bfff libsystem_configuration.dylib armv7s <2e43e283d6be3ad685e50217cb2b8661> /usr/lib/system/libsystem_configuration.dylib
0x36f8c000 - 0x36f8dfff libsystem_coreservices.dylib armv7s <b5dcec2938633107b43383dfbf8e07e6> /usr/lib/system/libsystem_coreservices.dylib
0x36f8e000 - 0x36f9afff libsystem_coretls.dylib armv7s <2dc9e3d6317535f4b536f631decf4913> /usr/lib/system/libsystem_coretls.dylib
0x36f9b000 - 0x36fa1fff libsystem_dnssd.dylib armv7s <7482038666363dc0b1a435e57b513989> /usr/lib/system/libsystem_dnssd.dylib
0x36fa2000 - 0x36fbafff libsystem_info.dylib armv7s <ff47cce8338c3fea9614c8c91a104349> /usr/lib/system/libsystem_info.dylib
0x36fbb000 - 0x36fd5fff libsystem_kernel.dylib armv7s <0135350370a335d1acca9ce9858595df> /usr/lib/system/libsystem_kernel.dylib
0x36fd6000 - 0x36ff5fff libsystem_m.dylib armv7s <d1bc7f2b6bbd3ddc83930b9ba33dc507> /usr/lib/system/libsystem_m.dylib
0x36ff6000 - 0x37008fff libsystem_malloc.dylib armv7s <4285bc1fb79b3dc4a45fe1680ddb276b> /usr/lib/system/libsystem_malloc.dylib
0x37009000 - 0x37036fff libsystem_network.dylib armv7s <93a5fa1da38835b693fcdbf8e200fe17> /usr/lib/system/libsystem_network.dylib
0x37037000 - 0x3703cfff libsystem_networkextension.dylib armv7s <3c2cc31c08e534f994eae9e9390c0bda> /usr/lib/system/libsystem_networkextension.dylib
0x3703d000 - 0x37044fff libsystem_notify.dylib armv7s <bc57f62dd51b39b49d5ef5890b386f76> /usr/lib/system/libsystem_notify.dylib
0x37045000 - 0x37049fff libsystem_platform.dylib armv7s <485d83aa9719310982082cb9c6c5a2c4> /usr/lib/system/libsystem_platform.dylib
0x3704a000 - 0x37050fff libsystem_pthread.dylib armv7s <211207e983bc395f9c59668f9088bef2> /usr/lib/system/libsystem_pthread.dylib
0x37051000 - 0x37053fff libsystem_sandbox.dylib armv7s <ae0d736739bd3aef9fa1c29fcf22e90e> /usr/lib/system/libsystem_sandbox.dylib
0x37054000 - 0x37057fff libsystem_stats.dylib armv7s <63dea98a903b3b49a7db9ffd18bd3681> /usr/lib/system/libsystem_stats.dylib
0x37058000 - 0x3705dfff libsystem_trace.dylib armv7s <f1d18cb2a43c3e518ad37bcf31224eda> /usr/lib/system/libsystem_trace.dylib
0x3705e000 - 0x3705efff libunwind.dylib armv7s <1440671d926a3346abaa73fa726ddbfc> /usr/lib/system/libunwind.dylib
0x3705f000 - 0x3707afff libxpc.dylib armv7s <acfe5f1e68d93d249b65d604403a9625> /usr/lib/system/libxpc.dylib

Hi,
Thank you for posting in Windows Server Forum.
As from your description it seems that you are using version 8.1.0 for your remote desktop MAC. Here I can suggest you update to latest remote desktop version 8.1.3 and check the result.
Microsoft Remote Desktop
https://itunes.apple.com/in/app/microsoft-remote-desktop/id714464092?mt=8
Hope it helps!
Thanks.
Dharmesh Solanki

Server does not support remote panels

I am developing an online laboratory setup and hence am using a client server model..the client VI being accessed by remote users online. I have done all the necessary steps using Web Publishing tool and the configuration set up. I have also tested the VI previously online. Suddenly now when I hit the URL for the VI the panel does not load...it says Server does not support remote panels. What could be the problem?

see answer given second posting of question.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Remote panels - Client Crashes Situation

Similar Messages

Maybe you are looking for