Can not Check-in/Upload the document file in RTC
Hi
I am trying to upload the MS word document file in RTC and the file is of size of 47.5MB, while uploading this file I am getting below error:
Failed to upload File /MyInfo.doc
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request". Examine any further details here or look in the server log files for more information on how to resolve the issue.
I can not see any more information in the server log file.
I have tried to set the file properties as below:
I set the MIME type and Line Delimiter to "text/plain" with the Line Delimiter set to "Platform".Also tried it settings the MIME Type to application/unknown and Delimiter as None but these both settings resulted in the same issue.
Let me know if anyone has any solution for this issue.
I am trying to upload the MS word document file in RTC and the file is of size of 47.5MB, while uploading this file I am getting below error:
I can not see any more information in the server log file.
I have tried to set the file properties as below:
I set the MIME type and Line Delimiter to "text/plain" with the Line Delimiter set to "Platform".Also tried it settings the MIME Type to application/unknown and Delimiter as None but these both settings resulted in the same issue.
Let me know if anyone has any solution for this issue.
3 answers
Hi
Thanks for the reply.
I also have the document with same properties as mentioned by you but still getting the below error:
Failed to upload File /MyInfo.doc
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request". Examine any further details here or look in the server log files for more information on how to resolve the issue.
Thanks for the reply.
I also have the document with same properties as mentioned by you but still getting the below error:
Failed to upload File /MyInfo.doc
CRJAZ1247I The request to the server failed. The server returned the http error 400 with error text "Bad Request". Examine any further details here or look in the server log files for more information on how to resolve the issue.
You could try to follow https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=63105
and do some SCM server side logging. Add the statements to the log4j.properties of your ccm application.
# Uncomment these lines to create a versioned content access log file
# WARNING : These files will grow fairly fast, if you wish to process this accurately, you
# will could use a FileAppender and pipe it into another script/program.
#log4j.appender.scm_scaa=org.apache.log4j.RollingFileAppender
#log4j.appender.scm_scaa.layout=org.apache.log4j.PatternLayout
#log4j.appender.scm_scaa.layout.ConversionPattern=%m %n
#log4j.appender.scm_scaa.File=scaa_content.log
#log4j.appender.scm_scaa.MaxBackupIndex=10
#log4j.appender.scm_scaa.MaxFileSize=7000KB
#log4j.logger.scm_scaa=TRACE, scm_scaa
The log format is as follows:
SCAA:{1}/{2},{3},{4},{5}/{6},{7}
where
1 is the user id
2 is the versionable item type (likely FileItem)
3 is the versionable name (not full path, just the last segment)
4 is the versionable item id
5 is the versionable state id
6 is the component name
7 is the component item id
and do some SCM server side logging. Add the statements to the log4j.properties of your ccm application.
# Uncomment these lines to create a versioned content access log file
# WARNING : These files will grow fairly fast, if you wish to process this accurately, you
# will could use a FileAppender and pipe it into another script/program.
#log4j.appender.scm_scaa=org.apache.log4j.RollingFileAppender
#log4j.appender.scm_scaa.layout=org.apache.log4j.PatternLayout
#log4j.appender.scm_scaa.layout.ConversionPattern=%m %n
#log4j.appender.scm_scaa.File=scaa_content.log
#log4j.appender.scm_scaa.MaxBackupIndex=10
#log4j.appender.scm_scaa.MaxFileSize=7000KB
#log4j.logger.scm_scaa=TRACE, scm_scaa
The log format is as follows:
SCAA:{1}/{2},{3},{4},{5}/{6},{7}
where
1 is the user id
2 is the versionable item type (likely FileItem)
3 is the versionable name (not full path, just the last segment)
4 is the versionable item id
5 is the versionable state id
6 is the component name
7 is the component item id