We paid our business partner to update us from the 2018 version to the 2019 version.  I normally don't have the new release installed until we're past R1, but I really wanted (need) the Global Search facility.  It's there, it opens, but when I search nothing happens -- no data returned.  Is this something that can be fixed, or is this (as others have theorized) Sage rushing out a release that wasn't ready to go?

Did you do what I mentioned in a prior post - do not use the refresh - enter the text and press enter ?????

As I have said mine works perfectly.

I don't even see a refresh button.  Yes, I entered the text and pressed enter -- and nothing happened.  It just sat there.

Something's wrong with this feature, it either works perfectly, or doesn't work at all, with nothing in between.  I installed in on a brand new, clean 32 bit Windows7 VM. I see the GlobalSearch service running, there are no event log errors, but nothing happens when you press Enter.  Either it's not compatible with Windows 7, or there's some service or DLL that I'm missing.  If I press the Refresh button, I get an app crash with this error at the top "Unable to access the registry ODBC.INI key to access the ODBC Data Source information"

I also have it installed on Win 7.  Enter does nothing.  Refresh gives a warning that it will take several minutes, but I'm only searching for "Black" in SAMINC.  After clicking OK, I get the app crash but different error than Jay's.  Mine begins with "unhandled exception..." at the top, and "System.ServiceModel.FaultException: The server was unable to process the request due to an internal error." followed by extensive details, including several that refer to location "c:\jenkins\workspace".  I googled that, and it looks like it's a programming error -- but then makes me wonder why it works in certain environments...  Any insights?  

Check the SQL Server ODBC driver on the workstation.  The basic one, not the native client.  I've seen times when the registry entries are partially missing.

Dana 

I found a log in the GS folder, and see this when I search for "black" and press Enter:

2018-09-03 15:11:13,752 [9] DEBUG GlobalSearchWindowService.SearchEngineCore - query: black
2018-09-03 15:11:13,752 [9] DEBUG GlobalSearchWindowService.SearchEngineCore - RequestUrl: localhost:8984/.../select desc,appayment_batch_number desc,apadjustment_batch_number desc,arinvoice_batch_number desc,arrefund_batch_number desc,%0d%0a%20%20arreceipt_batch_number desc,aradjustment_batch_number desc,gljournal_batchnumber desc,icreceipts_receiptnumber desc,icshipments_shipmentnumber desc,icinternalusage_internalusagenumber desc,%0d%0a%20%20icadjustments_adjustmentnumber desc,ictransfers_documentnumber desc,oeorder_ordernumber desc,oeshipment_shipmentnumber desc,oeinvoice_invoicenumber desc,oecreditdebitnote_documentnumber desc,%0d%0a%20%20porequisitions_requisitionnumber desc,popurchaseorder_ponumber desc,poreceipts_receiptnumber desc,poinvoices_invoicenumber desc,poreturns_returnnumber desc,pocreditdebitnote_documentnumber desc,%0d%0a%20%20item_number desc,customer_number desc,account_formattednumber desc,&rows=10&start=0
2018-09-03 15:11:15,874 [9] ERROR GlobalSearchWindowService.SearchEngineCore - Fail to query the engine
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8984
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at GlobalSearchWindowService.SearchEngineCore.Query(String query, Int32 pageNumber, Int32 pageSize, String company, String userName, String password, IList`1 sortFieldOrder, IList`1 filterFieldOrder, String targetEngineUrl) in c:\jenkins\workspace\build-gs-32-Sage300-2019\source\app\base\GlobalSearchWindowService\SearchEngineCore.cs:line 94

So, it's sort of looking like an IIS problem?

Nah, it's not IIS, it's the GlobalSearch engine, it can't see itself.

Getting this error now:

So this might be an Internet Explorer/TLS kind of configuration fix.  Dunno yet...

Mine does not have iis enabled - it is a test SQL server and test Win7 workstation, with no web screens.  But I have the same text you highlighted above in my log file, including address 127.0.0.1:8984.  We can live without it for now, but for many users, this is the only appealing new feature so it sure would be nice if it worked!

Check the SQL server odbc to see if its working.  Not the native client.  The basic one.

Classic odbc works perfectly.

Classic odbc works perfectly.

ditto