on 03-24-2009 12:12 PM
Hi All,
I go 4 central system installation ( OS : Linux , Database :Oracle 10g)but hangs at step check DDIC password while ABAP report "RADDBDIF" is running.
Error log is
INFO 2009-03-24 17:23:43
Function call was successful.
INFO 2009-03-24 17:23:43
Version 700 of remote SAP System RTD accepted.
INFO 2009-03-24 17:23:44
Setting new application function INST_EXECUTE_REPORT.
INFO 2009-03-24 17:23:44
Generating interface for remote function.
INFO 2009-03-24 17:23:46
Function call was successful.
INFO 2009-03-24 17:23:46
Function interface generated successfully.
INFO 2009-03-24 17:23:46
Technical properties of function set successfully.
INFO 2009-03-24 17:23:46
Information for application function INST_EXECUTE_REPORT copied to local Repository.
INFO 2009-03-24 17:23:46
Function module INST_EXECUTE_REPORT set successfully.
INFO 2009-03-24 17:23:46
Executing function call INST_EXECUTE_REPORT.
ERROR 2009-03-24 17:23:49
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
INFO 2009-03-24 17:23:49
RFC connection closed.
ERROR 2009-03-24 17:23:49
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
ERROR 2009-03-24 17:23:49
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Kindly suggest for the same.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Solution is to give appropriate permission to directory /usr/sap/trans/tmp.
/usr/sap/trans # chmod 777 tmp
/usr/sap/trans # ll
root root 26 Nov 17 14:10 tmp
/usr/sap/trans # cd tmp/
/usr/sap/trans/tmp # ll
fp1adm sapsys 1094 Nov 17 14:10 RADDBDIF.FP1
/usr/sap/trans/tmp #
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
I've just experienced this problem -
I had previously uninstalled SAP and had deleted the OS users and groups. When I recreated then I created them with different UID and GIDs
I think for some reason sapinst got confused with this. When it tries to write the log file for RADDBDIF in /usr/sap/trans/tmp the group that owns that log file is 502 which is the old GID for sapsys. I did a chown <sid>adm:sapsys on that log file and resumed the installation which went through
I would guess you somehow worked around your issue - but might be useful if anyone else experiences the problem.
Regards
Leigh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Polina,
Now error is changed :
tail -f sapinst.log
ERROR 2009-04-01 15:19:51
FRF-00007 Unable to open RFC connection.
ERROR 2009-04-01 15:19:51
MUT-03025 Caught ERfcExcept in Modulecall: No logon possible (no hw ID received by mssg server).
ERROR 2009-04-01 15:19:51
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
did you restart the SAP after changes?
If yes and you have still the error it would be helpfull to set the debugger break point bevor the call of the function 'APPEND_PROTOCOL' (see function SUBST_WRITE_PROTOCOL calling from the programm RADDBDIF). Start the RADDBDIF from SAP directly and follow the debugger steps. So you can find out the cause of your problem.
Polina.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Polina,
I hava changed the permissions from root to adm with 775)...
but still hangs at same step..
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 bin
drwxrwx--x 2 rtdadm sapsys 4096 Apr 1 13:01 buffer
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 cofiles
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 data
drwxrwx--x 5 rtdadm sapsys 4096 Jan 6 16:24 EPS
drwxrwx--x 2 rtdadm sapsys 4096 Jan 6 16:24 etc
drwxrwx--x 2 rtdadm sapsys 12288 Feb 18 16:16 log
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 sapnames
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 tmp
regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
root is definitly wrong. The SAP (if you start any program that should read or write in UNIX directories) access the files with the user <sysid>adm. The only permission SAP is checking on it is the owner permission. The permissions are read by the start of the SAP system and were cashed. So that the changes of the owner doesn't have effect bevor the restart of the system.
if you have 700 <sapadm> <sapgroup> <dir> you can read and write into the <dir>
if you have 770 root <sapgroup> <dir> then <sapadm> can not read and write (in spite of the fact that <sapadm> is on the <sapgroup>).
Sorry for my English:-)
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Polina,
I have changed owner for tmp now it is :
drwxrwx--x 2 root sapsys 4096 Feb 18 16:16 tmp
and file /dir is created under rtdadm user.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Amit,
the /tmp-directory is not relevant. Just the /usr/sap/trans/tmp.
Why does your list show the id 504 as the owner of the /usr/sap/trans/tmp (your sap-adm user is the rtdadm or not?). For my understanding the owner of this .../trans/tmp directoty should be the rtdadm.
Did you try to create a file under /usr/sap/trans/tmp with the rtdadm user?
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Polina,
These are the permissions for my /trans and /tmp files...
ls -lrth /tmp/
total 92K
drwxr-xr-x 3 root root 4.0K Mar 31 13:04 sapinst_exe.3621.1238484856
drwxrwxrwx 3 root sapinst 4.0K Mar 31 13:04 sapinst_instdir
-rw-r----- 1 root root 45K Mar 31 13:04 +~JF11509.tmp
drwx------ 2 orartd dba 4.0K Mar 31 14:05 ssh-kWXdu11776
drwx------ 3 orartd dba 4.0K Mar 31 14:05 gconfd-orartd
-rw-rr 1 orartd dba 111 Mar 31 14:05 sealert.log
srw------- 1 orartd dba 0 Mar 31 14:05 scim-socket-frontend-orartd
srw------- 1 orartd dba 0 Mar 31 14:05 scim-panel-socket:2-orartd
srw------- 1 orartd dba 0 Mar 31 14:05 scim-helper-manager-socket-orartd
srwxr-xr-x 1 orartd dba 0 Mar 31 14:05 scim-bridge-0.3.0.socket-501@localhost:2.0
drwx------ 2 orartd dba 4.0K Mar 31 14:05 keyring-h3iXSE
drwx------ 2 orartd dba 4.0K Mar 31 14:05 virtual-orartd.guFTr4
srwxr-xr-x 1 orartd dba 0 Mar 31 14:05 mapping-orartd
drwxr-x--- 2 orartd dba 4.0K Mar 31 14:50 hsperfdata_orartd
drwx------ 2 orartd dba 4.0K Mar 31 15:45 orbit-orartd
-rw-rr 1 root root 6 Apr 1 12:46 scim-bridge-0.3.0.lockfile-0@localhost:1.0
-rw-rr 1 orartd dba 6 Apr 1 13:05 scim-bridge-0.3.0.lockfile-501@localhost:2.0
isrxi:rtdadm 8> ls -lrth /usr/sap/trans/
total 44K
drwxrwx--x 2 root sapsys 4.0K Jan 6 16:24 etc
drwxrwx--x 5 root sapsys 4.0K Jan 6 16:24 EPS
drwxrwx--x 2 504 sapsys 4.0K Feb 18 16:16 tmp
drwxrwx--x 2 root sapsys 4.0K Feb 18 16:16 sapnames
drwxrwx--x 2 root sapsys 12K Feb 18 16:16 log
drwxrwx--x 2 root sapsys 4.0K Feb 18 16:16 data
drwxrwx--x 2 root sapsys 4.0K Feb 18 16:16 cofiles
drwxrwx--x 2 root sapsys 4.0K Feb 18 16:16 bin
drwxrwx--x 2 root sapsys 4.0K Apr 1 13:01 buffer
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
is the owner of the .../trans/tmp directory still the <sap>adm? Can you go to this ../tmp directory (log in as <sap>adm) and try to create a file (with touch or something like this)?
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
Now I go for fresh installation and then see what happens.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
After go for fresh installation, I am still getting the same error as I mentioned earlier...in the installation phase "Run Abap Reports " hangs when executing report " RADDBDIF
INFO 2009-04-01 10:02:50
Executing function call INST_EXECUTE_REPORT.
ERROR 2009-04-01 10:02:51
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
INFO 2009-04-01 10:02:51
RFC connection closed.
ERROR 2009-04-01 10:02:51
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
ERROR 2009-04-01 10:02:51
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Kindly help me for the same.
Regards,
Amit
Amit,
I've just forgotten - you have to restart SAP after changing the unix permissions for <SYS>adm. And try once more:-)
Regards
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Polinda,
Thanx for kind response.
I have changed the owner :
drwxrwx--x 2 rtdadm sapsys 4096 Feb 18 16:16 /usr/sap/trans/tmp/
drwxrwx--x 11 rtdadm sapsys 4096 Jan 6 16:24 /usr/sap/trans
But same problem exists.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
please change the owner of the /trans and /tmp directory to <SYS>adm and try again.
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Authorization for /usr/sap/trans/tmp dir is :
[root@isrxi ~]# ls -ld /usr/sap/trans/tmp/
drwxrwx--x 2 root sapsys 4096 Feb 18 16:16 /usr/sap/trans/tmp/
regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check also the permissions of /usr/sap/trans/tmp.
regards
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Polinda,
permissions of the /usr/sap/trans directory is :
drwxrwx--x 11 root sapsys 4096 Jan 6 16:24 /usr/sap/trans/
and space :
/dev/mapper/VolGroup_ID_22106-LogVol5
20G 9.4G 8.9G * 52%* /usr
adm user permissions :
isrxi:rtdadm 2> id
uid=504(rtdadm) gid=507(sapsys) groups=506(sapinst),507(sapsys),508(dba),509(oper)
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo Amit,
please check the permissions of the /usr/sap/trans directory. You <SYS>adm user must have full read uns write permissions there.
Do you have enough space on this directory ?
Regards
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
My RAM and swap memories are :
Mem: 12299040k total, 11065396k used, 1233644k free, 496628k buffers
Swap: 28831156k total, 484k used, 28830672k free, 8921700k cached
So I think this is not the issue related to memory.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit
regarding this problem, you need to increase RAM and swap size.
Regards
Bandla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear All,
To resolve this problem I have done following things :
1). Stop & Start Sap
2). Updation of Kernel
3). Logon to SapGui And manually run the report " RDDBDIF" but getting a dump.Dump is given below :
Runtime Errors RAISE_EXCEPTION
Date and Time 25.03.2009 10:32:50
Short text
Exception condition "WRITE_FAILED raised
What happened?
The current ABAP/4 program encountered an unexpected
situation.
Error analysis
A RAISE statement in the program "SAPLSUGI" raised the exception
condition "WRITE_FAILED".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-
Trigger Location of Runtime Error
Program SAPLSUGI
Include LSUGIU08
Row 77
Module type (FUNCTION)
Module Name SUBST_WRITE_PROTOCOL
Source Code Extract
Line SourceCde
47 LV_FILENAME = 'UNKNOWN.+++'.
48 REPLACE '+++' WITH SY-SYSID INTO LV_FILENAME.
49 ENDCASE.
50 * create complete path to the logfile
51 CALL FUNCTION 'STRF_SETNAME'
52 EXPORTING
53 DIRTYPE = LC_PATHTYPE
54 FILENAME = LV_FILENAME
55 SUBDIR = LC_SUBPATH
56 IMPORTING
57 FILE = EFNAME.
58
59 ELSE. EFNAME = IFNAME.
60 ENDIF.
61 MEMFILE = EFNAME.
62 * export memfile to memory id mem_id.
63 GV_MEM_FILE = MEMFILE.
64 EXPORT MEMFILE GV_MEM_FILE TO MEMORY ID MEM_ID.
65 CALL FUNCTION 'APPEND_PROTOCOL'
66 EXPORTING
67 ACCEPT_NOT_INIT = ' '
68 CLOSE_FILE = 'X'
69 CONDENSE = 'X'
70 MASTER_LANGU = 'D'
71 OPEN_FILE = 'X'
72 TABLES
73 XMSG = P_TAB
74 EXCEPTIONS
75 OTHERS = 1.
76 IF SY-SUBRC >< 0.
>>>>> RAISE WRITE_FAILED.
78 ENDIF.
79 REFRESH P_TAB.
80
81 ENDFUNCTION.
Trace files are :
[root@isrxi AS]# cat dev_rfc.trc
ERROR file opened at 20090324 162443 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [2] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [2] : returns 3:RFC_SYS_EXCEPTION
>TS> Tue Mar 24 16:28:49 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [3] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [3] : returns 3:RFC_SYS_EXCEPTION
>TS> Tue Mar 24 16:35:12 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [4] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [4] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090324 164720 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
>TS> Tue Mar 24 16:47:38 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [2] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [2] : returns 3:RFC_SYS_EXCEPTION
>TS> Tue Mar 24 16:47:43 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [3] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [3] : returns 3:RFC_SYS_EXCEPTION
>TS> Tue Mar 24 16:47:47 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [4] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [4] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090324 164854 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090324 172349 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090324 175325 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090325 095857 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
>TS> Wed Mar 25 09:59:44 2009
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [2] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [2] : returns 3:RFC_SYS_EXCEPTION
ERROR file opened at 20090325 104829 IST, SAP-REL 700,0,66 RFC-VER 3 841435 MT-SL
T:46912508454944 Error in program 'sapinstexe': ======> Exception condition "WRITE_FAILED" raised.
T:46912508454944 Error in program 'sapinstexe': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:46912508454944 Error in program 'sapinstexe': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
sapinst.log is :
INFO 2009-03-25 10:48:28
Function call was successful.
INFO 2009-03-25 10:48:28
Function interface generated successfully.
INFO 2009-03-25 10:48:28
Technical properties of function set successfully.
INFO 2009-03-25 10:48:28
Information for application function INST_EXECUTE_REPORT copied to local Repository.
INFO 2009-03-25 10:48:28
Function module INST_EXECUTE_REPORT set successfully.
INFO 2009-03-25 10:48:28
Executing function call INST_EXECUTE_REPORT.
ERROR 2009-03-25 10:48:29
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
INFO 2009-03-25 10:48:29
RFC connection closed.
ERROR 2009-03-25 10:48:29
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
ERROR 2009-03-25 10:48:29
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Kindly suggest 4 the same.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit
I saw a similar problem wherein the solution was given as:
*The issue was with the DDIC password. When I was setting up the install I clicked on change password for the DDIC and set it to what seems to be a different password from the default.
I uninstalled the instance and reinstalled it and left the DDIC password untouched*
Other possible solutions given for the same were:
1. Is this an error that happens at around 96% into the installation? It means that your new SAP system come up fast enough. So break out of the installation, bring you system up manually using the newly installed SAP MMC on your desktop, and then restart the install.
or
2. what you can also try is
logoff from the admin user doing the installation
log in into with user <SID>adm
Try to restart the SAP instance
logout and login with the user doing the installation, and should works
Hope this can help you.
3. Also, Try searching things for keyword RADDBDIF
Please check if any of them suits your situation as well
Regards
Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
the restart should not be the propely solution for your problem. Please make the checks Worren Wong have mentioned in the another thread (6550169, s. note from Juan). The function called by the program RADDBDIF can not open the log file.
Regards
Polina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Juan,
Thanx for kind response.
I go for ECC 6.0 installation.
I have manually stop and start SAP and DB,but no use ,again hangs at ABAP report RADDBDIF.
Regards,
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.