I have a TAPI Application (Delphi 2007) working on 32bits OSs (XP, Vista, Win7). The TAPI server is 32bits Windows 2003 SP2.
While TAPI APP is running on 64bits OS, I can connect to the line but i cannot get TAPI messages on my App.
I can see messages have arrived on machine through Tracing tapisrv but the WaitForSingleObjectEx to the event handle (returned by lineInitializeEx) is never signaled (always returns WAIT_TIMEOUT).
I've also tried C++ code and 64bits compiler but the 64bits App had the same behavior (except not even starting on 32bits OS :-) ).
Is there any ideas how i can receive the TAPI messages to my App???
EDIT: Well, it seems that only the messages regarding incoming calls are cut. If (while App is running) i execute "tcmsetup /c /d" (=disable TAPI) then i DO receive LINE_CLOSE and LINE_REMOVE messages. Then, if i execute "tcmsetup /c server_name", i DO get the LINE_CREATE message. I can lineOpen the new line provided but still CANNOT get LINE_APPNEWCALL, LINE_CALLSTATE etc
It was a Microsoft bug, after all. For more details and a HotFix, check http://support.microsoft.com/kb/2304914.
What underlying TSP, e.g. cisco.tsp, is your TAPI application connecting to?
Edit: I googled regarding a configuration such as yours and noted this article about a similar issue to the problem you're describing. It seems there is a problem regarding impersonating a user when the remotesp.tsp is involved.
Related
I have universal project targeting Windows Store 8.1 and Windows Phone 8.1 platform.
The windows one works fine but I having trouble running the WP one on an emulator. I get the error message saying:
Microsoft Visual Studio Unable to activate Windows Store app
'numbers-here!App'. The Kiss.WindowsPhone.exe process started, but the
activation request failed with error 'Msg in polish that the app did
not start'.
If this was Windows I would check System Event Log and see the logs just before the error what DLL the system was trying to load and that helped a lot when I was debugging similar problem with Windows Store project, here I have no clue on how to check what exactly was being loaded.
The worst part is that I created package (appx) and checked the dll's being packed with exe, it seems that it includes dependencies that the app explicility uses yet something is still missing and this might be some 'hidden' dependency of one of the other dlls.
Any ideas how to debug such issues with emulator?
For me it was due to having WIC code in my App and/or calling CoCreateInstance in a windows phone environment ( on PC it works flawlessly though )
I ran into the same problem on Windows 10. Turns out, that there is no Kernel32.dll on Windows 10 phone!
Instead you need to link against OneCore.lib which provides the entire Win32 API subset that is supported in UWP. This "umbrella library" will load the correct dlls at runtime.
See also:
https://msdn.microsoft.com/en-us/library/windows/desktop/mt683763(v=vs.85).aspx
I have a user who is running one of my apps, and he is seeing the app crash. How can I get a crash dump from his computer without asking him to use WinDbg?
I have read other questions, and this was easy to do in Windows XP using Dr. Watson, but it seems that option is not available in Windows 8.1 anymore.
Other answer points to c:\Users\[user]\AppData\Local\Microsoft\Windows\WER\ReportArchive directory, but I only see WER files there.
Any idea how to get crash dumps?
Thanks.
I wrote a program to trap WER crash dumps. I was able to use the keys mentioned in this article to trap the dump file locally. The only subtle requirement was that the program had to run with administrator rights. If you follow this methodology, make sure you run the program again to disable trapping crash reports because changing those keys could affect all future crash dumps for other applications.
ProcDump from SysInternals.
Register as the Just-in-Time (AeDebug) debugger. Makes full dumps in c:\dumps.
C:\>procdump -ma -i c:\dumps
First off, I think I've been to every website and forum there is that's discussing this issue and I've tried many different things. I'm at my wits end. This is the dumbest thing and I just want to start coding again!
I'm using Visual Studio Express 2012 for Windows Desktop. I have a x64 project I'm trying to run in Debug mode using the local windows debugger. The only external library I'm using is that of which is required to run DX11.
I attempt to run my program and it freezes. A window pops up saying "A remote operation is taking longer than expected."
I click Terminate and another window pops up asking if I'd like to terminate the remote session. Why yes, I would.
Then it says, "Unable to start program (my path leading to my .exe). The network connection to the Visual Studio Remote Debugger has been closed."
To my understanding, because Visual Studio itself is a 32 bit application, it needs to use the Remote Debugger to compile to x64. Is that correct?
Regardless, I'm still failing to see where that would break down. I've ran several repairs on VS and upgraded to Service Pack 2 (or 1, whichever is the latest).
I've ran a windows repair and uninstalled any VMWare type stuff on my computer. I'm not using a VPN.
I've even copied msvsmon.exe from my laptop (working instance of the project) over to this computer and still no luck.
I'm about ready to Nuke my OS and do a clean install on everything. sigh
Found the problem. It wasn't Windows Firewall like other threads describe. It was my internet filter. I guess it decided to try and block msvsmon.exe because it was using the network. Adding it, along with WDExpress.exe to the application exceptions list did the trick.
Moving from XP to Windows 7 with client side.
Running into a couple issues with Sybase 15.
1) "Interactive SQL" - many widgets in ie options are defective or missing
2) When running simple query get Swing/AVT widget exception error.
Anyone ran into or worked thru any issues moving to 7?
Other versions of the Windows app, but not 7. As you may be aware 7 is only slightly more reliable than Vista.
Those messages are classically due to (a) Sybase Client (SybaseCentral; InteractiveSQL, the GUI utilities) all using the Java VM and (b) that not being successfuly installed.
Get the Sybase Client CD, and install again. Do not Customise, use the Default installation options. Watch the progress for errors. Ensure the JVM installation succeeds. You may have to retrieve any missing files from the Windows 7 CD.
Otherwise open a Support Case.
I know that there are issues with the VFP OLEDB provider on 64 bit machines. ... but what issues do you encounter while actually running a VFP application - on a 64 bit machine? Has anyone had any experience in this area?
My first thought was that it would just run as a 32bit app, without making use of the 64 bit power. However, I ran into difficulties with a FoxPro application connecting to a SQL Server database (probably an OLEDB issue as well). Are there other issues as well?
This is somewhat of a specialized scenario, and it may not be related to 64 bitness, but since you asked...
My organization recently hosted a legacy VFP 7 app on a Windows Server 2008 Enterprise 64 bit server for access over Terminal Services. The app runs fine, but there is some kind of bug with the TS Easy Print technology. When you print from the app to a redirected client printer over Easy Print, the top, left, and bottom sides of each page of the document get clipped. The workaround we use is to have the users print to pdfFactory on the server first, then print from pdfFactory to the redirected client printer over Easy Print. Works great.
This is somewhat of a stab in the dark...but I believe there are some drivers with MDAC that aren't available in x64 windows. I think you may be able to install the normal 32-bit MDAC but it will install to the x86 folder.
We've seen zero problems with our VFP9 apps on 64-bit XP, Server 2003, Vista, or Server 2008.
Our print engine is a VB DLL though, so we wouldn't run into any VFP-specific printing issues.