taner91xp

Hello bicky, How you make connection with PowerShell to Net2 Database? Could you please guide me? And what should be syntax for deleting users without expiration date and users with expired validity before 2022? I also found this option: Export all users form Net2 in excel, manipulate all users. And import them back after changes. But here for me the missing part is, how to delete all users from Paxton net2 without affects other Groups, Access levels, Doors and other Net2 configurations. AN1011-AE.pdf

I did find Net 2 Query V4.10.0 but with this software, I could do only read queries. I am not able to delete anything. I Installed also SQL Management Studio but I don't know how to connect to NET2 SQL database, I don't know how to authenticate me with which user and name.

Hello all, Could you tell me how you procedure with your inactive users in the Paxton Net2? If access of one user is expired do you delete it or you keep it in the system? If you keep it how long time do you keep it before delete it? What is the best practice to keep clean the database? 2 months and more I am not able to do the integration Suprema with Paxton Net2. Finally the issues is identified. Paxton net 2 has limitation of 10 000 tokens. We have 8193 users in our system. After sync with Biostar2, Biostar2 adds new token to every one user in the system. And if we multiply 8193 by 2 we will have 16 000 + tokens in Paxton after sync but the limit in Paxton is 10 000 and for this reason integration is not possible. [TABLE=width: 547] [TR] [TD=class: xl65, width: 547, colspan: 6]The status of users are: 1877 users are inactive with expired access. 4286 users are inactive without expiration date but without any tokens but in notes is described as inactive, just the procedure of operators to keep them for anyway.... And only 2030 users are active really. Theoretically if we have only 2030 users in the system after sync with Biostar 2 we could multiply 2030 users by 2 or even 3 and in the end we will have 4000 + or 6000 + tokens and we will be under the limit of 10 000 tokens and the integration should be fine. What do you think? Also, do you know a way how I can delete all users with expired date before 2022? And how can I delete these 4286 without an expiration date? I know for these users only that they don't have any tokens and in the field Memo in user information is written for when the access is granted and when is stopped, for example this is in the Memo: 10.05.2016, expired 19.10.2016 I didn't find a way is it possible from SQL? I didn't have SQL credentials. Is it possible with tools or form front end? Is it possible Paxton to provide some way to do that? Thank you in advance for your opinion. [/TD] [/TR] [/TABLE]

Hi Supportman, Thank you for the information. We will wait for support from them to see what will happen. But we bought Suprema products and it’s late to return them. I started to think for splitting the management of the door into two as a workaround . One side with exit button from Paxton Net2 and the other side from BioStar2 with Suprema device. I imagine it in this way I am not sure is it possible before testing but I hope that it will be possible to connect two systems to the lock mechanism parallel. Then management will be complicated to support two system with two databases for the same user without sync only manually to providing access to to the door. For example, we could connect exit button to the Paxton net 2, Paxton net 2 to the lock mechanism of the door, BioStar2 to the Biolite device, Biolite device to the relay, relay to the lock mechanism. Hire is appearing one question will we have issue with this connectivity from electricity point of view? What do you think, as senior could you please share your opinion? And in the worst scenario for this door we could implementing in both sides only Suprema management and control of the door without Paxton net2. It’s not seriously to advertising and announcing of possibility for full integration of Suprema with Paxton net2 but in the reality it is not possible I am really disappointed from Suprema at the beginning….. their Dev team should be able to solve issues like this for their customers when they sell these products as compatible with Paxton… I will share more information when we done with the support ticket. Thank you for your time and attention to the topic.

Hi Supportman, I am devastated to hear that about Suprema.We chose them because an employee from Paxton Net 2 advised us.I am surprised to hear about your experience.How was the support from the Suprema side in your adventure? Did they pay attention to your cases? Did they find any solutions when using Suprema devices? Best Regards.

I did re-format the text. It's a adventure of a few years...

Hello, Do you have an issue with the integration of Suprema with Paxton Net2? Has anyone here had experience with Suprema issues? I opened a case to Suprema and I am waiting to receive support. I could share the story: The Paxton Net 2 has 8140 users with card and fingerprint biometric tokens. For Biometric fingerprints Ievo is integrated with Paxton Net2. This integration was created 10-15 years ago. The Ievo Physical devices are too old and with hardware issues and often I have to make reboots of them physically. In the latest upgrades of Paxton Net 2 Ievo integration is crashed. To escape from this issue we left the upgraded version of Paxton Net2 only on the server, on client machines we installed the old version of Paxton Net2, and Ievo fingerprint enrollment was recovered. But time by time Net2 clients started to crash too often. Close application start application and etc... We contacted Ievo support and they confirmed that in new versions of Paxton Net2 their integration is not supported, and their alternative solution was buying from them software called Ievo ISYNC. We didn't buy it.We contacted Paxton Net2 support and they said that they can't help. We asked them what vendor could we choose for biometric authentication which will be stable and well integrated with their Paxton Net2. They advised us to use Suprema products 2 years ago. Today we purchased and received Suprema Biolite N2 and BioMini Slim 2. For testing purposes we clonned the production Paxton Net2 server. We tried to integrate Suprema but without success, the curent version of Net2 is with unstable API. For this reason we upgraded Paxton net 2 to the latest version. We tried again, this time integration was fine. For Suprema integration we need Paxton Net2 server, Suprema integration Software, Suprema Biostar2 Server. Suprema Integration Software 2.2.6. Biostar2 version is 2.9.7.41. Paxton Net2 version is 6.8.14711.5051. In Paxton Net 2 we use OEM Client account to connect Net2 to Suprema integration software. In Paxton Net2 we activate API License which is free and receivde oficially from Paxton support.In Paxton Net2 we install Suprema integration software. We install new Server 2019 where we instal Biostar 2. In Suprema Integration software we make connection to Paxton Net2 and to Biostar2. Now we connect physically Suprema BioLite N2 to Paxton Net 2 plus controller using Wiegand wiring described in their configuration. D0 and D1 (Green D0 and white D1 wire from Biolite N2. also Gray wire for ground) we connect these wires to Paxton net2 plus controller in D0, D1 and 0V outputs in reader 2. We make wiegand configuration in Paxton Net2 Utility. In Biostar2 we do registering of BioLite N2 and we make wiegand wiring configuration described in their documentation. Now we try to do fingerprint enrollment and we do it successfully through Paxton Net2 client. The Biolite N2 receive the fingerprint and do sync of user in Paxton net2 in Biostar2. To here great, well, super, awesome, perfect. But we noticed that in Paxton Net2 no information for biometric fingerprint or token created during Finger print enrollment using Suprema Bioline N2 through Paxton Net2. When we try to open Paxton Net2 plus door with Suprema Biolite N2 using fingerprint authentication we see on the events error invalid token, because in the user not exist biometric token in Paxton Net2. If you think it could happend more worst than this you will be right. We replaced Suprema Integration 2.2.6 with 2.3.2 version.But nothing is changed. We started users sync between Biostar2 and Paxton Net2, it taked 2 days, all 8140 users are synced to Biostar2 but the sync didn't stop, it continued in a loop without end, one user was synced with Biostar2 three times in a one day. In the end Biostar2 crashed with high CPU usage and Low memmory. Paxton Net2 was affected too, now you are not able to add manually new token in users and you are not able to do fingerprint enrollment because you are not able to save the scanned biometric fingerprint. Also Biolite N2 also crashed with syncerror regarding reaching maximum card nuber limitation. The great part is that thi everything is happening in test environment. I don't wanna think how it will be if this happening in production environment. Now I wait Suprema support to answer regarding this case and issue. If you have experience with Suprema could you please share your experience? Note we did remove Ievo integration also but without any help. Thank you in advance.

Hi, I would like to inform you that if you use Ievo devices integrated with Paxton be carefully! In the latest version of Paxton Net2 the ievo integration doesn't work! Especially with this version and build 6.6.12017.4376! I don't understand why Paxton hide this issue, but I didn't find any release note or information about this issue! It's hard to open communication with Paxton Net2 support directly if you are not customer of their partner but in the past I was successfully reach them using their official email, today this is not possible, their official support email is filtered to white list, where are only partners and their internal employees. I did find unofficial way to contact someone from NET2 but I don't receive much information, only that they know for the issue and the advice was to contact Ievo. We contacted Ievo, they confirmed that it's a Paxton Net2 issue and Paxton usually recommends to their customers downgrade. Also Ievo provide new their own integration Isync which is compatible with the latest versions of NET2 but it's paid and need license. Finally my colleague did find sollution: Server could be 6.6.12017.4376! But the clients should be 6.06.11130.2638! In this combination client server Ievo integration works! I hope that this information will help someone.

Hi, thank you for the information. I have another question. Do you have any issues with biometric readers after upgrading to the latest version? We use IEVO controllers and IEVO readers for biometric tokens. The IEVO controllers are IP based. When I try to take new biometric finger print from menu Token Add Biometric the NET2 client stuck in not responding state and later the Net2 is closed automatically. This is the error in event viewer: Faulting application name: Net2.exe, version: 6.6.12017.4376, time stamp: 0x62fccd3fFaulting module name: OLEAUT32.dll, version: 10.0.19041.985, time stamp: 0xfc8f0d5bException code: 0xc0000005Fault offset: 0x0007043cFaulting process id: 0x5be8Faulting application start time: 0x01d950de23f98e7eFaulting application path: C:\Program Files (x86)\Paxton Access\Access Control\Net2.exeFaulting module path: C:\Windows\System32\OLEAUT32.dllReport Id: 069f22f2-69cf-498d-9ab3-9bcc67ae6b87Faulting package full name: Faulting package-relative application ID: Do you have any one bad experience with Ievo and the latest Paxton upgrade? The issue is happened after upgrade of NET2 server and clients. The previous version where the Ievo was okay is 6.1.8616.3794 in remote location A and 6.2.8928.4090 on remote location B , the current version on both locations is 6.6.12017.4376.

Hello, I did see here a few Paxton NET2 topics. I would like to ask you did you have any issues with NET2 classic and NET2 Plus controllers? My issue now is that when I want to check the firmware status of all controllers a lot of controllers on field firmware show unknown. My Paxton version is 6.6.12017.4376 Pro. I suspect that some of the controllers are with different hardware version. I did two times upgrade and this unknown status didn't cleared on the controllers. The interesting part is that during upgrade I see how firmware is uploaded and installed but in the final I am not able to see the current firmware version, I only see unknown state. Please keep in mind that the controllers work fine. It's like cosmetic bug. It's appeared after a few upgrades before and not cleared. Do you have any information ? Thank you in advance for your attention regarding the topic.