Bluetooth open connection error 60

i did simple connection between labview and my phone to use my labtop as headset but still give me error 60
so please help me to solve this error
Attachments:
3-24-2011 10-56-00 AM.png ‏7 KB

Hey FullOption,
You need to set up your bluetooth connection before you can call it. There is an excellent Knowledge Base article on Developing Bluetooth Applications with LabVIEW. That will help get you started. Good luck!
~kgarrett
Applications Engineer
National Instruments

Similar Messages

Heart beat could not open connection, error code 110

Hi, where can I find error codes for NFR and NSM?
I have problems with some agents connecting to the engine:
2/17/2010 16:02:55 EngineInterface: Heart beat could not open connection, error code 110
Both engine and agent runs on the same server (10.236.19.147):
AgentNCP Service Config
Host Address: 10.236.19.147
Service Ports: HTTPS: 3037 HTTP: 0
Data Path: /var/opt/novell/filereporter/agentncp
Debug Logging: Enabled
Heartbeat: 60 seconds
Engine Address: 10.239.19.147:3035
Use SSL: Yes
Alternate Hostname: huanovellfs1
Engine Service Config
Host Address: 10.236.19.147
Service Ports
Client HTTPS: 3033 HTTP: 0
Agent HTTPS: 3035 HTTP: 0
Data Path: /var/opt/novell/filereporter/engine
Debug Logging: Enabled
Heartbeat: 60 seconds
DSI Address: 10.236.19.89:8009
Use SSL: Yes
Scans per Volume: 2
Another OES2 server connects fine to the engine, butI have a Netware agent, which also fails to connect:
Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open connection.
NFR is 1.0.0
Thanks for any input.
Istvan

Hi Istvan! Sorry for the delay in our response! we are in the process
of building a list of error codes for everyone! in the meantime the 110
means the following:
// Couldn't create a new network interface
#define CC_STATUS_CCS_CANT_CREATE 110
Is this an NSM integration installation?
Also, remove the alternate hostname.
If you don't mind, let's move this support issue to
filereporter"@"novell.com!
Thank you!
icseke wrote:
> Hi, where can I find error codes for NFR and NSM?
>
> I have problems with some agents connecting to the engine:
>
> 2/17/2010 16:02:55 EngineInterface: Heart beat could not open
> connection, error code 110
>
> Both engine and agent runs on the same server (10.236.19.147):
>
>
> AgentNCP Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports: HTTPS: 3037 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/agentncp
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> Engine Address: 10.239.19.147:3035
> Use SSL: Yes
> Alternate Hostname: huanovellfs1
>
> Engine Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports
> Client HTTPS: 3033 HTTP: 0
> Agent HTTPS: 3035 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/engine
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> DSI Address: 10.236.19.89:8009
> Use SSL: Yes
> Scans per Volume: 2
>
> Another OES2 server connects fine to the engine, butI have a Netware
> agent, which also fails to connect:
>
> Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open
> connection.
>
> NFR is 1.0.0
>
> Thanks for any input.
>
> Istvan
>
>

Failed to open connection error message on Crystal Server

I have recently upgraded my desktop to Windows 7. Crystal Reports XI Developer works fine on this new system as it did on my earlier Vista system. I can create and run reports with no problems on each of these system using Developer.
The problem I am experiencing is this: when I publish, using the Publishing Wizard, a report on my Crystal Server using my Windows 7 system, the report does not work. Instead, the error message: 'Failed to open connection' appears from Crystal Report Viewer.
If I open the same report using my Developer license on my old Vista machine and then re-save it, I can publish it to my CR Server and it runs successfully.
ODBC is used on all systems and all appear to be 32 bit versions, albeit different version numbers.
This problem can be repeated with any of the many reports currently in use.

HI Don,
Let's see if I understand what you're saying:
When a report is created on a legacy desktop in CR Developer, the ODBC connection on that computer works with direct access to the SQL Server 2008 on my Windows Server 2003 R2 system. I can then also publish these using the Publishing Wizard to the CRS these same reports and they run successfully; no connection issues, works great.
However, when a report is created on my 64 bit Windows 7 desktop in CR Developer, the ODBC connection on that computer also works well with direct access to the SQL Server 2008 on my Windows Server 2003 R2 system. BUT, when I then publish these using the Publishing Wizard to the CRS these same reports do NOT successfully connect to the database and that is when I get the Crystal Viewer message about the connection failed.
So, I would assume then that Crystal Server on my Windows Server 2003 system is similar enough to older MDAC criteria on legacy systems but different enough my Win7 desktop to introduce the problem even though Developer on that same Win7 system works fine directly against the SQL DB.
If this is all correct, then I either need a legacy MDAC to work on my Win7 system, or an updated MDAC\WDAC for Crystal Server to use.
By the way, I'm using ODBC and here are some details from the Component Checker:
Server:
             MDAC 2.8 SP2 on Windows Server 2003 SP2
Desktops:
             MDAC 2.8 SP1 on Windows XP SP3 - on an XP machine that works fine
             UNKNOWN on Vista (but it works fine with CRS)
             UNKNOWN on Windows 7 - (doesn't work with CRS - must be a different UNKNOWN than on Vista)
Thanks for your assistance as this is rather important -
Bob.

Unable to open connection error

Hi All,
   I have a report that is connecting to two ODBC DSN connections. Using Crystal Reports 2008 it opens fine and generates reports (we did this even on the Crystal Server using CR 2008).
   When we load this report onto the Crystal Reports Server 2008 Server and try to open it using InfoView, it gives a message "Unable to open connection". Does anyone have any ideas to get it to work on the CR Server 2008? It is a very basic report with 2 ODBC connections. The driver for the ODBC connection is installed on the Server and was tested successfully with Crystal Reports just not with Crystal Reports Server 2008.
   Thank you in advance.

Used System DSN instead of User DSN

Windows 8.1 Bluetooth LE connection error

I've built a Bluetooth LE HID device which is a combined keyboard, mouse, and consumer device. All OS's can connect to it fine...except Windows 8.1,
on all hardware. It connects and pairs, but then appears to fail perhaps when parsing the HID descriptor (I'm guessing here). It then displays 'Driver Error' and disconnects from the device.
Only the keyboard appears in Printers and Devices with a warning. In properties it states there is a 'PnP error'.
I enabled Driver Verifier, so when I connect now I get a BSOD `driver_verifier_iomanager_violation`
Doing a analysis of the memory dump I get:
* Bugcheck Analysis *
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
call to IoMarkIrpPending.
Arg2: fffff8040090aa50, The address in the driver's code where the error was detected.
Arg3: ffffcf819e230bd0, IRP address.
Arg4: 0000000000000103, Status code.
Debugging Details:
BUGCHECK_STR: 0xc9_24c
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c
FAULTING_IP:
nt!ViGenericInternalDeviceControl+0
fffff804`0090aa50 4c8b05b117c8ff mov r8,qword ptr [nt!pXdvIRP_MJ_INTERNAL_DEVICE_CONTROL (fffff804`0058c208)]
FOLLOWUP_IP:
BTHUSB!BthUsb_AsynchCallUsbd+5b
fffff801`0ffdd65f 8bd8 mov ebx,eax
IRP_ADDRESS: ffffcf819e230bd0
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from fffff804008fa6b0 to fffff804003c5aa0
STACK_TEXT:
ffffd000`e24836a8 fffff804`008fa6b0 : 00000000`000000c9 00000000`0000024c fffff804`0090aa50 ffffcf81`9e230bd0 : nt!KeBugCheckEx
ffffd000`e24836b0 fffff804`008fd171 : fffff804`008ed470 fffff804`0090aa50 ffffcf81`9e230bd0 00000000`00000103 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`e24836f0 fffff804`008f3bd2 : ffffe001`165f3f40 ffffd000`e2483850 ffffe001`166b0b30 00000000`00000000 : nt!ViErrorFinishReport+0x10d
ffffd000`e2483750 fffff804`008f9bd5 : 00000000`00000000 fffff804`0090aec9 ffffe001`165f3f40 00000000`00020000 : nt!IovpCallDriver2+0x33e
ffffd000`e2483b20 fffff804`008ee928 : ffffcf81`9e230bd0 00000000`00000002 ffffcf81`9e230bd0 00000000`00000000 : nt!VfAfterCallDriver+0x289
ffffd000`e2483bb0 fffff804`0090aec9 : ffffcf81`9e230bd0 ffffe001`15303410 00000000`00000002 ffffe001`165f3f40 : nt!IovCallDriver+0x3e4
ffffd000`e2483c00 fffff804`008ee911 : ffffe001`15303560 ffffcf81`9e230bd0 fffff804`00395bd8 fffff804`0034fa7c : nt!ViFilterDispatchGeneric+0xd1
ffffd000`e2483c40 fffff801`0f806989 : ffffcf81`9e230bd0 fffff801`0ffdd65f fffff804`00395bd8 ffffe001`15dadde0 : nt!IovCallDriver+0x3cd
ffffd000`e2483c90 fffff801`0ffdd65f : ffffcf81`93704f00 ffffcf81`8374ab98 ffffcf81`844eaed0 ffffcf81`8374ab98 : VerifierExt!IofCallDriver_internal_wrapper+0x71
ffffd000`e2483cd0 fffff801`0ffdb9f8 : ffffcf81`93704f00 ffffcf81`844eaed0 ffffcf81`844eaed0 ffffcf81`8374aaa0 : BTHUSB!BthUsb_AsynchCallUsbd+0x5b
ffffd000`e2483d10 fffff801`0ffdbc48 : ffffcf81`93704f00 ffffd000`e2483dd0 ffffcf81`844eaed0 ffffcf81`844eaed0 : BTHUSB!BthUsb_SendTransferUrb+0xe8
ffffd000`e2483d50 fffff801`0ffdaf65 : ffffcf81`8f214fb8 ffffcf81`8374aaa0 ffffcf81`8f214fb8 ffffcf81`8374aaa0 : BTHUSB!BthUsb_WriteAclData+0x234
ffffd000`e2483e00 fffff801`12ca338b : ffffcf81`8f214fb8 ffffd000`e2483f40 ffffcf81`8d1e0ba0 ffffcf81`91184480 : BTHUSB!BthUsb_HciWrite+0xc1
ffffd000`e2483e40 fffff801`12ca3a3c : ffffcf81`91184480 ffffcf81`91184480 00000000`00000000 ffffcf81`8d1e0ba0 : bthport!HCI_SendNextAclWrite+0x943
ffffd000`e2483ff0 fffff801`12ca3cb6 : ffffcf81`9c702ed0 ffffcf81`8897af80 ffffcf81`91184480 00000000`0000001b : bthport!HCI_QueueOrStartAclWrBip+0x15c
ffffd000`e2484070 fffff801`12cf1b8d : ffffcf81`9322cc10 ffffcf81`8d1e0c30 ffffcf81`9c702ed0 ffffd000`e2484140 : bthport!HCI_WriteAclData+0x16e
ffffd000`e24840f0 fffff801`12ce2db5 : ffffcf81`9c702fbc 00000000`c0000225 ffffd000`e24841e9 00000000`00000000 : bthport!L2CapInt_SendFixedCIDData+0xf1
ffffd000`e2484140 fffff801`12ce2381 : ffffcf81`9322cc10 ffffcf81`9322cc10 fffff801`12d0e660 fffff801`12ce2278 : bthport!L2capCon_ProcessPostConnect+0x131
ffffd000`e2484250 fffff801`12cad868 : 00000000`00000000 ffffcf81`8d1e0c30 ffffcf81`9322cc28 ffffcf81`9322cc00 : bthport!L2CapCon_HciConnectCallback+0x109
ffffd000`e2484300 fffff801`12cb3c7d : 00000000`00000000 00000007`8033ec0c ffffcf81`8d1e0ba0 00000000`00000000 : bthport!HCI_CxnCallClientCallback+0xb0
ffffd000`e2484380 fffff801`12ce3069 : ffffcf81`00000000 00000007`8033ec0c ffffcf81`91184480 ffffcf81`9322cc10 : bthport!HCI_CreateConnection+0x2f5
ffffd000`e2484420 fffff801`12ce66f6 : 00000000`00000000 ffffcf81`97ea0d58 ffffcf81`9322cc10 fffff801`12d0e660 : bthport!L2capCon_CreateHciConnection+0xb5
ffffd000`e24844a0 fffff801`12ce6c54 : ffffcf81`96570a20 ffffcf81`9322cc10 ffffcf81`96570a20 ffffd000`e24845b8 : bthport!L2CapCon_ProcessNextSignalRequest+0x1a6
ffffd000`e2484560 fffff801`12c941ce : ffffe001`15311db0 ffffd000`e2484680 ffffcf81`97ea0d58 00000000`00000020 : bthport!L2CapInt_HandleSignalRequest+0x158
ffffd000`e2484600 fffff801`12c9299c : ffffe001`00000078 ffffe001`171cf301 ffffe001`15311c60 ffffe001`15311c60 : bthport!BthDispatchBrb+0xcda
ffffd000`e24846c0 fffff801`12c928bb : ffffcf81`96570a20 ffffe001`171cf310 00000000`00000000 00000000`00000103 : bthport!BthHandleInternalControl+0xdc
ffffd000`e2484720 fffff801`0f80d572 : ffffe001`15311c01 ffffe001`15311c60 ffffd000`e24847b0 fffff801`12c9279c : bthport!BthDispatchInternalControl+0x11f
ffffd000`e2484780 fffff804`008ee911 : ffffcf81`96570a20 00000000`00000002 ffffe001`16155f10 ffffcf81`8a348f00 : VerifierExt!xdv_IRP_MJ_INTERNAL_DEVICE_CONTROL_wrapper+0xfe
ffffd000`e24847e0 fffff804`0090aec9 : ffffcf81`96570a20 ffffe001`200fa4d0 00000000`00000002 ffffe001`15064510 : nt!IovCallDriver+0x3cd
ffffd000`e2484830 fffff804`008ee911 : ffffe001`200fa620 ffffcf81`96570a20 fffff804`00395bd8 ffffe001`15033310 : nt!ViFilterDispatchGeneric+0xd1
ffffd000`e2484870 fffff801`0f806989 : ffffcf81`96570a20 fffff801`0fabd056 fffff804`00395bd8 ffffe001`154f7f40 : nt!IovCallDriver+0x3cd
ffffd000`e24848c0 fffff801`0fabd056 : 00000000`00000005 ffffd000`e2484948 ffffcf81`97ea0d58 ffffcf81`97ea0d58 : VerifierExt!IofCallDriver_internal_wrapper+0x71
ffffd000`e2484900 fffff801`12dba9b0 : ffffcf81`97fb8fc0 ffffcf81`9013ae60 ffffcf81`8b3dae70 00000000`0041400b : Wdf01000!imp_WdfRequestSend+0x156
ffffd000`e2484960 fffff801`12dbb1f1 : ffffcf81`97ea0d58 0000307e`7952b0a8 0000307e`6fec5198 ffffe001`15033310 : BthLEEnum!BthLEEnumSendBrbAsync+0x118
ffffd000`e2484a00 fffff801`12dbbc92 : 00000000`00000000 ffffd000`e2484ab1 00000000`00000017 ffffcf81`9013af70 : BthLEEnum!BthLEEnumSendFixedCIDData+0xd5
ffffd000`e2484a40 fffff801`0fadbd00 : ffffcf81`7f678e00 00000000`00000000 ffffcf81`7f678e00 00000000`00000002 : BthLEEnum!BthLEEnumRootDeviceInternalIoControl+0x2c6
ffffd000`e2484b10 fffff801`0fab7d80 : fffff801`0fb2c300 ffffcf81`9013ae60 ffffcf81`7f678c20 0000307e`6fec5198 : Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x4c
ffffd000`e2484b50 fffff801`0fab7123 : 00000000`00000200 fffff801`0fb2c100 ffffcf81`94d1ef02 ffffd000`e2484d40 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x570
ffffd000`e2484c20 fffff801`0faefc60 : ffffcf81`7f678c20 00000000`00000000 00000000`00000000 00000000`00000001 : Wdf01000!FxIoQueue::DispatchEvents+0x363
ffffd000`e2484ce0 fffff801`0faef94e : ffffcf81`9544ac00 ffffcf81`9544ac20 ffffd000`e2484d70 ffffcf81`9013af90 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1ec
ffffd000`e2484d40 fffff801`0fb4486b : 00000000`00000000 ffffcf81`9013ae60 ffffcf81`9013ae60 fffff801`0facfbd0 : Wdf01000!FxIoQueue::ForwardRequestWorker+0xee
ffffd000`e2484db0 fffff801`0fb20976 : 0000307e`809873d8 ffffd000`e2484e40 ffffcf81`7f678c20 00000000`00000041 : Wdf01000!FxIoQueue::ForwardRequestToParent+0xeb
ffffd000`e2484de0 fffff801`12dc16fa : 00000000`00000000 0000307e`710e1518 ffffe001`15030000 ffffcf81`9706ef00 : Wdf01000!imp_WdfRequestForwardToParentDeviceIoQueue+0x1ae
ffffd000`e2484e70 fffff801`0fadbd00 : ffffcf81`9544ae00 0000307e`6fec5198 0000307e`6fec5198 00000000`00000017 : BthLEEnum!BthLEEnumDevicePdoIoInternalDeviceControl+0x5aa
ffffd000`e2484f10 fffff801`0fab7d80 : fffff801`0fb2c300 ffffcf81`9013ae60 ffffcf81`9544ac20 0000307e`6fec5198 : Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x4c
ffffd000`e2484f50 fffff801`0fab7123 : 00000000`00000200 fffff801`0fb2c100 ffffcf81`9750cf02 ffffd000`e2485150 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x570
ffffd000`e2485020 fffff801`0fac3279 : ffffcf81`9544ac20 ffffcf81`9013ae00 00000000`00000000 ffffd000`e24851c9 : Wdf01000!FxIoQueue::DispatchEvents+0x363
ffffd000`e24850e0 fffff801`0fabbd93 : ffffcf81`96570a00 ffffcf81`9013ae60 ffffcf81`96570a20 ffffcf81`96570a20 : Wdf01000!FxIoQueue::QueueRequest+0x8d
ffffd000`e2485150 fffff801`0f80d572 : 00000000`00020000 ffffd000`e2485200 ffffcf81`8ef1eae0 fffff801`0fabb240 : Wdf01000!FxDevice::DispatchWithLock+0xb51
ffffd000`e2485230 fffff804`008ee911 : ffffcf81`96570a20 00000000`00000002 ffffe001`169ae960 ffffe001`15413880 : VerifierExt!xdv_IRP_MJ_INTERNAL_DEVICE_CONTROL_wrapper+0xfe
ffffd000`e2485290 fffff804`0090aec9 : ffffcf81`96570a20 ffffe001`161af040 00000000`00000002 ffffe001`160d36e0 : nt!IovCallDriver+0x3cd
ffffd000`e24852e0 fffff804`008ee911 : ffffe001`161af190 ffffcf81`96570a20 fffff804`00395bd8 ffffd000`e2485401 : nt!ViFilterDispatchGeneric+0xd1
ffffd000`e2485320 fffff801`0f806989 : ffffcf81`96570a20 fffff801`0fabc711 fffff804`00395bd8 ffffe001`14c8a320 : nt!IovCallDriver+0x3cd
ffffd000`e2485370 fffff801`0fabc711 : ffffd000`e24855f0 ffffd000`e2485449 ffffcf81`901d6e70 ffffd000`e2485449 : VerifierExt!IofCallDriver_internal_wrapper+0x71
ffffd000`e24853b0 fffff801`0fada89c : 00000000`00000000 ffffd000`e2485500 00000000`00000001 00000000`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x191
ffffd000`e24854b0 fffff801`0fb32f48 : fffff801`12dd0000 ffffcf81`901d6e70 ffffcf81`9706efe0 fffff804`008efece : Wdf01000!FxIoTargetSendIoctl+0x1e4
ffffd000`e2485760 fffff801`12ddd63e : 02680284`028402a0 ffffd000`e2485830 00000000`00000280 00000000`00000000 : Wdf01000!imp_WdfIoTargetSendInternalIoctlSynchronously+0x48
ffffd000`e24857c0 fffff801`12de327c : 00000000`00000000 00000000`00000000 ffffd000`e24858e8 fffff801`12dd4f10 : BthLEEnum!BthLEEnumDeviceFdoSendAttDataSync+0x11a
ffffd000`e2485850 fffff801`12de2fe0 : 00000000`00000000 ffffe001`14745310 00000000`00000007 00000000`0000ffff : BthLEEnum!BthLEAttSendPduOneWayInternal+0x160
ffffd000`e24858b0 fffff801`12de1e3e : ffffd000`e2485a90 ffffd000`e24859a9 00000000`0000ffff 00000000`00000000 : BthLEEnum!BthLEAttSendPduTwoWay+0xa8
ffffd000`e2485920 fffff801`12de5415 : 00000000`00000000 00000000`00000000 ffffd000`e2485b00 00000000`00000000 : BthLEEnum!BthLEAttReadByGroupType+0x146
ffffd000`e2485a00 fffff801`12de48b1 : ffffe001`14745310 ffffe001`00000000 00000000`00000000 ffffd000`e2485c08 : BthLEEnum!BthLEGattGetServicesInternal+0x231
ffffd000`e2485b70 fffff801`12ddc49d : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`00000000 : BthLEEnum!BthLEGattThoroughRun+0x17d
ffffd000`e2485c00 fffff801`0facb242 : ffffcf81`7f61ea50 ffffd000`e2485db0 fffff801`0fb58ba0 00000000`00000000 : BthLEEnum!BthLEEnumDeviceFdoD0Entry+0x21d
ffffd000`e2485c50 fffff801`0fac7268 : 00000000`00000000 ffffd000`e2485db0 fffff801`0fb58c80 00000000`00000000 : Wdf01000!FxPkgPnp::PowerD0Starting+0x32
ffffd000`e2485cb0 fffff801`0fac765a : ffffcf81`7f61ea50 fffff801`0fb589c0 ffffcf81`7f61ea50 fffff801`0fb589c0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x138
ffffd000`e2485e00 fffff801`0fac73df : 00000000`00000000 ffffd000`e2485ef0 ffffcf81`7f61ec50 00000000`00000504 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xc6
ffffd000`e2485e80 fffff801`0facb062 : 00000000`00000000 ffffcf81`7f61ea50 00000000`00000501 ffffd000`e24860b0 : Wdf01000!FxPkgPnp::PowerProcessEvent+0xef
ffffd000`e2485f20 fffff801`0fac6c74 : ffffcf81`7f61ea50 ffffd000`e2485fc0 00000000`00000500 fffff804`0034f920 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
ffffd000`e2485f50 fffff801`0fac7069 : ffffcf81`7f61ea50 00000000`00000001 ffffcf81`7f61ea50 00000000`00000001 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0xf4
ffffd000`e2485fe0 fffff801`0fac6dd8 : 00000000`00000000 ffffd000`e24860d0 ffffcf81`7f61ed28 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x1df
ffffd000`e2486060 fffff801`0facd022 : 00000000`00000000 ffffe001`16877040 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x10c
ffffd000`e2486100 fffff801`0fac5942 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff804`0034f920 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9e
ffffd000`e2486140 fffff801`0fac5a5a : ffffcf81`7f61ea50 ffffcf81`7f61eb00 ffffcf81`7f61ea50 ffffcf81`7f61eb00 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x102
ffffd000`e24861d0 fffff801`0fac5bc4 : 00000000`00000000 ffffd000`e24862c0 ffffcf81`7f61eb80 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0xc2
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: BTHUSB!BthUsb_AsynchCallUsbd+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BTHUSB
IMAGE_NAME: BTHUSB.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 545054f8
BUCKET_ID_FUNC_OFFSET: 5b
FAILURE_BUCKET_ID: 0xc9_24c_VRF_BTHUSB!BthUsb_AsynchCallUsbd
BUCKET_ID: 0xc9_24c_VRF_BTHUSB!BthUsb_AsynchCallUsbd
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc9_24c_vrf_bthusb!bthusb_asynchcallusbd
FAILURE_ID_HASH: {dedf9404-a46e-32ea-628e-5dcde5ffdf19}
Followup: MachineOwner
Using Windows Message Analyser I was able to find the following error:
MessageNumber: 1004 Type: Microsoft_Windows_Bluetooth_BthLEEnum.Event_435Device (mac address removed) is not Compliant with the Bluetooth Core Specification: previous attribute was a (Characteristic), current attribute is a (Descriptor).
I'm not sure what characteristic or descriptor this is referring to. Is there any way I can find out? Any other suggestions how I can figure out this problem?

Wrong forum?

Opening Connection Error

When I try to open a connection in version 1.5.3 Build MAIN-5783, I get:
bq. C:\Oracle\OraHome_1\BIN\ocijdbc11.dll: The specified procedure could not be found.
I have this file, and it's in the path named in the error message.
Here's what's changed recently in my Oracle configuration:
I have the Oracle 11g client installed, but I just installed a 10g client so I could get the java Enterprise Manager Console. Could that have clobbered something SQL Developer needed?

I tried moving the application, so there are no spaces in the path, and executing from a bat file that contains:
set ORACLE_HOME=%CD%
start C:\SQLDeveloper153\sqldeveloper\bin\sqldeveloper.exe
The application launches fine, but, when I try to open a connection, I'm still getting the same message:
C:\Oracle\OraHome_1\BIB\ocijdbc11.dll: The specified procedure could not be found
Have I followed your insructions correctly?
What else can I try?
How do I reset the oracle home?

Having trouble opening connections and reading from Bluetooth devices.

Hello,
As the title states, I am having trouble opening connections and reading data from a Bluetooth device. We are using a PDA to communicate with LabVIEW. First, the Bluetooth Open Connection VI displays a timeout error half of the time. Second, when it does open, it does not read what the PDA is sending. Third, if it does allow an open connection, it will not do it a second time unless the devices are turned off.
I also have another related question. I am using a Linksys Bluetooth USB adapter, and the driver is proprietary. Labview requires the use of a Microsoft driver, and we are having problems going back and forth between the drivers. What Bluetooth receiver would you suggest using? The reason I ask is the fact that you have Bluetooth examples of client VI's. Therefore, you must use a similar device. Thank you for your time.
-Jon

Hi Jon,
I'm not sure what Bluetooth receivers were used to verify the functionality of the VIs. However, I still want to help you solve your issue. Please make sure that you are running the shipping examples and let me know what version of LabVIEW, what PC OS and what PDA OS you are using. Does the Microsoft driver work for your Bluetooth receiver if you uninstall the Linksys driver?
With your answers I'll do my best to help you out.
- Philip Courtois, Thinkbot Solutions

ORA-30678: too many open connections with UTL_MAIL.send

I'm have just recently started getting the ORA-30678: too many open connections error while calling the UTL_MAIL.send procedure to send emails via a pl/sql package. The call is made within a loop and there can be a significant number of calls made to this procedure. In fact, I received this error over 1400 times within the last three days. This was previously working until I made a change to the processing which now results in a larger number of emails/calls to this procedure. I don't see any documentation on how (or if) I can close the connection with UTL_MAIL.
I'm using Oracle 11g. Any insight would be much appreciated.
Thanks,
Teri

Looks like a bug possibly, check out this MOS Note:
Ora-30678: Too Many Open Connections From UTL_MAIL [ID 788442.1]
The bug note says it was fixed in 11.2. Not sure which version of 11 you are running.
Edited by: Centinul on Apr 26, 2010 2:07 PM

Too Many open connections. UTL_HTTP

I am submiiting The URL for multiple times.
So i am getting the too many open connections error. How to avoid the code.
For your reference i have attached my code.
DECLARE
req   UTL_HTTP.REQ;
resp UTL_HTTP.RESP;
value VARCHAR2(1024);
url   VARCHAR2(4000);
OPT   varchar2(1000);
CURSOR MOB IS SELECT MOB FROM MOBILE_NUMBER;
BEGIN
-- UTL_HTTP.SET_PROXY('proxy.my-company.com', 'corp.my-company.com');
FOR I IN MOB
LOOP
DBMS_OUTPUT.PUT_LINE(I.MOB);
URL:='http://www.meru.co.in/wip/sendsms?username=11|'&'||'password=11|'&'||'to='||I.MOB||'&'||'message=this%20is%20shanmugam';
DBMS_OUTPUT.PUT_LINE(URL);
req := UTL_HTTP.begin_REQUEST(url);
UTL_HTTP.SET_HEADER(req, 'User-Agent', 'Mozilla/4.0');
resp := UTL_HTTP.GET_RESPONSE(req);
UTL_HTTP.READ_LINE(resp, value, TRUE);
    DBMS_OUTPUT.PUT_LINE(value);
END LOOP;
UTL_HTTP.END_RESPONSE(resp);
EXCEPTION
WHEN UTL_HTTP.END_OF_BODY THEN
    UTL_HTTP.END_RESPONSE(resp);
END;how to close the connection for each record????
Can anyone help me out in this??
Thanks in Advance.
Cheers,
Shan

Move UTL_HTTP.END_RESPONSE(resp); inside the loop. I mean
UTL_HTTP.END_RESPONSE(resp);
END LOOP;

TCP active open: Failed connect() Error: Connection timed out SMTP

Hi,
Messaging server version is,
./imsimta version
Sun Java(tm) System Messaging Server 6.2-6.01 (built Apr 3 2006)
libimta.so 6.2-6.01 (built 11:20:35, Apr 3 2006)
SunOS bglbbmr1-a-fixed 5.9 Generic_118558-28 sun4u sparc SUNW,Sun-Fire-V440
17-Dec-2008 10:47:40.08 1730.8e.741
tcp_local Q 4 [email protected] rfc822;[email protected] [email protected] /mta/queue/queue/tcp_local/013/ZUg0i1t9I0ZG~.00 <[email protected]>; TCP active open: Failed connect() Error: Connection timed out SMTP/xyz.my-domain.in
I have been getting this above error on my mail server from last
4-5 days. I am getting complaints from end users that the users can't
send any mails using Outlook but I did check with my test user I can
send mail by using webmail.
The Failed MX lookup Errors also getting in my logs the error detail given bellow.
17-Dec-2008 10:47:39.65 1730.91.737
tcp_local - Y TCP|0.0.0.0||209.85.143.114|25 SMTP/airtelmail.in/aspmx.l.google.com
17-Dec-2008 10:47:39.92 1754.41.255
tcp_notify - Y SMTP/infomedia18.in/infomedia18.in
17-Dec-2008 10:47:39.92 1754.41.256
tcp_notify Q 7 rfc822;[email protected] [email protected] /mta/queue/queue/tcp_notify/017/ZXg0i1t3U_ZoD.00 <[email protected]>; Failed MX lookup; try again later
17-Dec-2008 10:47:39.94 1754.41.257
tcp_notify Q 6 rfc822;[email protected] [email protected] /mta/queue/queue/tcp_notify/010/ZXg0i1t3U_ZoF.00 <0KBZ003MRGU7MQ30@my-domain> Failed MX lookup; try again later
I tried stopping and starting msg service using stop-msg and start-msg to sort out this above problem but no result. :(
When I do check the tcp_local queue it has been growing every day as well the tcp_notification queue also.
/opt/SUNWmsgsr/sbin/imsimta qm su
Messages
Channel Queued Size (Kb) Oldest
tcp_notify 10741 1080610.61 16 Dec, 00:59:24
tcp_local 8334 733849.31 15 Dec, 00:19:00
tcp_lmtpcn 0 0.00
tcp_be 0 0.00
reprocess 0 0.00
process 0 0.00
conversion 0 0.00
Totals 19075 1814459.92
This queues are increasing day by day.
One more thing is that I cant see a service/channel called CONVERSION running on my server when i do use this command.
ps -aef | grep conversion
root 6144 6000 0 11:14:28 pts/1 0:00 grep conversion
When i try to start it using imsimta qm utility, output shows as
qm.maint>; start conversion
QM-I-STARTED, channel was not stopped
qm.maint>;
Later I stopped and started conversion channel
qm.maint>; stop conversion
QM-I-STOPPED, channel stopped
qm.maint>; start conversion
QM-I-STARTED, channel started
qm.maint>;
I can see that on other servers the conversion channel is running and few msges are in queue. I do have other servers which running the same messaging server. But I am not getting why don't on this server. Where both servers having the same configuration.
Please, help me to sort out this issue.
Thanks in advance....
BSK

Thanks Mr. Shane,
The server which is running conversion channel.
ps -eaf|grep conversion
mailserv 16824 8472 3 17:08:11 ? 0:48 /opt/SUNWmsgsr/lib/conversion
mailserv 28728 8472 0 17:17:30 ? 0:00 /opt/SUNWmsgsr/lib/conversion
root 1057 26387 0 17:18:12 pts/1 0:00 grep conversion
more /opt/SUNWmsgsr/config/conversions
in-channel=*; in-type=application; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=x-zip-compressed; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=image; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=audio; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=video; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
Following entry from /opt/SUNWmsgsr/lib/config-templates/imta_tailor
IMTA_CONVERSION_FILE=<msg.RootPathUNIX>/config/conversions
The server which doesnt show running conversion channel
#more /opt/SUNWmsgsr/config/conversions
!in-channel=*; in-type=*; in-subtype=*; in-disposition=*;
! parameter-symbol-0=NAME; parameter-copy-0=*;
! dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
! message-header-file=2; original-header-file=1;
! override-header-file=1; override-option-file=1;
! command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=application; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=x-zip-compressed; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=image; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=audio; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
in-channel=*; in-type=video; in-subtype=*; in-disposition=*;
parameter-symbol-0=NAME; parameter-copy-0=*;
dparameter-symbol-0=FILENAME; dparameter-copy-0=*;
message-header-file=2; original-header-file=1;
override-header-file=1; override-option-file=1;
command="/opt/SUNWmsgsr/private/virusscan.sh"
Following entry from /opt/SUNWmsgsr/lib/config-templates/imta_tailor
IMTA_CONVERSION_FILE=<msg.RootPathUNIX>/config/conversions
Is this above information u r asking?
As u wrote erlier, the conversion channel works some times and some times doesn't work.
Thanks lot...
BSKADAM

Failed to open the connection error using Business View OLE DB

I have a Crystal Report built on a Business View with the db being accessed by an OLE driver. Everything works fine using Crystal Designer, but when I try to access it through BOE I get the "Failed to open the connection" error. I have the ole drivers installed on the server.
We are on BOE 12.1.0.
The db is IBM as400.
Suggestions??

Ok so I spent the day trying to find the differences between the working and the non-working application. I began by adding code one piece at a time to the working application. The goal was to try and get it to break on the deployment server. I found the lines of code that is causing the break on the deployment server. Here it is:
    private void setReportParameters()
        try
            crystalReportDocument.SetParameterValue(0, reportUserName.Value);
            crystalReportDocument.SetParameterValue(1, reportArea.Value);
            crystalReportDocument.SetParameterValue(2, reportCDR.SelectedValue);
            crystalReportDocument.SetParameterValue(3, reportStatus.Value);
        catch (Exception ex)
            throw ex;
This sub-routine is called from my button click code and is used to set the parameters for the report. Once I added this to the working application it broke also. My goal here is to send the parameters to the report from a form the user is filling out. Please keep in mind this code works in Visual Studio 2005 and my local IIS server running on my development machine. It breaks on the target deployment server
The code broke on reports with sub-reports as well as report with no sub-reports. As soon as it was added and deployed the application through the "Failed to open the connection" error.
Thoughts?

SpamAssassin / Amavisd tuning - TCP active open: Failed connect() errors

I started this post as we were experiencing a problem with occassional delayed mail delivery to our mail store. As I continued writing it, I think that I've resolved it. But I wanted to post this anyway so if I'm doing things right it might help someone else; or, if I'm doing something wrong someone can correct me. :) For reference, we have a quad Sun v440, and process about 500,000 messages a day.
We were seeing messages like this in our log files:
09-Nov-2006 08:28:09.37 tcp_scan Q 1 [email protected] rfc822;[email protected] @tcp_scan-daemon:[email protected] TCP active open: Failed connect() Error: Connection timed out
example.com represents our local domain. The errors seemed to occur proportionally to the amount of incoming mail we received. That is, we saw more of them under load.
We are running SpamAssassin, Amavisd/clamav, and:
Sun Java(tm) System Messaging Server 6.2-5.01 (built Nov 22 2005)
libimta.so 6.2-5.01 (built 11:57:57, Nov 22 2005)
SunOS hostname 5.9 Generic_118558-11 sun4u sparc SUNW,Sun-Fire-V440
This line seems to say that the message is in the tcp_scan channel, and cannot send to 127.0.0.1:10024 (amavisd) because that port isn't listening.
My amavisd max_servers was set at 15. After reading http://www.ijs.si/software/amavisd/amavisd-new-magdeburg-20050519.pdf and making a wild guess, I increased it to 30. The errors were less frequent, but still occurred.
The output of 'sar -d' showed that my local disk was experiencing upwards of 80% utilization. I moved the amavisd temp directory and the spamassassin bayes db to a san volume, and that sped everything up dramatically. The connect errors went away, clamav avg time per message is at 4 seconds down from 10. I am now receiving errors from spamassassin that say:
Nov 9 10:27:27 hostname.example.com spamd[21601]: prefork: server reached --max-children setting, consider raising it
My --max-children is set to 25 right now, and the server is cpu bound under heavy load, so I see no reason to raise it.
So this is my setup. I am no longer having an immediate problem, but comments/questions are welcome.
Config files related to my setup are below.
Excerpts of imta.cnf:
! tcp_scan
[] $E$R${tcp_scan,$L}$U%[$L]@tcp_scan-daemon
! ims-ms
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 2 pool IMS_POOL destinat
ionspamfilter1 fileinto $U+$S@$D
ims-ms-daemon
! tcp_local
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL saslswitchchannel tcp
auth maytlsserver maysaslserver missingrecipientpolicy 0 aliasdetourhost tcpscan-daemon
tcp-daemon
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL allowswitchchannel saslswitchchannel tcp_auth
maytlsserver maysaslserver missingrecipientpolicy 4 aliasdetourhost tcp_scan-daemon
tcp_intranet-daemon
! tcp_scan
tcp_scan smtp single_sys subdirs 5 notices 1 backoff "pt10m" "pt30m" "pt2h" "pt4h" dequeue_removeroute maxjobs 7 pool SMTP_POOL daemon
[127.0.0.1] port 10024
tcp_scan-daemon
option.dat:
SPAMFILTER1_LIBRARY=/opt/sunjes/SUNWmsgsr/lib/libspamass.so
SPAMFILTER1_CONFIG_FILE=/opt/sunjes/SUNWmsgsr/config/SpamAssassin
SPAMFILTER1_STRING_ACTION=data:,require ["addheader"]; addheader "Spam-test: $U"; require "fileinto"; fileinto "Junk";
SPAMFILTER1_OPTIONAL=1
dispatcher.cnf:
[SERVICE=SMTP-SCAN]
DEBUG=-1
PARAMETER=CHANNEL=tcp_scan
PORT=10025
IMAGE=IMTA_BIN:tcp_smtp_server
LOGFILE=IMTA_LOG:tcp_scan-server.log
STACKSIZE=2048000
INTERFACE_ADDRESS=127.0.0.1
SpamAssassin:
host=127.0.0.1
port=783
debug=0
mode=1
field=
verdict=Junk
USE_CHECK=0

Suggest dropping Amavis in preference to the built-in
integration, per our documentation. Simpler, more
performant.Sorry, my title wasn't very accurate. We are running SpamAssassin through the built in integration, and clamav through amavisd. There isn't any built in integration to clamav, is there?

TCP active open: Failed connect() Error: Connection timed out

Hi,
There is one message which can't be delieved to the recepient with error " TCP active open: Failed connect() Error: Connection timed out" This is the error that we found in the mail.log_current file.
I have no problem sending email to the same address from my hotmail account.
any suggestion ?
Thanks,
Joe

The message can only mean one thing. Your server cannot connect to that host.
It's possible that the remote system is lying to your Messaging Server, and that's gotten it confused. Some firewalls do this by repeating the entire capability string from the server behind them, but can't actually handle all the capabilities.
PIX firewalls do this.
When you connect, they pretend to be able to "startls", but if you try, they hang up. They appear to handle "EHLO", but when you try, they hang up.
You can put debugging on the tcp_local channel, and see the actual conversation, if you like.
master_debug and slave_debug go into the imta.cnf definition line. MM_DEBUG=5 goes at the end of your option.dat file.
then
imsimta cnbuild
imsimta restart
will attempt to send the message. You will want to back the changes out, as you'll get lots of extra log files you really don't need.
Post the log file, and we can see what's happening.

I cant open my icloud its says connections error how can ı do connect?

please help my father take my ipad and ı have an important email and ı thing go to www.icloud.com and ı write an apple ID and Paswor but connections error when icloud page can be opened ?
THANKYOU FOR ALL ABAUT THİS

Hi jasmin,
Did you read what Demo wrote? He wasn't saying he had a problem. He was responding to the OP who had a problem, and was providing a solution. Follow what Demo said to do....
Cheers,
GB

Error in Crystal report( built on Universe) preview in CMC - Failed to load DB credentials or Failed to open Connection

Hi,
      I created a Crystal Report (CR XI r2) using Universe and database is Db2.
     My report is working fine in Crystal report ,.But when i am uploading this report (Save AS ->enterprise) to repository ,and then trying to preview this report from CMC/Infoview,it throws error "Failed to load DB credentials "or sometimes it throws" Failed to open Connection" .
I have given DB user credentials correctly and used both option "prompt user for DB logo" as well as "use same database logon" .
I am not sure why it is throwing this error.I checked both "Bo server machine as well as Client machine ,both are having DB2 cleint installed and configured.
Is this an issue with Service Packs ?
As my machine configuration is -
     BO Client - BO XI R2 RTM + SP1+SP2
     BO Server (Linux) - BO XI R2 RTM
If anybody faces the same issue ,please share the solution with me,as it is very urgent .
Thanks
Nitin

Hello,
Thank you for your post.
Based on your description, your issue is out of support of VS General Question forum which mainly discusses
WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
I suggest that you can consult your issue directly on SAP Crystal Reports:
http://scn.sap.com/community/crystal-reports/content?filterID=content~objecttype~objecttype[thread]
  for better solution and support.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Bluetooth open connection error 60

Similar Messages

Maybe you are looking for