Repository connect issue after MDM Patch Upgrade

MDM Expert
We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
SAP is asking to create new DB Instance for MDM.
If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
Please help
Thanks
Deelip

Solution provided by sAP

Similar Messages

Source System Connection Issue after BI 7 Upgrade

Hi all,
We have just upgraded from BW 3.1 to BI 7.
After the upgrade, I checked the connection to our R3 4.6 source system.
It is now saying the following message:
Source system XXX is marked as inactive in BI.
Check failed for RFC connection XXX ; check destination
After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
The thing is that our name & password ARE correct definitely.
Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
Any ideas?
Thank you
chris

Hi,
as from NW7.0, passwords are case-sensitive.
If you define the passwords in the RFC in uppercase, it will work.
This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

IPad connection issue after iOS 8 upgrade

I Have an iPad 3G - WiFi- and recently upgraded to IOS 8. Every since connection bounces from 3G to "no service" (AT&T provider). I have been able to get reconnected only by choosing "Reset Settings". I previously powered off and restarted with no resolution. Found article that mentioned this same issue but said it only was issue in iphone 6. Anyone else have a similar experience or easier solution? I rely on iPad for work and really need a solution that doesn't involve frequent resets....
Message was edited by: Raven72songs

I have been to Apple store twice now on this issue. We have tried all of the above suggestions-- restore, network reset, re-installing SIM card-- and the problem always returns. The Genius Bar tech told me the IOS update brought out a latent problem hidden in the firmware -- in other words, it is a problem caused by Apple, but not everyone experiences this problem. The tech also told me there was nothing more that could be done, short of buying a new ipad. I asked about going back to the earlier IOS version but she said Apple will not allow that at this point. So it sounds to me like a "forced obsolescence" thing that Apple has inflicted on me: they admit their update brought out a problem, previously unmanifested, which had always been lurking in their firmware-- but their solution is that I need to ditch my ipad 2 and buy a new ipad. I never had this type of issue before the upgrade. the problem is more of a nuisance/inconvenience than anything else, because it can be rectified by powering down every few hours, so it's not worth it to me to spend hundreds on a new ipad. And anyway if this is an example of their customer service I'm not sure I will stay with Apple when it finally is time to buy a new tablet.

Adobe form not working after MSS Patch Upgrade

Hi,
We have implemented ESS/MSS and in one of the MSS scenario to create a new personnel chnage request we have an Adobe interactive form (WD) which actually validates the users Social Security number by calling an RFC in the ECC 6.0 and updates the form's filed on the front end. There was an issue of "Expired SSO Ticket" and to resolve this SAP recommended to apply SAP_JTECHS (SAPJTECHS13P_14-10003467) and SAP_JTECHF (SAPJTECHF13P_15-10003468) patches to fix the problem. But after applying these patches Adobe form for PCR has stopped working and it just gets hanged, form appears on the front end and when user enters the values and hit enter to validate, it doesnt communicate with the Backend ECC system only the SAP status picture keeps rotating, i turned the trace ON and checked it, its not at all communicating with the ECC system. Where as in other systems where we have not appplied the pacthes, those are working fine. One of the error i noticed in the server log is as below:
jco.client.mysapsso2=AjExMDAgAA5wb3J0YWw6QkNPTFNUT4gAE2Jhc2ljYXV0aGVudGljYXRpb24BAAdCQ09MU1RPAgADMDAwAwADU1BEBAAMMjAwODExMDMxNjU3BQAEAAAAEAoAB0JDT0xTVE//AQUwggEBBgkqhkiG9w0BBwKggfMwgfACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0DCBzQIBATAiMB0xDDAKBgNVBAMTA1NQRDENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDgxMTAzMTY1NzQwWjAjBgkqhkiG9w0BCQQxFgQUfD7V7TS!58cgzIFyucxCSL4ltuswCQYHKoZIzjgEAwQvMC0CFA4Q0!Rr2xYFPwFwXz8WeFF1UALlAhUAmHiTdHw!3s4Q!Jc9gDyY4QSvxa4=, user=, mshost=sapdv2.company.com, r3name=DV2, jco.client.type=B, jco.client.trace=0, group=SRS, codepage=1100}
Client not connected#
#1.5 #76C1EDD07B440026000000000007501600045ACC2EF6809D#1225732914577#/Applications/BusinessLogic#sap.com/home~zb2bzsrs#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#BCOLSTO#1480##hadspd1.bnet_SPD_306896250#BCOLSTO#daca9e30a9cb11dd99c976c1edd07b44#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface.#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {passwd=?, lang=en, client=150,
Can someone please suggest what could be the possible reason for such a problem with Adobe form and whats the way out to resolve this. Appreciate a quick help in this regard.
Thanks in advance,
Sarabjeet.

Hi,
We had the same issue after the Patch update to SP17 in both Backend as well in Portal, to resolve my colleagues had a look at the standard forms which were working and found that because of the patch update the script used in the custom forms was changed and not the standard and
on event trigger which was processed in the container they replace the script to the standard one. and it started working.
But this is not the solution we are looking at solution on having the same version of script as in the standard even after the patch update.
So to your point to resolve compare the scripts in both standard and customized forms and do the same.
And also have a look at the SAP Note: 1109392
.... this is a temporary solution.....
Hope this helps.
Cheers-
Pramod

Is there a fix for the wifi connectivity issue after ios6 update?

Is there a fix for the wifi connectivity issue after ios6 update?
Cannot connect to any wifi since update to 6.0.1
How do I get update to 6.0.2?
Will that even help?

Some things to try first:
1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
4. Go into your router security settings and change from WEP to WPA with AES.
5. Renew IP Address: (especially if you are droping internet connection)
    •    Launch Settings app
    •    Tap on Wi-Fi
    •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
    •    In the window that opens, tap on the Renew Lease button
~~~~~~~~~~~~~~~~~~~~~~~~~
iOS 6 Wifi Problems/Fixes
How To: Workaround iPad Wi-Fi Issues
http://www.theipadfan.com/workaround-ipad-wifi-issues/
Another Fix For iOS 6 WiFi Problems
http://tabletcrunch.com/2012/10/27/fix-ios-6-wifi-problems-ssid/
Wifi Doesn't Connect After Waking From Sleep - Sometimes increasing screen brightness prevents the failure to reconnect after waking from sleep. According to Apple, “If brightness is at lowest level, increase it by moving the slider to the right and set auto brightness to off.”
Fix For iOS 6 WiFi Problems?
http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
iOS 6 iPad 3 wi-fi "connection fix" for netgear router
http://www.youtube.com/watch?v=XsWS4ha-dn0
Apple's iOS 6 Wi-Fi problems
http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
~~~~~~~~~~~~~~~~~~~~~~~
How to Fix a Poor Wi-Fi Signal on Your iPad
http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Fix-A-Poor-Wi-Fi-Signal-O n-Your-iPad.htm
iOS Troubleshooting Wi-Fi networks and connections http://support.apple.com/kb/TS1398
iPad: Issues connecting to Wi-Fi networks http://support.apple.com/kb/ts3304
WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
How to Fix: My iPad Won't Connect to WiFi
http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
iOS: Recommended settings for Wi-Fi routers and access points http://support.apple.com/kb/HT4199
How to Quickly Fix iPad 3 Wi-Fi Reception Problems
http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
iPad Wi-Fi Problems: Comprehensive List of Fixes
http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
Connect iPad to Wi-Fi (with troubleshooting info)
http://thehowto.wikidot.com/wifi-connect-ipad
Fix iPad Wifi Connection and Signal Issues http://www.youtube.com/watch?v=uwWtIG5jUxE
Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
Unable to Connect After iOS Update - saw this solution on another post.
https://discussions.apple.com/thread/4010130
Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
~~~~~~~~~~~~~~~
If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
 Cheers, Tom

Bluetooth connection issues after update

Is anyone experiencing bluetooth connection issues after upgrading to iOS 8.1.3? I upgraded to iOS 8.1.3 and now it won't connect to my car bluetooth and my bluetooth speaker will sound like it has static from time to time.

Hi, joshzik.
Thank you for visiting Apple Support Communities.
I understand that you are experiencing issues with various Bluetooth devices and your iPhone. Sometimes pairing the devices again can resolve the issue. However, here are a couple articles that have some helpful troubleshooting steps regarding Bluetooth connectivity and an iOS device.
Get help using your iPhone, iPad, or iPod touch with your car stereo
http://support.apple.com/en-us/HT203412
iOS: Troubleshooting Bluetooth connections
http://support.apple.com/kb/TS4562
-Jason H.

Is there any fix for the bluetooth connectivity issue after most recent OS update?

Seems to be a common problem particularly with bluetooth headseat connectivity. Any ideas?

There is no bluetooth connectivity issue after the recent OS update. There may be a problem with your phone, which may or may not be related to the update. A "common problem" looks like this in the forums:
I haven't seen any threads on BlueTooth with over 1.4 million views and over 12,000 replies, or even any vaguely close. For any problem that someone has there is bound to be someone else amoung 150 million users who have it. That doesn't make it a "common problem."
If you tell us what the problem is specifically and what you have done so far to try to resolve it someone can probably help you.

Airport time capsule Extreme dropping connection issue i have already upgraded new firmware 7.7.3 but problem is still in wifi connectivity drop please solve this issue i have expanded my money in tc drive

time capsule drop wifi connection issue .I have already upgraded new firmware 7.7.3 but problem in not solve i am very confuse to resolving this issue.also i attached my log here.
May 15 11:37:43
5
Initialized (firmware 7.7.3).
May 15 11:37:50
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 11:37:50
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 11:37:50
5
Rotated TKIP group key.
May 15 11:37:51
5
Clock synchronized to network time server time.apple.com (adjusted +1 seconds).
May 15 11:37:54
5
Associated with station b8:e8:56:1f:2c:98
May 15 11:37:54
5
Installed unicast CCMP key for supplicant b8:e8:56:1f:2c:98
May 15 11:38:27
5
Associated with station 78:a3:e4:ba:90:42
May 15 11:38:27
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 11:39:14
5
Connection accepted from [::ffff:192.168.1.170]:49439.
May 15 11:40:49
5
SMB/CIFS login OK from [email protected].
May 15 11:43:14
5
Connection accepted from [::ffff:192.168.1.170]:49452.
May 15 11:43:19
5
Connection accepted from [::ffff:192.168.1.170]:49454.
May 15 11:43:20
5
Connection accepted from [::ffff:192.168.1.170]:49456.
May 15 11:43:42
5
Disassociated with station b8:e8:56:1f:2c:98
May 15 11:43:43
5
Rotated TKIP group key.
May 15 11:44:20
5
Connection accepted from [::ffff:192.168.1.170]:49460.
May 15 11:45:21
5
SMB/CIFS login OK from [email protected].
May 15 11:47:33
5
Associated with station b8:e8:56:1f:2c:98
May 15 11:47:33
5
Installed unicast CCMP key for supplicant b8:e8:56:1f:2c:98
May 15 11:47:34
5
Disassociated with station b8:e8:56:1f:2c:98
May 15 11:47:35
5
Rotated TKIP group key.
May 15 11:47:57
5
Associated with station e4:92:fb:dc:02:0b
May 15 11:47:57
5
Installed unicast CCMP key for supplicant e4:92:fb:dc:02:0b
May 15 11:49:25
5
SMB/CIFS login OK from [email protected].
May 15 11:50:37
5
Connection accepted from [::ffff:192.168.1.170]:49472.
May 15 11:50:42
5
Connection accepted from [::ffff:192.168.1.170]:49474.
May 15 11:50:44
5
Connection accepted from [::ffff:192.168.1.170]:49476.
May 15 11:51:18
5
SMB/CIFS login OK from [email protected].
May 15 11:51:25
5
SMB/CIFS login OK from [email protected].
May 15 11:51:53
5
Connection accepted from [::ffff:192.168.1.170]:49478.
May 15 11:53:07
5
Idle timeout for station e4:92:fb:dc:02:0b
May 15 11:53:07
5
Disassociating with station e4:92:fb:dc:02:0b (reserved 4).
May 15 11:53:07
5
Disassociated with station e4:92:fb:dc:02:0b
May 15 11:53:07
5
Rotated TKIP group key.
May 15 11:54:45
5
Connection accepted from [::ffff:192.168.1.170]:49497.
May 15 11:54:52
5
Connection accepted from [::ffff:192.168.1.170]:49499.
May 15 11:54:57
5
Connection accepted from [::ffff:192.168.1.170]:49502.
May 15 11:55:15
5
Connection accepted from [::ffff:192.168.1.170]:49504.
May 15 11:55:24
5
Connection accepted from [::ffff:192.168.1.170]:49506.
May 15 11:55:45
5
Connection accepted from [::ffff:192.168.1.170]:49508.
May 15 12:05:39
5
SMB/CIFS login OK from [email protected].
May 15 12:05:40
5
unloading current configuration.
May 15 12:05:55
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:05:55
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:05:55
5
Rotated TKIP group key.
May 15 12:05:56
5
Clock synchronized to network time server time.apple.com (adjusted +0 seconds).
May 15 12:06:00
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:06:00
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:06:45
5
Disassociated with station 78:a3:e4:ba:90:42
May 15 12:06:45
5
Rotated TKIP group key.
May 15 12:07:19
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:07:19
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:09:15
5
Connection accepted from [::ffff:192.168.1.170]:49576.
May 15 12:09:35
5
Connection accepted from [::ffff:192.168.1.170]:49578.
May 15 12:09:49
5
Connection accepted from [::ffff:192.168.1.170]:49580.
May 15 12:25:40
5
Connection accepted from [::ffff:192.168.1.170]:49709.
May 15 12:25:51
5
Connection accepted from [::ffff:192.168.1.170]:49711.
May 15 12:26:12
5
Connection accepted from [::ffff:192.168.1.170]:49717.
May 15 12:27:40
5
Connection accepted from [::ffff:192.168.1.170]:49723.
May 15 12:27:41
5
unloading current configuration.
May 15 12:27:56
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:27:56
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:27:56
5
Rotated TKIP group key.
May 15 12:28:00
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:28:00
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:29:23
5
SMB/CIFS login OK from [email protected].
May 15 12:29:31
5
Connection accepted from [::ffff:192.168.1.170]:49730.
May 15 12:29:31
5
Connection accepted from [::ffff:192.168.1.170]:49732.
May 15 12:34:15
5
Connection accepted from [::ffff:192.168.1.170]:49739.
May 15 12:34:16
5
unloading current configuration.
May 15 12:34:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:34:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:34:31
5
Rotated TKIP group key.
May 15 12:34:49
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:34:50
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:36:07
5
Connection accepted from [::ffff:192.168.1.170]:49745.
May 15 12:36:08
5
Connection accepted from [::ffff:192.168.1.170]:49747.
May 15 12:40:40
5
Associated with station 10:68:3f:46:d2:69
May 15 12:40:41
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 12:40:41
5
Deauthenticating with station 10:68:3f:46:d2:69 (reserved 2).
May 15 12:40:41
5
Disassociated with station 10:68:3f:46:d2:69
May 15 12:41:48
5
Disassociated with station 10:68:3f:46:d2:69
May 15 12:42:12
5
Connection accepted from [::ffff:192.168.1.170]:49759.
May 15 12:42:13
5
unloading current configuration.
May 15 12:42:28
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:42:28
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:42:28
5
Rotated TKIP group key.
May 15 12:42:32
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:42:32
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:44:04
5
Connection accepted from [::ffff:192.168.1.170]:49768.
May 15 12:44:10
5
Connection accepted from [::ffff:192.168.1.170]:49771.
May 15 12:45:03
5
Connection accepted from [::ffff:192.168.1.170]:49773.
May 15 12:45:03
5
unloading current configuration.
May 15 12:45:18
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 12:45:18
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 12:45:18
5
Rotated TKIP group key.
May 15 12:45:23
5
Associated with station 78:a3:e4:ba:90:42
May 15 12:45:23
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 12:46:23
5
Associated with station e4:92:fb:dc:02:0b
May 15 12:46:24
5
Installed unicast CCMP key for supplicant e4:92:fb:dc:02:0b
May 15 12:46:43
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:46:43
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:46:58
5
Connection accepted from [::ffff:192.168.1.170]:49780.
May 15 12:47:02
5
Connection accepted from [::ffff:192.168.1.170]:49782.
May 15 12:47:05
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:05
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:13
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:14
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:27
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:30
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:47:39
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:47:40
5
Rotated TKIP group key.
May 15 12:47:44
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:47:44
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:49:07
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:49:07
5
Rotated TKIP group key.
May 15 12:49:13
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:49:13
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:19
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:20
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:20
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:26
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:30
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:30
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:31
5
Rotated TKIP group key.
May 15 12:51:31
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:31
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:34
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:38
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:40
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:40
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:40
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:41
5
Rotated TKIP group key.
May 15 12:51:42
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:42
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:47
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:49
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:49
5
Installed unicast CCMP key for supplicant 24:fd:52:d0:3c:50
May 15 12:51:55
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:57
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:51:59
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:51:59
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:51:59
5
Rotated TKIP group key.
May 15 12:52:05
5
Associated with station 24:fd:52:d0:3c:50
May 15 12:52:09
5
Deauthenticating with station 24:fd:52:d0:3c:50 (reserved 2).
May 15 12:52:09
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:52:20
5
Disassociated with station 24:fd:52:d0:3c:50
May 15 12:59:22
5
Connection accepted from [::ffff:192.168.1.170]:49810.
May 15 12:59:22
5
Connection accepted from [::ffff:192.168.1.170]:49812.
May 15 13:00:07
5
Connection accepted from [::ffff:192.168.1.170]:49817.
May 15 13:00:07
5
unloading current configuration.
May 15 13:00:22
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:00:22
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:00:22
5
Rotated TKIP group key.
May 15 13:00:35
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:00:35
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:02:00
5
Connection accepted from [::ffff:192.168.1.170]:49826.
May 15 13:02:00
5
Connection accepted from [::ffff:192.168.1.170]:49828.
May 15 13:03:14
5
Connection accepted from [::ffff:192.168.1.170]:49832.
May 15 13:03:15
5
unloading current configuration.
May 15 13:03:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:03:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:03:31
5
Rotated TKIP group key.
May 15 13:04:03
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:04:03
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:05:07
5
Connection accepted from [::ffff:192.168.1.170]:49843.
May 15 13:05:07
5
Connection accepted from [::ffff:192.168.1.170]:49845.
May 15 13:06:15
5
Connection accepted from [::ffff:192.168.1.170]:49848.
May 15 13:06:16
5
unloading current configuration.
May 15 13:06:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 3).
May 15 13:06:31
5
Deauthenticating with station ff:ff:ff:ff:ff:ff (reserved 2).
May 15 13:06:31
5
Rotated TKIP group key.
May 15 13:07:04
5
Associated with station 78:a3:e4:ba:90:42
May 15 13:07:04
5
Installed unicast CCMP key for supplicant 78:a3:e4:ba:90:42
May 15 13:08:08
5
Connection accepted from [::ffff:192.168.1.170]:49854.
May 15 13:08:09
5
Connection accepted from [::ffff:192.168.1.170]:49856.
May 15 13:08:20
5
Connection accepted from [::ffff:192.168.1.170]:49858.
May 15 13:12:31
5
unloading current configuration.
May 15 13:32:36
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:32:57
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:09
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:22
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 13:33:33
1
WPA handshake failed with STA 1c:7b:21:9c:20:fd likely due to bad password from client
May 15 15:21:21
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 15:21:26
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
May 15 15:21:41
1
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client

It says you have the wrong password.
WPA handshake failed with STA 10:68:3f:46:d2:69 likely due to bad password from client
Reset the TC to factory and start again.
But do not be surprised if the v5 utility no longer works to do the setup.

POS-DM, BIW & R/3 posting issue after BIW patch updation

Landscape details:
SAP IS-Retail (ECC 6.0), SAP POS (Triversity GM 9.5.10), PI 7.0, BIW/POS-DM 7.0
Issue Detail
We have upgraded the patch level of Support package BI_CONT in BIW from 5 to 11 in production server and after that following issues have started:
1.     The duplicate posting started in R/3 i.e. if some POS EoD (TLog) file is already posted from POS-DM to R/3 and if the same file comes to POS-DM again then it gets posted in R/3 again. It was not happening before updating the patch, it used to get stop in POS-DM only.
2.     We have some EANs which starts with ZERO, those POS transaction doesnu2019t get posted in BIW Cubes and R/3 wherein the ZERO prefix articles exists. It stuck in POS-DM with the error u201CUnknown EAN/UPC numberu201D. But this error comes only if we enable the u201CMstr Data Filteru201D check from General Setting in /N/POSDW/IMG. If we disable this check then the data gets posted in R/3 but it doesnu2019t go in RSA7 & BIW Cubes.
3.     Before updating the patch the u201CMstr Data Filteru201D check was disabled and our posting was happening perfectly in R/3 as well BIW. What we understand is that, this check is required to pick the Article Code from masters with reference of EAN number which comes in POS TLog file and then it gets posted. We had written a ROUTINE in update rules to pick the Article Code from masters after truncating ZERO prefix from EAN, because the masters which we upload in R/3 with ZERO prefix EAN are getting updated in BIW without ZERO prefix.
4.    In the T-Code /N/POSDW/MON0, we are not able to change the status of processed transaction from 4 (completed) to 1 (ready) or vice-a-versa. Earlier we were able to do the same. This is required to re-process the transactions after doing the corrections in errors occurred at the time of first processing.
Regards
Amar Preet Singh

Hi
1)Duplicate posting in R/3 : check the 'Tasks' configuration WPUUMS & WPUTAB in /N/POSDW/IMG in POSDM.
2) Write a Routine in BI side to allow EAN's with prefix Zeros
3) master data filter is used to check the data with BI master data. Master data filter should always be used while data posting.
4) The status should be first changed from completed to cancelled/rejected and then cancelled to Ready status.
    Then you will be able to reprocess the posdm data to ISR.
Regards
Abhijit

After recent patch upgrade, BW delta Data loads for 2LIS_02_ITM failing

Hi All
We have patched our BW 3.5 system from 16 to 25. After updating patches, I am geetting delta load issues.
2lis_02_itm and 2lis_02_scl delta loads are taking long long time. Deltas are failing even for 3000 records . some time it is taking 14 hours . Delta loads are failing and I am getting below message. Please advise.
I am still getting below dump and i could not find any errors in
ST22. Please see below error.
Processing in Warehouse timed out; processing steps mising
Diagnosis
Processing the request in the BW system is taking a long time and the
processing step Update rules has still not been executed.
System response
<DS:DE.RSCALLER>Caller is still missing.
Procedure
Check in the process overview in the BW system whether processes are
running in the BW system under the background user.
If this is not the case, check the short dump overview in the BW system.
Thanks
Pramod

Hello Pramod,
Is this load is to load to initial level ODS? If Yes I understand that you have issue in loading but not at activation of the ODS?
Normally this kind of issue comes during the activation of ODS.
1. If you are getting this during the data loads, then try to check loading only to PSA first and then from PSA to target? And check how much time that it's taking as this will help to track the issue whether its present in Source or in BW?
2. If the load is fine till PSA then try loading the same to ODS and then check whether this issue is present or not?
3. At the same you need to check the source side the system load and the number of processors which are available?
4. Did you perform the delta queue draining before the stack upgrade in R/3 or not? Normally as a pre-requisite this needs to be done if not then you will have issues in extracting the data!
5. Finally this can be avoided by having Initwithout data transfer and then performing the Delta loads. BUt for this need to first extract all the data from Source to BW and then take a down time in R/3 for few min and perform this activity so that the Init Timstamp will be reset properly and the Delta should work fine for you.
Do get back to us with more details.
Thanks
Murali M

System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8

Hi,
We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
Following is our system environment
SAP Release.............. "640"
Application server....... "abci"
Operating system......... "SunOS"
Release.................. "5.10"
Hardware type............ "sun4v"
Database server.......... "abdb"
Database type............ "ORACLE"
Database name............ "ABP"
Database owner........... "SAPABP"
SAP kernel............... "640"
Database version......... "OCI_920 "
Patch level.............. "175"
Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
Runtime Errors         SYSTEM_CORE_DUMPED
Date and Time          14.04.2008 09:26:17
ShrtText
     Process terminated by signal 11.
What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
    processor discovered an invalid system state.
What can you do?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
Error analysis
    An SAP System process was terminated by an operating system signal.
    Possible reasons for this are:
    1. Internal SAP System error.
    2. Process was terminated externally (by the system administrator).
               Last error logged in SAP kernel
    Component............ "Taskhandler"
    Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
    Version.............. 1
    Error code........... 11
    Error text........... "ThSigHandler: signal"
    Description.......... " "
    System call.......... " "
    Module............... "thxxhead.c"
    Line................. 9780
How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.
    Save this file under another name.
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
    2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
Kindly help.
Regards
Sachin
Edited by: Sachin N on Apr 14, 2008 12:26 PM

No. If the environment would be wrong the system wouldn´t start up.
Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
Markus

Logic Remote connectivity issues after updating to iOS 8 (solved!)

Has anyone else has been experiencing connectivity issues with Logic Remote after updating to iOS 8?
After updating to iOS 8 I could no longer connect so I sent a feedback report to Apple and got a response that cleared up my problem immediately:
Navigate to the following directory on your desktop system running GarageBand:
~/Library/Containers/com.apple.garageband10/Data/Library/Preferences/
You can quickly navigate there using the “Go” menu in Finder -> Go To Folder (shift-command-G), then copy this path:
~/Library/Containers/com.apple.garageband10/Data/Library/Preferences/
In the Preferences folder should be a file named "com.apple.garageband10.cs”.
Make sure GarageBand is not running and delete the "com.apple.garageband10.cs” file.
Relaunch GarageBand and see if you should now be able to connect.
The same can be done for Logic by navigating to:
~/Library/Preferences/
And deleting "com.apple.logic.pro.cs" and restarting Logic.
Note that doing this will fix Logic Remote connectivity issues (and possibly other problems with latency and mixer functionality) but will also delete any other Controller settings that you've configured with Logic, if you happen to be using another controller of some sort.

Thanks very much! This solved my connection problem.

Backup error after kernel patch upgrade

Hi.
I have a backup problem after the kernel patch upgrade. I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
I have upgraded kernel patch from 1655 to 2337.
Afterward, I am getting following backup error:
BR280I Time stamp 2007-11-06 09.29.01
BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
BR232E 0 of 115 files saved by backup utility
BR280I Time stamp 2007-11-06 09.29.01
BR231E Backup utility call failed
Does anyone know how to correct this?
Thank you.

Hi Jun,
backint is a link file that is in SAP kernel directory which links to the backup client on the server.
eg:
lrwxrwxrwx 1 root other 32 Aug 13 2004 backint -> /usr/openv/netbackup/bin/backint
As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
Cheers,
Nisch

Has any seen collection issues after 11g database upgrade?

We do have an SR open.
Just wondering if anyone else has experienced collection issues after upgrading the db to 11g? Our technical folks are hoping it is something else but for the past few weeks we have seen random issues stemming from collections. We run a full collections 5 nights a week. There are material transactions occurring during the two plus hours of collections. This seems to be randomly skewing on hand snapshots in collections as well as missing supply i.e. work orders. Only impacts a fraction of the records in material transactions and they are different every night.
Reason I believe it has to do with transactions during collections is one collection run out of the five is generally pretty good...Sunday evening for there is very limited transactions taking place on this evening.
Thanks in advance

Answer to above question not required now as:
Having read the 24th December update of note 761570.1 - 'Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade' I have decided to upgrade the database to 11.2.0.x by following the Path C option.
Unfortunately as the 11.2.0.x upgrade isn't covered by MWIZ yet I will have to follow the manual steps.

Bluetooth connectivity issues after updating to OS X 10.10.3

I have been experiencing issues with bluetooth mouse connectivity (apple magic mouse) after updating OS X to 10.10.3. My Macbook Retina 15" pro (early 2013) keeps losing connection with the mouse. Switching the mouse on/off helps in re- establishing connection between the mouse and the laptop for a few seconds. I was under the impression that this update of Yosemite was intended to rectify bluetooth and wifi connectivity issues. Any suggestions/advice welcome.

Back up all data.
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/com.apple.Bluetooth.plist
Right-click or control-click the line and select
Services ▹ Reveal
from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Repository connect issue after MDM Patch Upgrade

Similar Messages

Maybe you are looking for