Bcaaa 1306 Error
Contents |
Security ProxySG These Support Forums are read only. To register for an account please click the Sign Up button
Event Id 1221 Bcaaa
and complete the registration form. Forums Performance August: 90% of new threads checktokenmembership() failed; status=87:0x57:the parameter is incorrect. were responded to within 3.3 days. Announcement Collapse No announcement yet. ProxySG and BCAAA problem Collapse X Collapse
Checktokenmembership Failed Bcaaa
Posts Latest Activity Search Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: event id 1306 redundancy lost Clear All new posts c0rec0re Junior Member Join Date: Dec 2013 Posts: 27 #1 ProxySG and BCAAA problem 02-17-2014, 12:13 PM Suddenly I faces strange problem. ProxySG stopped serve users, browser will endless load any website. I have 2 proxysg in failove cluster. Web-interface of proxysg works fine. I made master 2nd node of cluster and it worked for a while (about 10 or 15 minutes) and then also stopped working. Reboot of proxysg solves that and then again after a while it stops serve users. That was strange. I made policy trace and found this error in trace of my test request: user: unauthenticated EXCEPTION(authentication_failed): Authentication failed either because credentials were not provided or they could not be validated url.category: Search Engines/Portals@Blue Coat I started to check BCAAA servers and found on primary error messages Event Type: Error Event Source: BCAAA Event Category: (1) Event ID: 1306 Date: 2/11/2014 Time: 3:41:51 PM User: N/A Computer: BCAAA Description: [916:640] len=596 B64BlobReq='XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXX'; status=87:0x57:The parameter is incorrect. where XXXXX is some request, that I removed from quote. It's some blob text. Event Type: Error Event Source: BCAAA Event Category: (1) Event ID: 1306 Date: 2/11/2014 Time: 3:41:51 PM User: N/A Computer: BCAAA Description: [916:640] ver=130 tId=5cb18 PLType=4 PLLen=76 Seq=5cb18; status=87:0x57:The parameter is incorrect. Event Type: Error Event Source: BCAAA Event Category: (1) Event ID: 1306 Date: 2/11/2014 Time: 3:41:51 PM User: N/A Computer: BCAAA Description: [916:640] AcceptSecurityContext fai
is not an error.300Various messagesThe associated message warns about an unexpected condition that does not prevent operation.400Various messagesThe associated message describes an error condition that prevents normal operation.1001Authentication Agent service started: port=# threads=# socket=0x# process id=# agent version=# ProxySG version=#This indicates successful startup and provides information about the agent.1002Authentication Agent stoppedThis indicates normal shutdown of the service.1003ProxySG (a.b.c.d) connected; Process # spawned as #This indicates a ProxySG has connected to the agent (Windows only).1004ProxySG agent process exited (normal logout)This https://forums.bluecoat.com/forum/security-policy-enforcement-center/proxysg/397-proxysg-and-bcaaa-problem indicates normal logout by a ProxySG.1005Process %d has terminated, ExitCode=0x#, link=0x#This indicates an unexpected termination of an agent process (Windows only).1006Service dispatcher exited.This indicates an unexpected termination of the service dispatcher.1007CreateNamedPipe failed, pipe='%s'The agent dispatcher could not create the named pipe for the reason given.1008ConnectNamedPipe failed, pipe='%s'The agent process could not obtain the http://bluecoat.force.com/knowledgebase/articles/Solution/BCAAAEventIDexplanations information from the dispatcher on the named pipe for the reason given.1009WriteFile failed, pipe='%s'The dispatcher could not write information to the named pipe for the reason given.1011CreateThread (ProcessTimerThread) failedThe dispatcher could not create its timer thread.1012Failed to create ProxySG process '%s'The BCAAA server does not have the same version of BCAAA available as the ProxySG is expecting.1019VariousThe dispatcher was unable to determine the exit status of an agent process.1020Terminating ProxySG process #, ProcNum=# Handle=0x#An agent process was active when the Windows service was shut down.1022VariousThe associated message reports the status of a ProxySG login attempt.1101BasicAuth: CloseHandle failed; user 'xx\\xx'The agent was unable to close the login handle for the specified user.1102Username: '%s\\%s' too longThe ProxySG offered the specified username, which is too long.1106VariousAn attempted authentication using BASIC credentials failed for the reason given.1107User Right 'Act as part of the operating system' required for Basic AuthenticationThe agent does not have the necessary privileges to do BASIC authentication1108VariousThe agent
Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows https://community.spiceworks.com/windows_event/show/1805-bcaaa-1306 Events Event 1306 (Error) Source: BCAAA How important is this event? http://etherealmind.com/bcaaa-bluecoat-performance-speed-capacity/ (0 votes) 1 2 3 4 5 not important very important Description This Windows Event does not have a description yet. Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS event id ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages No messages to display. Comments No comments yet. Add your comments on this Windows Event! Join the IT Network or Login. Stats Reported 7 years ago 0 Comments 2,894 Views Other sources bcaaa 1306 error for 1306 BINLSVC Server Administrator Others from BCAAA 1221 2206 2001 400 2102 1012 1403 1313 See More IT's easier with help Join millions of IT pros working smarter and faster together COMMUNITY STATS 200K+ 10K+ 5M+ Product Reviews How-tos & Scripts Posts Connect with OR Join - It's Free Have an account? Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your email address First Name Last Name Email Join Now or Log In Email Password Log In Forgot your password? Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. By creating an account, you're agreeing to our Terms of Use and our P
Operation Basics Tech Notes Network ZEN OSX Books You are here: Home / Blog / Operation / Blue Coat / Performance of Blue Coat BCAAA agent for authenticationPerformance of Blue Coat BCAAA agent for authentication 11th February 2008 by Greg Ferro A common question in the Blue Coat forums is about the server specification for the BCAAA and how many users can be supported. While I am not sure sure about the performance that Blue Coat recommends I can tell you my experiences. I understand that according to Microsoft the Domain Controller should be able to handle 6000 parallel authentication requests, so presumably Microsoft can handle the authentication performance. Small to Medium Site I would say that for up to 1000 users, a Pentium 4 (any type), with 512MB RAM running Windows XP is more than enough. I recommend using VMware (the free version) so that you can use the snapshot features to perform upgrades and to give you a simple roll back plan. You should have at least two machines for high availability. You will not notice any CPU use, and memory will hardly be used. Large to Very Large I have used the BCAAA in a very large site with more than 50000 users in a global network, with multiple AD trees, distributed across many servers. A very large MS AD site indeed. We had the BCAAA agent installed on two Quad Core Xeon with 2GB RAM with Server 2003 Standard in separate data centers and at full load I did not see the CPU move above 3 percent. I think that even then it was the virus software causing the load. Observations From what I determine, BCAAA is a proxy software agent that receives the authentication request from the ProxySG and then uses a Windows Authentication API to verify the credentials. If successful, it sends back a success message, if not a it sends failure message. It doesn't need a lot of CPU or memory to do this and it is very fast. Most importantly, it is fully compliant with NTLM authentication, so it provides a transparent authentication to the user. Whereas, when you use AD authentication, every element of a web page will needs authentication and Windows does not allow caching of such a request (at least without some configuration). Therefore almost every Blue Coat ProxySG installation will use the BCAAA agent for authentication. Related Posts & ArticlesTech Notes: CheckPoint Firewall Cluster XL in 2014What Makes Network Appliances Fast ?Are SDN Controllers a Security Risk ?Server Performance, Network Agents, Software Routers and…The End of WHOIS ?Filed