After my hard drive failed in my iMac, I rebuilt the system using my MacBook and then booted my MacBook off the external drive to check everything out first. I reinstalled 1Password so that I could enter passwords as I was rebuilding things. I also enabled Unlock with Apple Watch and Touch ID.
I believe it is trying to unlock 1Password with my Apple Watch and/or Touch ID, however my iMac (Retina 5K, 27-inch, 2017) - does not support Touch ID. Going into Settings > Security, there are no settings for Apple Watch and Touch ID. My MacBook at the same 1Password level has them above Auto-lock in the security settings.
I suspect that 1Password does realize I do not have Touch ID on my iMac and is not showing the security settings for that reason, however it is already set somewhere and it is trying to use Touch ID to unlock the iMac anyway, which of course fails, and that is the reason for the message.
I can't recall if I was able to unlock 1Password with my Apple Watch before my internal drive failed, but that is not even an option now as I said and no indication that 1Password is attempting to unlock with the Apple Watch.
Hoping this might explain the problem that I see others have experienced, where this message appears, and lead to a fix or at least a circumvention. Maybe there are property files somewhere which if I delete them it will fix the problem.
I'm sorry that you're unable to unlock 1Password on your Mac. I know how important it is to be able to access 1Password and the team and I are here to help. So that I can better understand the situation can you please tell me the following:
I am able to unlock 1Password. My issue is just the message that comes up each time I start 1Password or if 1Password locks and I open it again. The issue was also mentioned in the discussion -screen-shows-that-didnt-work-message-on-startup
Thank you for clarifying. I see that the issue being discussed in that thread is still open with our development team. If you're willing to send one, then a diagnostics report would help us investigate further:
master9.teamviewer.com is resolving to 178.77.120.106 because that is in your hostfile. Check one of the working computers you have access to, hopefully they can ping master9.teamviewer.com and have it resolve to a different (closer) IP.
Otherwise, can you enable and use LAN connections? Just use your IP address instead of a TeamViewer ID. This will help determine if there is someting wrong with your TeamViewer install or your access through your router\firewall.
i am using google dns and teamviewer v12 never worked for me but v11 is still running excelent.. my pc is resolving the same dns ip's like whoer.net lookup for every masterx subdomain.. On my windows server it's the same problem..
Network and Sharing Center > Change adapter Settings > Right click on the connection > Propieties > IP V4 Protocol to see what DNS that computer was using, and did the same thing on mine to put the same DNS. You can also do that by cmd command.
1. yesterday, I was working on one of my client's computers and Windows was asking for the administrator (domain) credentials. The TeamViewer screen blanked and at the client's end, it was waiting for the credentials to be installed. I had to abort doing this remotely because I didn't want to give the client that information. Thus, a trip down to their office.
2 second question, when I restart a workstation, sometimes I'm given the option to reconnect after a restart but most times not. How can I set that so that I always am able to log back in without the client having to re-run the TV program and sending me a new password?
I have no teamviewer entries in my hosts file, nothing blocking it in router, pc firewall is off, my PC DNS matches DNS in router settings, I can ping the master1.teamviewer.com server (and others)... yet still no connection. Any ideas?
1. Add teamviewer and teamviewer service to exclusions in scanning. Then restart pc.
2. Run in command line (as admin):
netsh winsock reset
netsh int ip reset
(then restart) that usually helps and teaviewer starts to connect again.
3. If above doesn't help, I go to network interfaces in device management and then delete lan and wifi interfaces (without deleting drivers) - just delete interfaces and restart pc.
These steps always help to restore teamviewer connectivity.
I tried all above suggestions above to no avail. I inherited my laptop from company that went Bankrupt in July 2018. I think the TV ID: (tied to MAC address?) has not changed and I suspect the TV ID is blocked by teamviewer. If there are actually TV internal support persons here that can help, please email me at [edited by a moderator] and I can send you the TV IF to check internal records. I have used TV in both windows and Linux since 2009 and really enjoyed using it. Thanks everyone for the above suggestions. Very Frustrating problem and support access seems limited without a valid license.
Well, I found out that also Eset Security (NOD32 Antivirus) is blocking Teamviewer, too. I exclude Teamviewer_Service.exe from scanning, restart PC and it's working again. Try that way, too. Maybe some AV is blocking it.
When I started receiving this error, I found that the settings for the Private network were not allowing Teamviewer to connect. It was only allowed on public networks. Allowed private networks and it connected immediately.
All of a sudden i had faced same issue. I went to task manager, deleted all teamviewer processes, and then started teamviewer again. Guess what, it worked. This is just a workaround and not solution but atleast your work won't stop.
This issue didn't start untill last night. I have 3 portal layers (hosted feature layers) that are supposed to update every evening. They didn't update last night. I wasn't aware of this issue till the customer reported that their apps were getting an error that said couldn't add layer to the map. This morning I created a new map image service that works great. The issue alone is with hosted feature layers. All other services that are not hosted feature layers draw just fine.
Here is a rundown of my issues... 1. Hosted feature layers are unable to be added to map. 2. When I go to the rest endpoints for the hosted feature layers I see a list of the layers but when you click on one it goes no further. So it is like they are there but it cant see them. 3. IN any application that uses a hosted feature layer it gets a message that layer can't be added to the map. 4. I can't upload a csv file or anything that I wish to create a hosted feature layer. The error I get states Error While analyzing file. There was an error trying to analyze your file. Please check that file is formatted cortrectly. I have tried this with several different csv files and all produce the same results. 5. I can upload an image. I have no problem doing that. I can also upload using the Add CSV file only option. 6. I validated the datastore and it validated correctly. 7. I checked the federation and it is valid also. 7. I tried adding a hosted feature layer in pro also and this also failed. So this was all working yesterday and it is not working today. They did patch our server last night so I had them roll back the patches and it is still not working. I need to addresss this issue asap and get it working for my end users.
What does the portal log say about the 3 hosted feature services? What about the other hosted feature services work except the 3 hosted feature services we are having trouble with? Also, Have you tried to stop the services and start them manually or restart the portal services?
Appears to be an issue related to connectivity between ArcGIS Server and ArcGIS DataStore. Although, you mentioned datastore is validating correctly. Did you validate through Server Manager or Server Admin API?
First thing I would do is restart the Server and DataStore services, validate DataStore again through Server Manager and check logs if there are any errors. Following that, use the blog below to check that the expected processes are running for each Enterprise component in Task Manager:
I wanted to get this posted for others somewhere - I've had this issue several times over the past three years and the only solution that I have found, after several support tickets with Esri is the answer from @ThienTran above. If an initial restart of each service does not work, then I do it again until it does.
We experienced this as well after Windows Server patching/updates. Data Store service is running, validates with ArcGIS Server, hosted services are started, but they do not load in Portal's map viewer nor in ArcGIS Pro.
This allowed hosted layers to work in Portal now. In ArcGIS Pro 3.1 and 3.2 we had to start with new Projects for the hosted layers to begin working. Existing maps continued to show the same errors, even after re-adding layers/updating sources.
Also wanted to note: This outage has happened twice before. In those instances we ran the Configure ArcGIS Server account and input the same credentials we had used before, and this also solved the issue. Rebooting windows services fixed it for us in this instance but the configure service account might be something to try if that doesn't work.
In one of our test instance (HA) we start and stop the VMs daily (gracefully) - the issue with hosted feature services and hosted 3D scene layers is a common issue. After many attempts, I just stop and start the arcgis service in the gis server and that brings back the hosted feature and 3d scenes without any issue. Initially I followed the steps as above: datastore, server and portal, but it seems the connection issue is just with gis server (at least in our case).
I am facing an issue with my Shopify Advanced site - A few shoppers are getting this error "Your payment details could not be verified. Check your card details and try again" when they enter their credit details. We have contacted our third party payment provider and they are saying that they are not receiving the payment request. We also do not see this order in the Shopify admin. Can you help to share in what scenarios would you display the error "Your payment details could not be verified. Check your card details and try again" so that we can troubleshoot this with our third party payment provider?
c80f0f1006