Osstatus Error 9844
can not post a blank message. Please type your message and try again. SKHofDFW Level 1 (0 points) Q: What is the cause of OSStatus error -9844? My news reader started throwing this after a restart when connecting to NNTP servers. Any help appreciated. Mac Pro, Mac OS X (10.6.8) Posted on Feb 12, 2012 4:40 PM I have this question too Close Q: What is the cause of OSStatus error -9844? All replies Helpful answers by X423424X,★Helpful X423424X Feb 12, 2012 5:15 PM in response to SKHofDFW Level 6 (14,237 points) Feb 12, 2012 5:15 PM in response to SKHofDFW From my research on this it may be SSL related. Has your NNTP server changed is settings requirements? Now using SSL and you are not or vice versa? IP changes? Helpful (1) Reply options Link to this post by SKHofDFW, SKHofDFW Feb 12, 2012 6:33 PM in response to X423424X Level 1 (0 points) Feb 12, 2012 6:33 PM in response to X423424X Have contacted the application vendor and came up with the same conclusion. The really weird part is that the application was fine just twenty minutes earlier. Thanks for the info. Helpful (0) Reply options Link to this post This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use. Support Apple Support Communities Shop the Apple Online Store (1-800-MY-APPLE), visit an Apple Retail Store, or find a reseller. Apple Info Site Map Hot News RSS Feeds Contact Us Copyright © Apple Inc. All rights reserved. Terms of Use Updated Privacy Policy Cookie Usage
inHidden fieldsSearch for groups or messages
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site http://stackoverflow.com/questions/7809848/asycnsocket-not-connecting-to-tcp-serial-port-over-wifi About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up AsycnSocket not connecting to osstatus error TCP serial port over wifi up vote 0 down vote favorite I have an iPhone app that I run on the simulator. XCode ver 3.2.6/4.3. I am trying to communicate with a radio on a serial port of a PC over wifi, both on the same server... I've tried NSStream and GCDAsyncSocket (just to make sure). The radio has its own IP address and port osstatus error 9844 number. It's actually a TCP/IP wifi module. After changing the remote access on the PC to accept my IP address, I am finally able to connect but I get kicked off immediately, I'm assuming it's when I try to read or write. Same happens when using Telnet, connects then disconnects. The radio issues HELLO when someone connects, so Telnet must try to read since data is sent. I'm guessing. I thought since I am able to connect, I should be able to read/write. (Yes, newbie here) I would appreciate any thoughts or direction. I've been researching for over a week now and going bonkers. Thanks. I added the code below as well as the error message. This is the error message: socketDidDisconnect:withError: "Error Domain=NSOSStatusErrorDomain Code=-9844 "The operation couldn’t be completed. (OSStatus error -9844.)" UserInfo=0x4c38a60 {}" - (IBAction)performConnection:(id)sender { asyncSocket = [[GCDAsyncSocket alloc] initWithDelegate:self delegateQueue:dispatch_get_main_queue()]; NSError *error = nil; uint16_t port = [[[self serverPort] text] intValue]; if (![asyncSocket connectToHost:[serverAddr text] onPort:port error:&error]) { DDLogError(@"Unable to connect due to invalid configuration: %@", error); [self debugPrint:[NSString stringWithFormat:@"Unable to connect due to invalid configuration: %@", error]]; } else { DDLogVerbose(@"Connecting...IP:%@, port:%i", [serverAddr text], port); } } - (void)socket:(GC