Report hangs when using Remote Desktop

I am having trouble with Crystal Reports 11. I was wondering if there is a known issue when using it in conjuction with Remote Desktop.
Here is the scenario.
I am using Remote Desktop to connect to a server.
I am running a report using Crystal Reports 11.
The records have already been retrieved (approx. 800,000 records) and is printing - slowly.
It takes around 75 minutes for the report to print 12 pages.
If the Remote Desktop connection is closed, then re-established, the Crystal Reports pops up a message box stating "Not Supported". The pages of data the were previously printed are now blank. (For example: if it was on page 1 of 9+ it will go back to 1 of 1+ and the page will be blank.)
If I use a VPN to connect to the network, then use the Remote Desktop Connection to connect to the server, the connection will periodically disconnect and the re-establish. This does not occur when not using Crystal Reports.
Is there a problem with using Crystal Reports with Remote Desktop? Is there a better way to run my reports remotely?
Thanks for any input.
Ryan

You may be better off posting this in the Crystal Reports Design forum as that team supports issues regarding working with the CR designer:
SAP Crystal Reports
Ludek

Similar Messages

  • Printing to a Printer Connected to TIme Machine when using Remote Desktop

    Hi,
    I am having trouble printing to a printer connected to our wireless network via Time Capsule when I am on my remote desktop connection. Printing from all other programs work. I downloaded Bonjour on our Windows based server, and it did not detect any printers. When I am connected directly to the printer, I can print when using remote desktop. Any suggestions are much appreciated.
    Thanks!
    Mac OS X (10.5.4)

    Airport Extreme/Express do emulate Jetdirect/port 9100 printing, but that isn't what they use for printing from OS X. OS X and the Bonjour/airport software use USB port redirection, a unique and separate method.
    If the HP driver supports any protocol over ethernet, it would be appletalk. Does that router server use appletalk?

  • RMBP reaches 104C when using remote desktop.  Is this normal?

    I have a new rMBP that is reaching temps of 104C when using remote desktop or other moderately intensive applications.  Is this normal?

    No, that's way too hot. It's only a few degrees below automatic thermal shutdown.

  • ITunes won't play when using Remote Desktop

    I noticed that if I access my home computer from work remotely using Windows Remote Desktop, and that iTunes is opened on my Home PC, when I get home, I can't play music from iTunes.
    I need to close iTunes and re-open it again...
    any idea?

    Sorted it.

  • Bug when using Remote Desktop

    I've found a bug that I have replicated on 3 different computers, all running Vista. Listen to a song in iTunes and pause it. Now, remote desktop to that computer from a new computer. After you're connected, simply disconnect and return to the original computer.
    Now, if you press Play, the button changes to the Pause symbol like usual, but it never actually plays. The timebar doesn't advance either.
    Is there a fix for this?

    You must turn off hardware acceleration in the Firefox 4 browser on the remote PC to allow remote desktop applications to refresh the screen properly. Obviously you will not be able to make this change remotely, as you will not be able to see the menus until after the change is made.
    1. FireFox > options > options> Advanced > Browsing > Uncheck "Use hardware acceleration when available"
    2. Restart Firefox 4

  • Specific User receiving Application crash when using Remote Desktop Application

    I have a client running a server with their line of business software configured as a remote application. I have one user that when he attempts to run the line of business software as a remote application he receives a APPCRASH error.However if another user
    launches the remote application and then signs in as the problem user there is no APPCRASH.
    The following information is reported with the error:
    Faulting application name: impress.exe, version: 5.1.102.0, time stamp: 0x522f820a
    Faulting module name: impress.exe, version: 5.1.102.0, time stamp: 0x522f820a
    Exception code: 0xc0000005
    Fault offset: 0x003fe41f
    Faulting process id: 0x268
    Faulting application start time: 0x01cf11ffa8811e46
    Faulting application path: C:\data\Impress\impress.exe
    Faulting module path: C:\data\Impress\impress.exe
    Report Id: 238e8dfc-7df6-11e3-b1b6-001e678ee8f8
    After the app crash the is a warning in the event log, but its about 43 seconds later; Event 1530, user Profile Service
    Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  
     DETAIL - 
     1 user registry handles leaked from \Registry\User\S-1-5-21-2105745629-1987324649-1874639966-1224:
    Process 328 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-2105745629-1987324649-1874639966-1224\Printers\DevModePerUser
    just trying to find some sort of hint as to way the remote application would crash for just one user. it is my luck that the one user is the owner.

    It looks like the issue was resolved by deleting the problem users profile off of the terminal server.  The user can now access the RD application without suffering an APPCRASH error.

  • Agent install hang When Install by using remote desktop

    Hi All
    My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
    When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
    But he call another admin install agent locally. agent install successfully.
    Who have the same experience about remote install by using remote desktop(mstsc) ??
    thanks
    wyldkao

    Originally Posted by wyldkao
    Hi All
    My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
    When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
    But he call another admin install agent locally. agent install successfully.
    Who have the same experience about remote install by using remote desktop(mstsc) ??
    thanks
    wyldkao
    Windows XP right?
    Then you need to install this patch before installing ZCM agent: An application that installs a mirror driver over a Terminal Services session may stop responding on a Windows XP-based computer
    Thomas

  • Cannot use Remote Desktop host on Windows 8.1 Pro, termsrv corrupted?

    Hello,
    Few days ago I upgraded my home desktop machine from Windows 8.1 to Windows 8.1 Professional so I can use the Remote Desktop feature.
    I enabled everything needed, checked "Allow computers to connect to this computer" from the Remote Settings, forwarded the port 3389 in my rounter and allowed it in my firewall etc...
    But I still can't connect to this computer from outside my home network or inside it. The error I get trying to connect is this:
    (For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
    I'm trying to connect using a laptop running Windows 7 Home Premium.
    After searching around I found out that the service responsible for the RDP is called "TermService", I found it on my services but was unable to start it:
    (For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
    Also, notice the description of the service. So I tried to run a System File Checker on the service's DLL (sfc /scanfile=c:\windows\system32\termsrv.dll) and got this log:
    2014-10-05 14:20:41, Info                  CBS    TI: --- Initializing Trusted Installer ---
    2014-10-05 14:20:41, Info                  CBS    TI: Last boot time: 2014-10-05 13:56:05.492
    2014-10-05 14:20:41, Info                  CBS    Starting TrustedInstaller initialization.
    2014-10-05 14:20:41, Info                  CBS    Ending TrustedInstaller initialization.
    2014-10-05 14:20:41, Info                  CBS    Starting the TrustedInstaller main loop.
    2014-10-05 14:20:41, Info                  CBS    TrustedInstaller service starts successfully.
    2014-10-05 14:20:41, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
    2014-10-05 14:20:41, Info                  CBS    Startup processing thread terminated normally
    2014-10-05 14:20:41, Info                  CBS    Starting TiWorker initialization.
    2014-10-05 14:20:41, Info                  CBS    Ending TiWorker initialization.
    2014-10-05 14:20:41, Info                  CBS    Starting the TiWorker main loop.
    2014-10-05 14:20:41, Info                  CBS    TiWorker starts successfully.
    2014-10-05 14:20:41, Info                  CBS    TiWorker: Client requests SFP repair object.
    2014-10-05 14:20:41, Info                  CBS    Universal Time is: 2014-10-05 11:20:41.783
    2014-10-05 14:20:41, Info                  CBS    Loaded Servicing Stack v6.3.9600.17246 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17246_none_fa4ae8e99b1f603c\cbscore.dll
    2014-10-05 14:20:41, Info                  CSI    [email protected]/10/5:11:20:41.786 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffeeace2e53 @0x7ffeeace24ac @0x7ff69a94d2df @0x7ff69a94dc97
    @0x7fff02912225)
    2014-10-05 14:20:41, Info                  CBS    SQM: Initializing online with Windows opt-in: True
    2014-10-05 14:20:41, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2014-10-05 14:20:41, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2014-10-05 14:20:41, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
    2014-10-05 14:20:41, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2014-10-05 14:20:41, Info                  CBS    NonStart: Set pending store consistency check.
    2014-10-05 14:20:41, Info                  CSI    [email protected]/10/5:11:20:41.801 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffef3637fc0 @0x7ffef36380f2 @0x7ff69a94ca25 @0x7ff69a94dcae
    @0x7fff02912225)
    2014-10-05 14:20:41, Info                  CSI    00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x559943db20
    2014-10-05 14:20:41, Info                  CSI    00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
    2014-10-05 14:20:41, Info                  CSI    00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x26c
    2014-10-05 14:20:41, Info                  CSI    00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
    2014-10-05 14:20:41, Info                  CSI    [email protected]/10/5:11:20:41.999 Beginning NT transaction commit...
    2014-10-05 14:20:41, Info                  CSI    [email protected]/10/5:11:20:41.999 CSI perf trace:
    CSIPERF:TXCOMMIT;143
    2014-10-05 14:20:42, Info                  CSI    00000009 CSI Store 367642371808 (0x00000055993166e0) initialized
    2014-10-05 14:20:42, Info                  CSI    0000000a [SR] Verifying 1 components
    2014-10-05 14:20:42, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
    2014-10-05 14:20:42, Info                  CSI    0000000c [SR] Verify complete
    2014-10-05 14:20:52, Info                  CBS    TiWorker: Client requests SFP repair object.
    2014-10-05 14:20:55, Info                  CBS    TiWorker: Client requests SFP repair object.
    2014-10-05 14:20:55, Info                  CSI    0000000d [SR] Verifying 1 components
    2014-10-05 14:20:55, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
    2014-10-05 14:20:55, Info                  CSI    0000000f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000010 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
    pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-05 14:20:55, Info                  CSI    00000011 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000012 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
    pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-05 14:20:55, Info                  CSI    00000013 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
    2014-10-05 14:20:55, Info                  CSI    00000014 Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000015 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000016 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
    in store is also corrupted
    2014-10-05 14:20:55, Info                  CSI    00000017 [SR] Verify complete
    2014-10-05 14:20:55, Info                  CSI    00000018 [SR] Repairing 1 components
    2014-10-05 14:20:55, Info                  CSI    00000019 [SR] Beginning Verify and Repair transaction
    2014-10-05 14:20:55, Info                  CSI    0000001a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    0000001b [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
    pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-05 14:20:55, Info                  CSI    0000001c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    0000001d [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
    pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-10-05 14:20:55, Info                  CSI    0000001e [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
    2014-10-05 14:20:55, Info                  CSI    0000001f Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000020 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
    do not match actual file [l:22{11}]"termsrv.dll" :
      Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
    2014-10-05 14:20:55, Info                  CSI    00000021 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
    in store is also corrupted
    2014-10-05 14:20:55, Info                  CSI    00000022 [SR] Repair complete
    Since it's the first time I use this tool I'm not familiar with this log file, but what I managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
    My question is:
    How can I repair this file? Is this even the problem preventing me from connecting to this computer via Remote Desktop?
    Here's a link to my original question which contatining the images.
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/cannot-use-remote-desktop-host-on-windows-81-pro/e4776239-4d9e-4934-ae2d-b87cc09f7ade

    managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
    So, the next step supposedly is
    using  DISM.
    Coincidentally I reached that page last night from
    this one, which I thought gave me a better awareness of how much manual repair might be possible.  E.g. maybe the WinSxS isn't quite as fragile as we are being led to believe?  (It's making me feel sort of like how I used to feel about the
    registry when seeing all the caveats about using RegEdit before I got used to that tool.)
    Advanced guidelines for diagnosing and fixing servicing corruption
    http://technet.microsoft.com/en-us/library/ee619779(v=WS.10).aspx 
    Something else that I became aware of yesterday serendipitously is SxStrace.exe.  I have never seen it used but it sounds useful.  E.g. perhaps easier to interpret for supplemental clues than the ProcMon trace that I usually advocate. 
    Or perhaps use both and see in ProcMon when the SxStrace is writing.   E.g. filter with  Operation Is WriteFile.
    However, what I would do first is find out what the state of your system is regarding that module.  E.g. try this Powershell pipeline to list what you have.
    PS C:\windows> dir -R -Fil "termsrv.dll" | sort-object FullName | ft Length, FullName -AutoSize
    Note that I am giving you the whole command line, including prompt to show where the command should be started from.
    C.f. another thread where doing the same diagnostic procedure seems to be finding more a problem with the Windows Update software than with the user's WinSxS cache.
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3#LastReply  
    HTH
    Robert Aldwinckle

  • Xvnc hangs after exiting Remote Desktop session

    After closing a window of Remote Desktop session with XFCE Desktop run on latest ArchLinux, XRDP server exits, but Xvnc server started by that session keeps running, and within 5-10 min starts suddenly putting high load on CPU, while doing nothing useful.
    Why this happen, and how to auto close it when closing Remote Desktop window & session?

    While the hang reason is still unknown, I found that login out of XFCE from within open XRDP session window before closing the session will shutdown relevant processes on the server host, including Xvnc.

  • Not able to use remote desktop externally on a WRV200

    Hello all,
    Untill 5 minutes ago I wasn't able to get remote desktop to work from an extern computer to my computer which is wireless connected in our network. It worked from a network computer from the beginning.
    I have port 3389 correctly forwarded to my static intern ip address (same way as i did with my ftp server which works properly, so I guess I did it wright)
    Just 5 minutes ago I found out that it does work when I enable DMZ (see bottom for DMZ details).. What am I doing wrong? I prefer not to use DMZ since it will automatically forward all internet port requests which arent forwarded to any of the other computers, which makes my computer quite vulnerable, wright? (I am using the win xp firewall, but still)
    Thanks in advance!
    Edit 1: I have UPNP enabled
    Edit 2: I have remote desktop excluded in the windows firewall, but thats logic since remote desktop does work from another network computer and with DMZ enabled
    Edit 3: I'm the only one in our network who is using remote desktop
    Edit 4: I also tried to forward all these ports to my pc: 22, 65301, 5631-5632
    The DMZ screen allows one local PC to be exposed to the Internet for use of a special-purpose service such as
    Internet gaming and videoconferencing through Software DMZ. Whereas Port Range Forwarding can only forward
    a maximum of 10 ranges of ports, DMZ hosting forwards all the ports for one PC at the same time.
    Message Edited by PulpVictim on 07-06-2007 02:30 AM
    Message Edited by PulpVictim on 07-06-2007 02:34 AM
    Message Edited by PulpVictim on 07-06-2007 02:35 AM
    Message Edited by PulpVictim on 07-06-2007 02:39 AM

    Enable the logs on your router. Then try to do remote desktop. It will fail of course. After it does, view the logs, there might be ports listed in the incoming logs that you failed to forward.

  • How to use remote desktop client in mountain lion

    How to use remote desktop client in mountain lion.
    I want to connect my other system(ubuntu) using mac remote desktop client, But i could not locate remote desktop client in moutain lion.

    In Ubuntu 12.xx use Dash to find "Desktop Sharing" and set the preferences, including requiring a password.
    Then in Ubu use System Settings > Network to determine your Ubu machine's IP address, such as 192.168.1.13.
    On the Mountain Lion Mac do Finder > Go > Connect to Server   and enter:  vnc://192.168.1.13  or whatever your IP is.  Enter the password that you used in the Ubu Desktop Sharing setup, when asked.
    On the Ubu machine answer the question that pops up asking for permission to connect.  Your Ubu screen will now show up on the Mac, and you can remote control it.   Here I am running "Octave" (a math program) on the Ubu machine, remotely.
    Works great!  BTW, you can do this from an iPad too, using a VNC client such as Mocha VNC Lite.  You can even run both remotes simultaneously.
    Good luck.

  • LabView (8.2) hangs when using I/O operations with traditiona​l NI-DAQ 7.4.4 after aborting LabView program

    Hello!
    We have the following problem:
    LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
    We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
    We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
    Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
    Best regards,
    Matthias

    Hello Sprice,
    Browse the shipping examples according to “Directory Structure” and then select
    DAQ to find the Traditional DAQ examples. 
    There a lot of examples that are written for counters (Counter >>
    daq-stc.llb >> Count Edges (DAQ-STC).vi). 
    What kind of signals are your photons creating?  Are they TTL compatible at a certain
    frequency?  You don’t care about overwriting
    your buffer?
    Respectfully,
    Rob F
    Test Engineer
    Condition Measurements
    National Instruments

  • Kinect for windows sensor does not start when using remote WMI

    Scenario:
    I have written a software (lets call it kinectRecorder.exe) that uses "kinect for windows sensor" to record images. The machine that connects to the kinect sensor has windows 8.1 and kinect v2 installed. The software is able to successfully records
    images from kinect sensor when running locally. (meaning if I hit f5 from vs2013, frames are recorded to local disk)
    Due to resource constraint and other requirement, I have to remotely kickoff kinectRecorder.exe on the windows 8.1 machine from a windows 7 machine. on the windows 7 machine, I remotely kick off the kinectRecorder.exe using windows WMI infrastructure. 
    The credential used for windows 8.1 machine and windows 7 machine are the same under same windows domain. the credential used to authenticate in wmi is also the same, I can see the user name running kinectRecorder.exe after kinectrecorder.exe is started
    remotely. 
    Problem:
    The result is that kinectRecorder.exe starts ok, but after the kinectsensor.open call, isavailable property changed to false, meaning sensor not detected. 
    Question:
    What's stopping kinect sensor to be detected/opened (i'm not sure what the correct jargon is here)?
    I have been search the web, In msdn documentation (known issues),  I cannot find the problem being mentioned. I wonder if I'm the only person who has encountered this issue before. 
    Any pointer is hugely appreciated. 

    Kinect is not supported within the context of a service because of the underlying need for a user session, see
    https://social.msdn.microsoft.com/Forums/en-US/72cecf8b-ac64-47e2-b54b-ddbd1dc237c9/calling-kinect-sdk-apis-from-a-windows-service-is-not-possiblesupported?forum=kinectv2sdk
    Can determine that the system has at least one logged in user and can you launch the application within that users session? KinectMontior/KinectService must be running for the runtime to get any data from the sensor. If you use Remote
    Desktop to log into that user session, you can confirm this works by running any of the samples and they should work without issue(remember to ensure that your audio remoting is left on the server, see troubleshooting guide
    https://social.msdn.microsoft.com/Forums/en-US/20dbadae-dcee-406a-b66f-a182d76cea3b/troubleshooting-and-common-issues-guide?forum=kinectv2sdk).
    Carmine Sirignano - MSFT

  • Installation issue - using a remote server without using remote desktop or citrix

    Hello Experts..
    We have a client who wants to install SAP Client (SAP 9 PL 11) in their local machines, but connecting to a remote server. They want to avoid connecting through Remote Desktop or Citrix.They already installed SAP clients in local pc's and when they select the server, they already configured it to a server located overseas. We succed on achieve the connection, but the performance is really poor (sometimes it takes about 2 minutes to open a simple menu in SAP).
    We ran internet speed tests in the client's office and in the server, and both results were more than satisfactory. But we couldn't come up with a reason for this enviroment works properly..
    The question is... Is this kind of enviroment supported by SAP?? Do you know about any alternative to connect from the local PC to a remote server without using remote desktop or citrix??
    Thanks in advance...
    Raúl Fragueiro

    Hi,
    I assumed you are using VPN connection right?
    In your scenario that is normal since the GUI of SAP B1 is not built for type of connection compare
    to SAP ERP GUI.
    The only SAP supported type of remote connection is either Terminal Server or Citrix.
    In our own scenario we are using Terminal Server and we are very satisfied. We have used
    this between to different cities. This is also prevents data corruption cause by intermittent
    internet connection.
    Hoping you will be convinced of using Terminal Server or Citrix.
    By the way, a quick question, why are you hesitant to use RDC or Citrix?
    For overview, if your remote requirement is just simple and basic you may use Terminal Server.
    The implementation of  this is very fast and simple also, what you need is only a license.
    If complex and advance features connection requirement connection use Citrix.
    For better understanding you may search from the site for the difference of the two.
    Thanks.
    Regards,
    Clint

  • I don't have a wireless keyboard or mouse for my 2007 iMac, is there any way that can use remote desktop and access it from my 2010mbp.

    i don't have a wireless keyboard or mouse for my 2007 iMac, is there any way that can use remote desktop and access it from my 2010mbp

    Hi champrider,
    You can use an application such as Apple Remote Desktop to control your iMac remotely. See this article -
    OS X Mavericks: Allow access using Apple Remote Desktop
    This help page will provide you with some other useful resources for Apple Remote Desktop -
    Remote Desktop Help
    Thanks for using Apple Support Communities.
    Best,
    Brett L 

Maybe you are looking for