Windows AD connection for a BO Universe.

Hiu2026
I am new to the Universe Designer and CMC interface.
My question is this:
Can I establish a database connection, for a universe, to a MS-SQL 2008 server using either ODBC or OLE DB that uses Windows authenticated account and not a SQL Server authenticated login ID/Password?
When I create a ODBC / OLEDB integrated security on the BO server and test the universe connection, the user that is currently using the Universe is the account that is being passed to the MSSQL 2008 database, for authentication. I cannot use that pass-through connection. I need to use a dedicated service AD account to be the connection between our Universe an our MSSQL 2008 database.
I haven't read any on-line information that explains how to connect a universe to a data source, using a domain AD account. If someone can point me to some on-line documentation, I would appreciate it. And the BO server version that is being used: 3.1.
Thanksu2026

Hi Joe,
your thread is close to
http://scn.sap.com/thread/1532816
http://scn.sap.com/thread/3309317
Regards
NK

Similar Messages

I am trying to allow guests on windows to connect to shares on my Lion server but it keeps asking for a password for guest. I have allow guest users to access this share enabled but it still does not work.

I am trying to allow guests on windows to connect to shares on my Lion server but it keeps asking for a password for guest. I have allow guest users to access this share enabled but it still does not work.

Ditto. Guest accounts shouldn't have a password. No way to enter one in System Prefs...

I have Remote desktop connection for my mac running osx 10.6.8 and I have a windows xp laptop, I want to have my mac be able to run the windows xp from my pc, how do I do it?

I have Remote desktop connection for my mac running osx 10.6.8 and I have a windows xp laptop, I want to have my mac be able to run the windows xp from my pc, how do I do it?

Hello Fiona,
Congratulations on your new iPhone! You can sync information to your iPhone from your MacBook Pro using the Info tab in iTunes when your iPhone is connected. Use the steps in the following article:
iOS: Syncing your data with iTunes
http://support.apple.com/kb/ht1386
Thank you for using Apple Support Communities.
Best,
Sheila M.

Crystal Reports for Enterprise and universe connections

Hi, I have noticed an issue with Crystal Reports for Enterprise that may give many administrators a headache.
If a BOBJ user has access to a sensitive universe (eg HR or Finance data) to run pre-built WebI reports from (but not create new ones or edit the universe) then they must have been give data-access to that universe's connection object. Security on the universe and folder could prevent them from accessing information from the universe they shouldn't see or editing the reports and creating new ones.
However if the same user is given access to Crystal Reports for Enterprise in order to access other data sources, then the fact that they have data-access to the above universe connection object now creates a security problem.
Crystal for Enterprise allows a user to open a universe connection object as a data-source. If the user opened the connection for the above 'sensitive' universe they could see all the data in the database - avoiding any universe level restrictions in the process.
What is the suggested way around this? There doesn't appear to be granular enough security to prevent users with data access on a connection object also using that object to create new reports in Crystal for Enterprise.
The only way around it I can see is to deny the user access to the sensitive universe output altogether, but this changes the whole business process for the team involved.
thanks
Keith

I have a couple of thoughts:
1. Create a special reporting user in the database that only has access to a set of views that don't include the sensitive information. Then create a universe based on those views which uses a connecting that logs in as that special user. Give the folks who don't have access to the sensitive data access to this connection and universe instead of the universe and connection that include the sensitive data.
2. Since you have BO, you should have a support contract. I would report this as a bug. However, SAP may tell you that it is "working as designed", in which case you could go to IdeaPlace (https://ideas.sap.com/) and add this as a requested enhancement.
-Dell

Universe Connections for SAP BEx

Hi All,
We are planning to build couple of Universes over SAP BEx query.
Could anyone inform if we should go for creating a single connection and use it for all Universes (or) Create multiple connections.
Does having different connections for different Universes(though Data Warehouse-BW) is same helps in increasing report performance?
Thank you.
- AK

Hi,
It all depends on your requirement. There are few ways.
You can create one super universe on the top of your BW Query and then create your reports using your super universe.
Or you can create multiple universes and then create your reports.
Basically one universe one connection. SAP Universes are different then other universes where you create one connection.
In SAP environment one universe one connection.
Hope it helps.
Regards,
Bashir Awan

Universe connection for sybase

Hi mates,
I am trying to connect with sybase from universe , I have sybase client 12 installed in my machine and I can able to ping to sybase server successfully.
But I am unable to access the sybase from universe connectiion.
I also tried with ODBC connection mean while creating DSN for sybase database .
But no luck
any help great appreciation.................................

Did DSN creation successful??
What exact error message BO throwing out??
I'm Back

Freeze login window when connected disk for Time-Machine

MacBook, 13-inch, Early 2008, Lion 10.7.3 (same problem on 10.7, 10.7.2)
- Freeze login window when connected disk for Time-Machine.
In logs I can see they Time-Machine finished work successfully.
I have do hardware reset every time to login my laptop.

wongkh wrote:
If connecting the time machine after windows is up,both windows and the time machine works properly.
i can access the time machine hdd in windows.
Don't, Time Machine knows nothing about Windows, and vice versa.

AnyConnect pre Windows login connects and disconnects for some users

Hi,
I have Cisco VPN AnyConnect (version 3.1.0310) clients with a connectivity issue which manifests as follows:
A user boots their Windows 7 SP1 laptop up.
Before Windows login, the user clicks "switch user" and enters their Cisco AnyConnect credentials (this connects OK).
Once the VPN tunnel is established a user logs into Windows.
At this point, 1 of 2 things happen:
1. Most users VPN connection stays connected and user GPO processing\logins work as normal
2. For a minority of users, the VPN connection disconnects and then reconnects. The VPN disconnect and reconnect causes connectivity issues with mapped drives and Outlook (most likely due to GPO processing not applying as the VPN tunnel wasn't established at the required time).
There are no known commanalities between problematic users - all users are in the same OU and laptops are in the same OU, so they should be getting the same AD settings. The same user can login 14 times OK, but may experience this issue on the 15th occasion.
Within the profile xml file (stored in c:\program data\) the key "AutoConnectStart" is set to false for user controllable and default value. The XML policy settings are being applied correctly (we've checked Event ID 3010 within the Cisco AnyConnect Windows logs).
What we have noticed from using the back end Cisco monitoring client is that users who experience connection issues, connect pre windows login OK, but once they're logged into Windows the Cisco VPN AnyConnects seems to try and re-connect, which causes the current VPN tunnel to disconnect and re-connect. This disconnect and re-connect for users seems to cause issues with logon and GPO processing.
So far, the only rock solid way we've found of stopping this disconnect and re-connect behaviour is by configuring a system deny permission on registry key "HKLM\Software\Microsoft\Windows\CurrentVersion\Run". This key contains an entry for Cisco AnyConnect VPN. Unfortunately setting a deny on the individual node value isn't possible and if the key is deleted or modified the system re-creates it. I'd rather avoid setting a system deny on the key for all users.
Any advice on how troubleshoot and diagnose this problem is appreciated.
Thanks

I've attached some log files in case someone is particularly keen eyed at spotting issues (all data is anonymized)
6
Oct 30 2013
10:19:31
172.16.12.17
58124
10.5.128.21
8080
Built inbound TCP connection 123678229 for outside:172.16.12.17/58124 (172.16.12.17/58124)(LOCAL\jpk789) to inside:10.5.128.21/8080 (10.5.128.21/8080)
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Teardown TCP connection 123678214 for outside:172.16.12.17/58122(LOCAL\jpk789) to inside:10.5.140.210/443 duration 0:00:00 bytes 11971 TCP Reset-O
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Teardown UDP connection 123678191 for outside:172.16.12.17/51368(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 110
6
Oct 30 2013
10:19:31
172.16.12.17
58123
10.5.12.182
88
Built inbound TCP connection 123678217 for outside:172.16.12.17/58123 (172.16.12.17/58123)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Teardown UDP connection 123678189 for outside:172.16.12.17/62455(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 430
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Built inbound TCP connection 123678214 for outside:172.16.12.17/58122 (172.16.12.17/58122)(LOCAL\jpk789) to inside:10.5.140.210/443 (10.5.140.210/443)
6
Oct 30 2013
10:19:31
172.16.12.17
56197
10.5.141.155
53
Built inbound UDP connection 123678212 for outside:172.16.12.17/56197 (172.16.12.17/56197)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
58121
10.5.12.179
389
Built inbound TCP connection 123678196 for outside:172.16.12.17/58121 (172.16.12.17/58121)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:19:31
172.16.12.17
58120
10.5.12.199
80
Built inbound TCP connection 123678195 for outside:172.16.12.17/58120 (172.16.12.17/58120)(LOCAL\jpk789) to inside:10.5.12.199/80 (10.5.12.199/80)
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Built inbound UDP connection 123678191 for outside:172.16.12.17/51368 (172.16.12.17/51368)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
62458
10.5.12.182
389
Built inbound UDP connection 123678190 for outside:172.16.12.17/62458 (172.16.12.17/62458)(LOCAL\jpk789) to inside:10.5.12.182/389 (10.5.12.182/389)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Built inbound UDP connection 123678189 for outside:172.16.12.17/62455 (172.16.12.17/62455)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:30
IPSEC: An inbound remote access SA (SPI= 0x67ED9B28) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
IPSEC: An outbound remote access SA (SPI= 0x9C00507E) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
Group User IP <75.12.34.56> AnyConnect session resumed connection from IP <75.12.34.56>.
5
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:19:18
172.16.12.17
64287
10.5.12.182
445
Teardown TCP connection 123673186 for outside:172.16.12.17/64287(LOCAL\jpk789) to inside:10.5.12.182/445 duration 0:02:01 bytes 14605 Tunnel has been torn down
6
Oct 30 2013
10:19:17
172.16.12.17
64278
10.5.141.144
445
Teardown TCP connection 123672510 for outside:172.16.12.17/64278(LOCAL\jpk789) to inside:10.5.141.144/445 duration 0:02:15 bytes 9237 Tunnel has been torn down
6
Oct 30 2013
10:19:14
172.16.12.17
64273
10.5.140.231
445
Teardown TCP connection 123672368 for outside:172.16.12.17/64273(LOCAL\jpk789) to inside:10.5.140.231/445 duration 0:02:16 bytes 7297 Tunnel has been torn down
6
Oct 30 2013
10:19:04
172.16.12.17
54449
10.5.141.155
389
Teardown UDP connection 123672541 for outside:172.16.12.17/54449(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:19:04
172.16.12.17
137
10.5.141.155
137
Teardown UDP connection 123672421 for outside:172.16.12.17/137(LOCAL\jpk789) to inside:10.5.141.155/137 duration 0:02:04 bytes 486
6
Oct 30 2013
10:19:00
172.16.12.17
138
10.5.141.155
138
Teardown UDP connection 123672424 for outside:172.16.12.17/138(LOCAL\jpk789) to inside:10.5.141.155/138 duration 0:02:01 bytes 177
6
Oct 30 2013
10:18:58
172.16.12.17
63666
10.5.141.155
389
Teardown UDP connection 123672316 for outside:172.16.12.17/63666(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:58
172.16.12.17
53105
10.5.141.155
389
Teardown UDP connection 123672300 for outside:172.16.12.17/53105(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:47
172.16.12.17
61715
10.5.12.182
389
Teardown UDP connection 123671945 for outside:172.16.12.17/61715(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 312
6
Oct 30 2013
10:18:43
172.16.12.17
54262
10.5.12.179
389
Teardown UDP connection 123671801 for outside:172.16.12.17/54262(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:42
172.16.12.17
57911
10.5.141.156
389
Teardown UDP connection 123671777 for outside:172.16.12.17/57911(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:40
172.16.12.17
123
10.5.12.182
123
Teardown UDP connection 123671670 for outside:172.16.12.17/123(LOCAL\jpk789) to inside:10.5.12.182/123 duration 0:02:01 bytes 136
6
Oct 30 2013
10:18:40
172.16.12.17
58107
10.5.12.179
389
Teardown UDP connection 123671639 for outside:172.16.12.17/58107(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:40
172.16.12.17
58825
10.5.12.179
389
Teardown UDP connection 123671633 for outside:172.16.12.17/58825(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:02 bytes 355
6
Oct 30 2013
10:18:39
172.16.12.17
60424
10.5.141.156
389
Teardown UDP connection 123671611 for outside:172.16.12.17/60424(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
56635
10.5.141.156
389
Teardown UDP connection 123671566 for outside:172.16.12.17/56635(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
61204
10.5.12.179
389
Teardown UDP connection 123671558 for outside:172.16.12.17/61204(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
50615
10.5.12.179
389
Teardown UDP connection 123671545 for outside:172.16.12.17/50615(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
57940
10.5.141.154
389
Teardown UDP connection 123671537 for outside:172.16.12.17/57940(LOCAL\jpk789) to inside:10.5.141.154/389 duration 0:02:02 bytes 313
6
Oct 30 2013
10:18:38
172.16.12.17
57939
10.5.141.156
389
Teardown UDP connection 123671536 for outside:172.16.12.17/57939(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:02 bytes 366
6
Oct 30 2013
10:18:38
172.16.12.17
64495
10.5.12.182
389
Teardown UDP connection 123671532 for outside:172.16.12.17/64495(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:02 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
62965
10.5.12.182
389
Teardown UDP connection 123671521 for outside:172.16.12.17/62965(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54994
10.5.12.179
389
Teardown UDP connection 123671514 for outside:172.16.12.17/54994(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54993
10.5.12.179
389
Teardown UDP connection 123671513 for outside:172.16.12.17/54993(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
63390
10.34.140.104
389
Teardown UDP connection 123671483 for outside:172.16.12.17/63390(LOCAL\jpk789) to inside:10.34.140.104/389 duration 0:02:01 bytes 385
6
Oct 30 2013
10:18:37
172.16.12.17
63389
10.33.140.104
389
Teardown UDP connection 123671482 for outside:172.16.12.17/63389(LOCAL\jpk789) to inside:10.33.140.104/389 duration 0:02:01 bytes 384
6
Oct 30 2013
10:18:10
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 75.12.34.56 and 80.21.182.245 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
Group User IP <75.12.34.56> AnyConnect session lost connection. Waiting to resume.
5
Oct 30 2013
10:18:10
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA DOWN. Reason: peer lost
6
Oct 30 2013
10:17:42
172.16.12.17
64250
10.5.141.186
445
Teardown TCP connection 123671908 for outside:172.16.12.17/64250(LOCAL\jpk789) to inside:10.5.141.186/445 duration 0:00:57 bytes 454851 TCP Reset-I
6
Oct 30 2013
10:17:20
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673268 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:19
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673244 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:18
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673218 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:36
172.16.12.17
63060
10.5.141.155
53
Built inbound UDP connection 123671551 for outside:172.16.12.17/63060 (172.16.12.17/63060)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:36
172.16.12.17
63010
10.5.12.182
88
Built inbound TCP connection 123671549 for outside:172.16.12.17/63010 (172.16.12.17/63010)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63009
10.5.12.182
88
Built inbound TCP connection 123671548 for outside:172.16.12.17/63009 (172.16.12.17/63009)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63008
10.5.141.156
389
Built inbound TCP connection 123671546 for outside:172.16.12.17/63008 (172.16.12.17/63008)(LOCAL\jpk789) to inside:10.5.141.156/389 (10.5.141.156/389)
6
Oct 30 2013
10:16:36
172.16.12.17
50615
10.5.12.179
389
Built inbound UDP connection 123671545 for outside:172.16.12.17/50615 (172.16.12.17/50615)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:16:36
172.16.12.17
63007
10.5.12.182
88
Built inbound TCP connection 123671544 for outside:172.16.12.17/63007 (172.16.12.17/63007)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
55425
10.5.141.155
53
Teardown UDP connection 123671487 for outside:172.16.12.17/55425(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 164
6
Oct 30 2013
10:16:36
172.16.12.17
50614
10.5.141.155
53
Built inbound UDP connection 123671543 for outside:172.16.12.17/50614 (172.16.12.17/50614)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56263
10.5.141.156
53
Built inbound UDP connection 123671461 for outside:172.16.12.17/56263 (172.16.12.17/56263)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60708
10.5.141.155
53
Built inbound UDP connection 123671460 for outside:172.16.12.17/60708 (172.16.12.17/60708)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56982
10.5.141.156
53
Built inbound UDP connection 123671459 for outside:172.16.12.17/56982 (172.16.12.17/56982)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64548
10.5.141.155
53
Built inbound UDP connection 123671458 for outside:172.16.12.17/64548 (172.16.12.17/64548)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60827
10.5.141.156
53
Built inbound UDP connection 123671457 for outside:172.16.12.17/60827 (172.16.12.17/60827)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64207
10.5.141.155
53
Built inbound UDP connection 123671453 for outside:172.16.12.17/64207 (172.16.12.17/64207)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671443 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671442 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671441 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:34
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:16:34
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
5
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:16:34
Group User IP <75.12.34.56> AnyConnect parent session started.
6
Oct 30 2013
10:16:34
DAP: User jpk789, Addr 75.12.34.56, Connection AnyConnect: The following DAP records were selected for this connection: ContosoPolicy
6
Oct 30 2013
10:16:34
AAA transaction status ACCEPT : user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved default group policy (DfltGrpPolicy) for user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved user specific group policy (useGroup1s.Grp) for user = jpk789
6
Oct 30 2013
10:16:34
AAA group policy for user jpk789 is being set to useGroup1s.Grp;
6
Oct 30 2013
10:16:34
AAA user authentication Successful : server = 192.168.7.4 : user = jpk789

My airport network will not connect to to the internet via my modem. My host computer is a hp running windows xp. I have had great connection for 3 years. Then suddenly can not connect. Please can you assist

My airport will not connect to the internet via my modem. Worked for 3 years. Suddenly stopped. Main host computer is hp running windows xp.
When trying to connect windows states connection was cancelled. I have had hp checked by compputer repair and still have same problem?

The router is much, much newer than the computer, perhaps some characteristic of the WiFi network as it's currently setup is preventing the computer from connecting.
Try to go back to the basics: set your WiFi network to "b" mode only (i.e., turn off "g") and termporarily remove the password from it. See if the computer will at least establish a connection at that point. Then start turning on one thing at a time ("g" mode, then security, etc).
Not sure what format your WEP key is, but if it's not 10 characters (the minimum for the standard, which constitutes a 64-bit key), you can try making it that long. If it's 13 or 26 characters, it might be a higher encryption than the computer can support.
If all else fails, you could try looking on ebay/craigslist for a copy of Tiger to install on the iMac, which would have software support for more WiFi encryption schemes. Also, it would provide software support for USB WiFi adapters that would also be able to connect to more modern networks.

Itunes launches fine however I cannot connect to the Itunes store. It says that Itunes has stopped working and windows is looking for a solution.

Everything seems fine until I try to access the ITunes store. Then I get a message that ITunes has stopped working and that Windows is looking for a solution. Then it tells me that no solution has been found and closes down Itunes.
I can still sync music / podcasts to my ipod and iphone. I am still getting podcast downloads automatically for the ones I have subscribed to.
This is the first time this issue with not being able to access the Itune stores has happened to me. I was just there 2 nights ago.

Hello notime4,
The article linked below details some useful troubleshooting steps that can help stabilize iTunes on your computer.
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
http://support.apple.com/kb/TS1717
Cheers,
Allen

Where to find the timeout setting for connecting to SAP Bi Universe in Power Query for Excel

Hi All,
I am trying to connect a SAP BI Universe. I am able to login to the environment and get the list of folders. But on trying to use the universe inside the folder, I am getting a time out error. The time out happens exactly at 100 seconds always.
DataSource.Error: SapBusinessObjects: The operation has timed out
Can you let me know if any setting can be done to avoid this timeout and get the universe into power query?

I have the same problem with Version: 2.17.3850.242. It times out after 100 seconds.
In addition, I couldn't report it by sending a frown. Get the following error message
Error Message: Could not load file or assembly 'Microsoft.Office.Interop.Outlook, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
or one of its dependencies. The system cannot find the file specified.

CR2008 connectivity issue with BOE Universes(sap and non sap universes)

Hi Experts !!
Recently we tried to build/connect to a Universe in Crystal Reports2008 via 'Make a new connection tab'.
The universes are of SAP BW or non SAP Lying in BOE Servers and we are trying to build reports on them by conncting/utilizing the universes as a database for Crystal Reporting.
Our issue is most of the time we are not able to connect to the Universes and the connectivity blows out by some 'communication Error' thing initially.
While at some other points in time, the connectivity takes us to the Universe and we are able to select few characteristics and key figures from the Universe but the moment we go futher and try to run by pressing 'OK' button it blows out and say' LOGON FAILED'.
Apparantly, it is an connectivity issue with BOE server and from the different blogs it looks like it is a known issue for long.
The proposed issue resolution were like either CR2008 should be SP2 with BOE SP3 or there should be some additional .dll files defined in the paths in case of MSSQL database. None of this applies to us as we are on CR2008 with SP3 and going back to SP2 is probably not a viable option for us, and we are using Oracle as underlying database in this specific case.( i would like to tell you here that we are able to connect to Oracle Database directly though).
We have raised a message with SAP and was just wondering if we do have some solution/workaround already available to this known issue in place please?
Thanks&Regards.
Edited by: AMIT GHILDYAL on Aug 1, 2011 2:41 PM
Edited by: AMIT GHILDYAL on Aug 1, 2011 2:44 PM
Edited by: AMIT GHILDYAL on Aug 1, 2011 3:14 PM

Hi Amit,
Moved to Universe Forum.
If you have a case logged then no point posting here also, this is a public site and not a case management tool.
Once you do get the solution from your case please post it here also to help others if they have the same problem.
Thank you
Don

TS1591 my classic iPod no longer appears in iTunes window when connected to iMac. does this mean my device is no longer supported by iTunes? or incompatible with OSX?

my classic iPod no longer appears in iTunes window when connected to iMac. does this mean my device is no longer supported by iTunes? or incompatible with OSX?

Hello stiannac
Check out the article below for troubleshooting to get your iPod showing back up on your iMac
iPod not recognized in iTunes and Mac desktop
http://support.apple.com/kb/ts1410
Thanks for using Apple Support Communities.
Regards,
-Norm G.

Windows Vista claims for "Bluetooth Peripheral Device" driver

When I connect my iPhone via bluetooth to my computer for "tethering", Windows Vista claims for "Bluetooth Peripheral Device" driver and i can´t connect.
Where is the driver? Anyone knows it?
Thanks!

My Mac Book Pro decided to update with windows update ... I lost bluetooth and when my machine started up it said found new hardware ... and proceeded to look for the driver BCM2046A ... its not on the Mac Discs nor on the XP Disc ...
I searched and searched and searched ..bump
I then found this link download and use ... and pass on ....
http://www.broadcom.com/support/license.php?file=SetupBtwDownloadSE.exe

Windows "Easy Connect" does not reply with the password / "Easy Connect is not Available"

Hello,
I have posted a related question some time ago, which was eventually resolved. However, after some time a problem with Easy Connect (used for MSRA) came back:
Whenever I arrive at the point in setting up a MSRA session where Easy Connect is needed, I get the reply: "Easy Connect is not Available". Here is an example of the problem:
Start MSRA
--> as expected, a window with "invite someone to help you" and " Help some who has invited you" appears
Select "invite someone to help you"
--> as expected, a window with "Who do you want to get help from" appears
Select "Invite someone to help you"
--> as expected, a windows with "How do you want to invite your trusted helper?" appears
Select "Use Easy Connect"
--> as expected, the temporary "Create invitation window / checking network capabilities" window appears
Next, I would expect this windows to close a new window to provide me with the Easy Connect password. However, instead I get the window "Easy Connect is not available".
I cannot continue. (I have screenshots so can repost with them if that would clarity my question)
Any suggestion how to resolve would be appreciated.
(Please do not reply with the 3 suggestions from the FAQ (both computers must run windows 7 / Access to internet is limited / your router does not support Easy Connect - doesn't help)
More background information and things I have tried:
The "Easy Connect is not available" window offers the "Tell me more about how to fix this problem" which I have tried, but those suggestions do not help
If I use the other MSRA option: "Help someone who has invited you" (this would be my typical use case), followed by "help someone new" and than select "Use Easy Connect", I also get the "Easy Connect is not available"
window instead of the expected option to enter the Easy Connect password. I believe this is that same problem.
This happed with both the 32 as well as the 64 MSRA versions
I'm using Window 7 Ultimate, 64 bit with all the latest updates
This desktop PC is wired to the internet via an Edimax gigabit switch, a Dlink DIR-855 wireless router and a fiber modem in bridge mode
The W7 desktop has a single active network connection only
I'm using Windows Firewall and Windows Security Essentials
Disabling the firewall on the PC did not help
Network discovery is enabled in Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings (that’s UPnP – right?)
The Internet Connectivity Evaluation Tool does not seem to be available anymore from MSFT sites
Restarting "Peer Name Resolution Protocol" did not help
Restarting "Peer Networking Identity Manager Properties" did not help
Starting up with a "Clean Boot" (disabled all non-Microsoft services using MSConfig) did not help
I would also be interested to understand how I can check on the status of the "Easy Connect" service. Is this a service hosted somewhere, or??
Thanks!

Dear Andy,
Thanks a lot for your reply. Let me answer your questions:
Q: Could you use the other methods: save this invitation as a file and use e-mail to send invitation?
A: yes, that way I can establish a MSRA connection
Q: Have you disable other network connections, including disable all virtual network card?
A: if I check with ‘Device Manager/Network Adapters’ (or Control Panel/Network and Internet/Network Connections) I see two network adapters (my Asus motherboard has two network connectors). Both are available, but only one is used. I have
disabled one. Unfortunately, this does not solve the problem. I will leave it disable for now.
Q: To find detailed information about this issue, please locate to event view and find the logs about remote assistance.
A: I have to admit that the Event Viewer is unfamiliar territory for me. So, I’m not sure where and what to look for. However, as suggested, I found "Event Viewer (local)/Applications and Services Logs/Microsoft/Windows/Remote assistance/Operational".
Each time, I attempt to use MSRA/Easy Connect, it seems two entries are added. As I cannot seem to upload files with this post, here are just the two entries:
“Diagnosis Repro Attempt resulted in a failure.”
“Remote Assistance troubleshooting has confirmed the problem: Remote Assistance Easy Connect isn't available.”
If you need more details, please suggest what to forward or check. I'm eager to find a solution!
W.

Windows AD connection for a BO Universe.

Similar Messages

Maybe you are looking for