E71 windows 7 bluetooth "Cannot authenticate the p...

I am using 7.1.51.0 Nokia PC Suite on Windows 7. I have Nokia e71-2. I have latest software on device (410.21.010) using Nokia ovi Suite (2.2.0.245).
Under Device manager->Bluetooth Radios, I have following Drivers versions installed:
Micorsoft Bluetooth Enumerator from Microsoft: 6.1.7600.16385
HP Integerated module with Bluetooth Wireless 2.1Technology from Broadcom: 6.2.0.9000
Using PC Suite when I try to connect to bluetooth, it supplies the pairing code. I hit OK and then enter the pairing code on e71. The pairing seems successsful and I can see my "tjsingh-mobl" laptop on e71 under Menu->Connectivity->Bluetooth->"Paired Devices". I set it as authorized device. However after some time PC Suite tells me that "Cannot authenticate the phone".
I have searched the forum and have failed to find any solution.
I tried the following also but didn't help. There is no "Service Controllers" app on my e71.
Menu > Applications > App. mgr. > Installed apps. > uninstall 'Service Controllers' and 'Contacts Groups DS Plugin' applications.
/t5/PC-and-Mac-Software/PC-Suite-Vista-x64-and-N78-FAIL/m-p/401633/highlight/true#M31457
Can anyone help?

I had this problem too, but the phone got recognized at last after the latest OVI Suite upgrade. Somehow it must have installed some drivers which allowed win7 to recognize and autenticate the phone

Similar Messages

Cannot authenticate the phone - bluetooth

Please help!!!!!!!!!!!!!!!!
I got the error message like "Cannot authenticate the phone" when connecting to my bluetooth device, an BlueSoleil
What happened? Any tips to solv this problem?
Im tired of this **bleep**tt,
have done everything, even reinstall windows xp!
my Phone an Nokia 6680
Bluetooth software product version: Bluesoleil 2.1.3.0 VoIP realase 060429
Operating system:
Microsoft Windows XP
Build 2600
Service Pack 2
Language: English (United States)
Language for non-Unicode programs: Swedish (Finland)
Locale: Swedish
Input language: Swedish
Nokia PC Suite:
Version 6.81.13.0
Language: English
Connectivity Cable Drivers:
Version 6.81.1.2
Microsoft Outlook:
Version 11.0
Build 5510
Bluetooth stacks:
Microsoft Bluetooth stack
Version 5.1.2600.2180
IVT Bluetooth stack
Version InstallMessage Edited by webbis on 06-Sep-2006
09:05 PM
Message Edited by webbis on 06-Sep-2006
09:06 PM

I too had this problem. I could connect, but the final authentication failed. I was able to send files using the bluetooth manager (Toshiba).
This was my solution:
Go to the phone's bluetooth pairing (after you've tried to authenticate). See if your computer's name is there (mine was). Select it, then options and finally 'set as authorized'. And it should work.
There's one strange thing: in the about section there's no mention of the Toshiba BT stack, while in 'Get connected' I get both Toshiba and Microsoft BT stack. I'm not sure which one is being used, but hey: it works!
Some info:
Operating system:
Microsoft Windows XP
Build 2600
Service Pack 2
Language: English (United States)
Language for non-Unicode programs: English (United States)
Locale: Dutch (Netherlands)
Input language: English (United States)
Nokia PC Suite:
Version 6.81.13.0
Language: English
Connectivity Cable Drivers:
Version 6.81.1.2
Microsoft Outlook:
Version 11.0
Build 8010
Bluetooth stack:
Microsoft Bluetooth stack
Version 5.1.2600.2180Message Edited by doctorh on 23-Sep-2006
10:26 AM
Message Edited by doctorh on 23-Sep-2006
10:26 AM

Cannot authenticate the phone : brand new 6085

I have just bought a brand new 6085 and wish to connect via Bluetooth to my laprop ( full details below) . Depsite having a perfect working BlueTooth set up prior to installing PC Suite , I continually get the
'Cannot authenticate the phone'
error message after I have entered the passkey on the phone.
I have spent about 6 hours checking all aspects of BT , which is otherwise working fine.
What is going on? If I can't get a solution promptly, sadly this phone , which in theory is ideal for my needs, is going back to the shop.
Thanks for your help,
Operating system:
Microsoft Windows XP
Build 2600
Service Pack 2
Language: English
Language for non-Unicode programs: English
Locale: English
Input language: English
Nokia PC Suite:
Version 6.84.10.4
Language: English
Connectivity Cable Drivers:
Version 6.84.4.0
PC Connectivity Solution:
Version 7.22.7.1
Microsoft Outlook:
Version 11.0
Build 8118
Bluetooth stacks:
WIDCOMM Bluetooth stack
Version 5.0.1
Build 1200
Microsoft Bluetooth stack
Version 5.1.2600
Build 2180

Cannot authenticate the phone same stupid problem (with settings). please help

"Cannot Authenticate the Phone" with IBM T60 and N...

Hello!
I've been reading through the various posts on the "cannot authenticate the phone" -issue, yet after uninstalling & installing BT stack & PC Suite various times my problem still persists. I've also followed every single piece of instruction I've found on uninstalling Microsoft BT stack, yet PC Suite still reports that it is available.
I can connect from my laptop to the dial-up networking service on the phone, and I am able to connect from the phone to the headset service on my laptop, so BT stack & pairing works ok; I am also able to synchronise the phone via IR => problem must be somewhere in the PC Suite's bluetooth sections.
Is there any flags to enable debugging level logs in PC Suite? I would SOOO MUCH like to see what the hell goes wrong in there.
Or is there *any* way of getting this to work??
Getting pretty tired with this..
Rgrds,
sakuvee.
Operating system:
Microsoft Windows XP
Build 2600
Service Pack 2
Language: English (United States)
Language for non-Unicode programs: English (United States)
Locale: English (United States)
Input language: Finnish
Nokia PC Suite:
Version 6.81.13.0
Language: English
Connectivity Cable Drivers:
Version 6.81.1.2
Microsoft Outlook:
Version 11.0
Build 8010
Bluetooth stacks:
Microsoft Bluetooth stack
Version 5.1.2600.2180
WIDCOMM Bluetooth stack
Version 5.0.1
Build 3200
BT device: Thinkpad Bluetooth with Enhanced Data Rate
BT firmware: Broadcom 2.1.92.108, HCI 2.0 206C, LMP 2.0 415C
BT driver: Broadcom, 1.8.2006, 5.0.1.3200
Phone: V 3.0617.0.6, 03-05-2006, RM-92, Nokia N80 (03)
---Message Edited by sakuvee on 19-Oct-2006
02:46 PM

OK - here's what I did to FINALLY get it working:
1) Uninstall PC Suite (from Add Remove Programs)
2) Uninstall Nokia Connectivity Solution
3) Remove C:\Documents and Settings\[uid]\Application Data\Nokia, ...\\Application Data\[uid]\PC Suite, ...\All Users\Application Data\PC Suite, C:\Program Files\Common Files\Nokia, C:\Program Files\Nokia. Basically all Nokia directories left behind by Nokia uninstallers.
4) Restart machine
5) Run PC Suite Cleaner (all options one at a time, except the diagnostics, don't restart although it recommends to do so)
6) Restart machine
7) Manually clean all typelibs, activex-objects, device-ids and other registry entries linking to or containing Nokia related stuff from registry using regedit.exe
8) Restart machine
9) Install PC Suite
10) Unpair phone (from laptop and from phone)
11) Run Get Connected Wizard

Cannot authenticate the phone

Version 6.86.9.3 of Nokia PC Suite fails with error message:
"Cannot authenticate the phone"
It does not matter what I try (rebooting unpairing/repairing, etc.) it does not work.
The previous version of the software worked fine.
My setup:
Phone: Nokia 6233
Windows 2000 Server
BlueSoleil Bluetooth USB key.
BlueSoleil 2.3.0.1 Release 060802
Stack Version: 05.04.11.20060622
I downloaded a very large update from Nokia, and upgraded for a better experience, however it resulted in a worse experience. I feel very bitter about upgrading.
Do Nokia even monitor these message boards? I've seen others with similar problems but with no solid answers from Nokia other than, "are you sure you plugged it in and paired it properly".

Yes, I have tried your suggestion and it did not work.
I have checked permissions using a sysinternals tools. There are no permission problems, although the following two files were modified during the failed connection attempt.
C:\Documents and Settings\All Users.WINNT\Application Data\PC Suite\ConfServer\Settings.xml
C:\Documents and Settings\All Users.WINNT\Application Data\PC Suite\ConfServer\Nokia;SuiteConf;RM-145;359727000098587.xml
I am curious to see how long it takes Nokia to resolve this error I am getting. I know I'm not the only one... and I'm not going away until it is fixed.

"Cannot authenticate the phone" Nokia 6021

Hello,
I am trying to connect to my phone through Nokia PC Suite using bluethooth dongle but often get this message: "Cannot authenticate the phone". Following is information relevant to my system:
PC Connectivity Solution:
Version 8.22.2.0
[Nokia Connectivity Cable Driver:]
Version 7.0.2.0
Operating system:
Microsoft Windows Vista 32-bit Edition
Language: English
Language for non-Unicode programs: English
Detected Internet browsers:
- Microsoft Internet Explorer 7.0 (Default browser)
Detected Bluetooth stacks:
- Microsoft (Version: 6.0.6000, Build: 16386)
I would appreciate help as my phone memory is full and I want to transfer info to my PC.
Thanks

Hi,
What you can do is donot insert the dongle before switching on the PC. Switch on the PC first, open Nokia PC Suite and then insert dongle (donot try to switch on the PC when dongle is already inserted in the PC) connect your Phone and now try to connect your phone with the PC. If still it fails, why donot you try it using latest Nokia PC Suite 7.0.7.0 ??? Guys i am not 100% if this could help you but still you can try Best of luck.

SEEBURGER AS2: AS2 Adapter failure - Cannot authenticate the user

Hello,
All was working fine but now I got these errors in an AS2 scenario. Sending a message via AS2. Also we don't receive any messages via AS2 anymore. This is the error when sending a message:
Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user., SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Cannot authenticate the user.: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure.
Please advice, many thanks!
Erik

Are you using the "Use Authentication" option in the communication channel? If yes, then ensure that the user provided is correct and is not locked. Also recheck the authentication certificate settings.
Regards,
Prateek

HT1843 hi my bluetooth cannot see the other bluetooth devices. When it is picked up by a different device tries to pair with it but the pairing does not occur. what can I do apart from throwing this **** thing in the bin?

hi my bluetooth cannot see the other bluetooth devices. When it is picked up by a different device tries to pair with it but the pairing does not occur. what can I do apart from throwing this **** thing in the bin?

It isn't supposed to pair with the MacBook. You can use WiFi to connect but not Bluetooth. You can setup a personal HotSpot on the iPhone and connect the MacBook, or setup the MacBook AirPort to create a network and attach the iPhone, and use the USB cable to connect the iPhone to the MacBook for syncing and backup purposes.
The communications are rather limited.

"Windows Backup cannot read the backup destination" when trying to backup to Backup Once to Samba share on NAS

Environment:
Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.
Background:
My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.
I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.
For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.
Problem:
When I try to run the Backup Once operation to test my backup, I get the following error message:
"Windows Backup cannot read the backup destination."
What I've tried:
I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.
Adding the backup user to the Administrators group did not have an effect.
Update 2014-02-18
I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.
However, Backup Once always results in the above error message.
So the problem is confined to the "Backup Once" operation.

Vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'Microsoft File Share Shadow Copy provider'
Provider type: Fileshare
Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
Vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {5636adcf-668c-4761-9f10-93475904c341}
Contained 1 shadow copies at creation time: 2/19/2014 7:00:00 AM
Shadow Copy ID: {4ca86ed5-9da5-49ca-8591-bf56ebd43486}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {aa265dab-feaa-49ed-9b0e-7ed39ab7f9d6}
Contained 1 shadow copies at creation time: 2/19/2014 2:00:00 PM
Shadow Copy ID: {653a4fa5-4d37-4ea4-9d2a-5710b48cde09}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {9180a420-a6bd-490d-85da-8b81231502b9}
Contained 1 shadow copies at creation time: 2/20/2014 7:00:00 AM
Shadow Copy ID: {871d10ee-9034-4269-b841-4aeee9570464}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {d83afc4e-317f-488c-89d5-a0e65844b93e}
Contained 1 shadow copies at creation time: 2/20/2014 2:00:00 PM
Shadow Copy ID: {f6fbb4ff-bac8-4a82-88e8-dffba8656424}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {3774a3f2-cd36-4f36-9667-4f96c0dbe0b3}
Contained 1 shadow copies at creation time: 2/21/2014 7:00:00 AM
Shadow Copy ID: {91d6c61a-8b39-48dd-811d-e0dcf593c967}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {99be106c-a96d-4488-a9ae-6e92452393ee}
Contained 1 shadow copies at creation time: 2/21/2014 2:00:00 PM
Shadow Copy ID: {5bd57dff-0591-4b0f-9ee8-1b8857f59e54}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {299f4ca8-bffa-47b7-9bb2-12358e0282ce}
Contained 1 shadow copies at creation time: 2/22/2014 7:00:00 AM
Shadow Copy ID: {90b732ae-7ea8-4457-8a6d-84983e27b120}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {97225977-6687-4538-b627-1b33985c9ac1}
Contained 1 shadow copies at creation time: 2/22/2014 2:00:00 PM
Shadow Copy ID: {128d7818-ce91-4d35-ad9e-577856d17374}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {b196f043-a073-46e4-baa4-2eb99969cc7e}
Contained 1 shadow copies at creation time: 2/23/2014 7:00:00 AM
Shadow Copy ID: {931780f6-be5e-4ad9-9f4d-151ffd6b1942}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {f24e1101-8505-450c-a802-8ba65e46d8d5}
Contained 1 shadow copies at creation time: 2/23/2014 2:00:00 PM
Shadow Copy ID: {815dff7e-92df-449e-a1ed-eb8e5fa3baeb}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy10
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {d4213f80-6b73-418c-af73-b704007511ed}
Contained 1 shadow copies at creation time: 2/24/2014 7:00:00 AM
Shadow Copy ID: {e3bd9313-e7a3-4972-a138-e298e6c12eff}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy11
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {1587431c-1ca9-4276-8d33-dd13ae58a122}
Contained 1 shadow copies at creation time: 2/24/2014 2:00:00 PM
Shadow Copy ID: {e4c3e5b4-0314-4496-9215-369b3c973b25}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {b79771fa-666c-40ff-98c2-80580c1fdf85}
Contained 1 shadow copies at creation time: 2/25/2014 2:00:01 PM
Shadow Copy ID: {9d23803a-5d4e-4222-a389-ddd1e17b0472}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {5b472176-33e7-447f-aebf-da630cebe01d}
Contained 1 shadow copies at creation time: 2/26/2014 7:00:01 AM
Shadow Copy ID: {0d5a5d90-c9e7-42c0-ab0b-accf0d7d7304}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {879a32b4-48f3-434f-8d92-7202a9a25076}
Contained 1 shadow copies at creation time: 2/26/2014 2:00:00 PM
Shadow Copy ID: {887d8ff9-db0d-4eaa-9a75-df60015c2bb7}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {fc8d7e9e-c4d4-4010-b603-d88b99435338}
Contained 1 shadow copies at creation time: 2/27/2014 7:00:00 AM
Shadow Copy ID: {69ca835d-0130-4435-8621-83a716f1b621}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {7cebbd3b-c599-4800-91f5-da94ca038a42}
Contained 1 shadow copies at creation time: 2/27/2014 2:00:00 PM
Shadow Copy ID: {57320a15-e046-4128-8305-661984910fff}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {702d2ca4-3f60-4d64-8578-50d9dd587ba6}
Contained 1 shadow copies at creation time: 3/12/2014 6:00:01 AM
Shadow Copy ID: {41c62c15-ad88-4191-8cc8-c2814da9a2f4}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy18
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Used Shadow Copy Storage space: 3.47 GB (8%)
Allocated Shadow Copy Storage space: 3.73 GB (9%)
Maximum Shadow Copy Storage space: 3.96 GB (10%)
Vssadmin list volumes
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Volume path: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
Volume name: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
Volume path: C:\
Volume name: \\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {004b7983-7f00-4abe-81de-36729db8355f}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {73682cd4-c469-4d00-b9b9-4b64f08af879}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {652f9dce-637f-447f-bbde-a16dc119e409}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {cd1dab9c-a9cb-4783-aff3-32fa2f9e625f}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {ba4c4bc6-9081-422a-9ed1-647c0eacfe8d}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {4e4ca3e1-c62a-474f-a925-fadc1a534188}
State: [1] Stable
Last error: No error
Writer name: 'Windows Server Storage VSS Writer'
Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
Writer Instance Id: {044b493b-829f-4bcd-9a8f-6d96a9d38daa}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {72c13a8c-4950-4abb-961a-2e0f612ea9b6}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {da138ec1-764b-4179-b2f4-70e94ac22276}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {dd729383-00a9-484c-9abc-3de903f5347c}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a7c0287b-0e85-4d37-9649-d79928def55e}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {aca73317-e7ce-40a0-aac2-548fd6a987c3}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {d7753d0e-6b3b-4af0-95ea-9aa6733071f4}
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {5971db7f-8508-438c-8f62-736f1b07750f}
State: [1] Stable
Last error: No error

Windows AD cannot authenticate if BI platform UNIX?

We were eagerly awaiting BI4 SP04 to address several SAP integration issues including the requirement use Windows AD for single sign to SAP Enterprise Portal hosting BI4 content (dashboards/webis/Analysis for OLAP) and BEx Web analyzer, i.e. user logs on once for Windows to authenticate to all SAP systems, ECC, BW, BI, EP, etc.. We have no plans to use the BI Launch Pad.
We are on AIX 6.1 for BI4 SP04, NW 7.3.1 and EP and BW 7.3.1 and are working through Kerberos client on AIX to Windows AD and SNC and SSO in SAP...
Frankly we have been struggling for some time with issues on BI4 SP02 and NW 7.3 so we are frustrated when we came across the followg in SAP doc -
Business Intelligence Platform Administrator Guide.pdf (http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf)
Page 211
The Windows AD security plugin cannot authenticate users if the BI platform server components are running on Unix
Page 212
Windows AD with Kerberos is supported if the Java application is on Unix. However, BI platform services must run on a Windows server.
Can someone clarify these statements? We will install Java application (NW? BI Java?) on UNIX. We will not run BI Platform? services on Windows.
If our requirement is to have a user only logon once to Windows and access BI4 content in the SAP Portal, not the BI Launch Pad, MUST we run BI4 on Windows?
Sincere thanks for your time and thoughts,
Lee Lewis
Summit Electric Supply
ASUG EDW and BO SIG Volunteer - Market Leader
[Email address removed. Please see the rules of engagement. The forum Administrator]

Hi Ainsley,
A work around? Yes and no and sort of ...kind of...
This turns out to be quite complex and tempermental.
In short, you cannot use Windows AD authentication, but instead use LDAP (with the Microsoft Active Directory). We were able to get this to work with much effort. The biggest limitation is that it supports a single AD forest.
I am giving a presentation on silent single sign on for BI4 and Enterprise Portals at the SAP BO User Confernce in Orlando and will see about posting the slides after the conference, but can share some of the resources here that we found to be most useful. Please reach out to me if I can help further.
Lee Lewis
•Integrating SAP BusinessObjects BI Platform 4.x with SAP NetWeaver, Ingo Hilgefort, SapPress 2011
•Configuring LDAP Manual Authentication and SSO for BI4 on Unix
•1631734 - Configuring Active Directory Manual Authentication and SSO for BI4
•Business Intelligence Platform Administrator Guide, SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3, June 2012
•1670073 - How -To: Generate keystore and certificate in the process of configuring STS for SAP
•1687295 - How to configure Single Sign On (SSO) on the SAP Netweaver 7.x portal to BI4
•IBM - Configure single sign-on authentication on AIX
•1537480 - Best Practice: How To setup Active Directory Single Sign On when BOE CMS is on Unix or Linux
•Kerberos Explained - Microsoft Technet
•SAP Help - Secure Network Communications (SNC)
•Using Kerberos Authentication for Single Sign-On
•SAP Netweaver 7.3 Configuring Kerberos Authentication
•SAP BusinessObjects BI4 Active Directory SSO Tutorial
• 1631734 - Configuring Active Directory Manual Authentication and SSO for BI4
•1245218 - How to connect the LDAP plugin to Active Directory
Lee Lewis

Bluetooth cannot detect the remote device

hi all,
I finished the Midlet code using bluetooth adaptor on my PC to search the remote bluetooth device, but when I run it, (Eclipse 3.2, JAVA JDK 1.5, SUN WDK 2.5), it can identiy the local bluetooth, and giveback the address, but it cannot search the remote device.
actually this program can run on a cell phone with JSR 82 API, is there any different? should I add some code to identify the serial port? I set the local bluetooth on COM 6 and remote device on COM 7 through a Bluetooth software which is provided by vendor.

Hey!!
I experienced similar error a week back. Pal i got to know that Java cannot access the windows blue tooth protocol stack. So there seems to be a solution called bluecove get it from benhui.com and im unable to get it worked. So if u find any solution mail me to [email protected] and i will keep you updated thanx bro!

Windows Vista cannot read the file in my ipod touch

I am using windows vista and I have 2 separate problems with my ipod touch:
1. Itune recognizes my ipod and all the songs that are on it but not the photos.
2. Windows cannot display the files that are on the device. When I go to my computer the ipod is not listed as one of the available drive.
What am I doing wrong?

Hi Garry296,
I'm happy to assist you today, with your problem! Let's take it step by step...
Garry296 wrote:
1. Itune recognizes my ipod and all the songs that are on it but not the photos.
So you mean you can sync music, but not photos? How are you doing it? See if this articles helps you: http://docs.info.apple.com/article.html?path=iTunesMac/7.5/en/789x.html
Garry296 wrote:
2. Windows cannot display the files that are on the device. When I go to my computer the ipod is not listed as one of the available drive.
That's not a problem. It is just like that! iPod Touch and iPhone cannot be used as a Storage drive. Apple removed this feature from this devices.
Hope this helps!
!http://signatures.mylivesignature.com/54486/122/A57996D55BE7ABB4A67DE686D381A27 4.png!

R12 on Windows: I cannot find the OM tables in VIS - please help

Hi,
I have R12 installed on my Windows. I am using Oracle SQL Developer to browse the VIS tables but I cannot find the tables I need to browse.
For example: oe_order_headers_all, oe_order_lines_all, & wsh_delivery_details
Thanks,
Amorsolo

I can find those objects in my 12.1.3 Vision instance.
SQL> select owner, object_type, object_name
from dba_objects
where object_name in ('OE_ORDER_HEADERS_ALL', 'OE_ORDER_LINES_ALL', 'WSH_DELIVERY_DETAILS')
order by 3;
OWNER      OBJECT_TYPE         OBJECT_NAME
ONT        TABLE               OE_ORDER_HEADERS_ALL
APPS       SYNONYM             OE_ORDER_HEADERS_ALL
APPS       SYNONYM             OE_ORDER_LINES_ALL
ONT        TABLE               OE_ORDER_LINES_ALL
WSH        TABLE               WSH_DELIVERY_DETAILS
APPS       SYNONYM             WSH_DELIVERY_DETAILS
6 rows selected.Thanks,
Hussein

HT1846 windows 7 cannot detect the wi-fi or wirless signal

Anyone can help me out? I've just install the bootcamp on my Macbook Pro 15" with Lion OS, Windows 7 ultimate 64, the program cannot find the wirless signal, is there any trick that I missed?

Wrong section, oops

Cannot authenticate the phone????? ARGHH!

LAPTOP: HP Pavilion DV6836TX
MOBILE: Nokia 6120 Cllasic
ALSO in Bluetooth Devices under the tab Hardware it has
- Microsoft Bluetooth Enumerator
- HP Integrated Module with Bluetooth 2.0 Wireless Technology
PC Connectivity Solution:
Version 8.22.2.0
[Nokia Connectivity Cable Driver:]
Version 7.0.2.0
Operating system:
Microsoft Windows Vista 32-bit Edition, Service Pack 1
Language: English
Language for non-Unicode programs: English
Detected Internet browsers:
- Microsoft Internet Explorer 7.0
Detected Bluetooth stacks:
- Microsoft (Version: 6.0.6000, Build: 16386)
PC Suite seems to not recognize the HP Bluetooth stack and only the microsoft one...could this be the problem? If not how can I get this thing working...because I need to be able to sync Outlook to my phone!

Hi,
Could you please check this post
/discussions/board/message?board.id=pcsuite&thread.id=27160
Best of luck

E71 windows 7 bluetooth "Cannot authenticate the p...

Similar Messages

Maybe you are looking for