Hi Michael,
I have some tips to solve the problem.
At first, you don't have to configure any NMEA port in GPS Controller. (That's for other applications on older devices, or to output coordinates, but not for AP). So I rather uninstall this app and reset the device. Sometimes GPS Controller's and GPScorrect's settings can mix up the device...
Anyway, using AP+GPScorrect you don't have to set up any GPS port settings, because GPScontroller automatically does it when you press Activate GPS in ArcPad. It recognises your device and knows which port to open and protocol to use. (See Juno's User Guide, page 61.)
You use GPScorrect to be able to use real-time corrections and log data for post-processing, don't you? So why should you use NMEA protocol instead of TSIP? When you use NMEA protocol, you're unable to receive any real-time corrections within AP or to log for post-processing... (However, you can log corrected data using NMEA, BUT only if your receiver corrects data internally and output these corrected data via NMEA to your application...Hope it's not confusing :D)
Anyway, if you use ArcPad without GPScorrect, the correct settings on GPS tab: COM4 @ 4800 baud. You don't have to use GPS Controller to configure, because it is preconfigured on Juno!
(On older devices GPS Controller automatically removed itself when another controller sw was installed. Trimble should've kept this funcionality on newer devices...)
And another trick - just to totally mix you up 😉 -, you can use the FindGPS command (black spy-glass icon) on GPS tab to automatically search for GPS and to configure settings.
To the SQL Server Compact Edt error: It's because you didn't installed/deployed this application to the device in conjunction with AP. (It's not compulsory, but you need this to use advanced functionality of AXF files, like related tables, and so...)
Hope this helps.