SP2-0027: Input is too long ( 2499 characters) - line ignored

Hi All,
I am getting SP2-0027: Input is too long (> 2499 characters) - line ignored error when running a script. It looks like it is a limitation of the buffer size to be 2500 characters. I tried both the command prompt sqlplus and SQL Plus, nothing worked. Is there any other way to avoid that as I have to migrate the whole database which is in insert statement's script form.
BTW I am using Oracle 10g
Thanks

You're going to have to add line feeds to that file to make the line sizes smaller. Hopefully you're on Unix where you can use sed.

Similar Messages

SP2-0027: Input is too long -error on pl/sql procedure

Hi,
We are on Oracle 11.2.0.2 on Solaris 10. I have a procedure call that errors out with this error:
SP2-0027: Input is too long (> 2499 characters) - line ignored
It is one single procedure but it takes too many long inputs in it. This giant procedure call -with some names changed - is as below - is there a way I can avoid this errro? I will be thankful for inputs on it.
SQL> exec func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF','co Reporting','NOT',func_j23k_TYPE_ACTION_ARRAY(func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Find in Report List'),LANG_TEXT_TYPE('en_CA', 'Find in Report List'),LANG_TEXT_TYPE('fr_CA', 'Chercher dans la liste des rapports'),LANG_TEXT_TYPE('es_US', 'Buscar en lista de informes')),'/Reporting/el/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open using Excel'),LANG_TEXT_TYPE('en_CA', 'Open using Excel'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format Excel'),LANG_TEXT_TYPE('es_US', 'Abrir usando Excel')),'/Reporting/el/xls/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in PDF'),LANG_TEXT_TYPE('en_CA', 'Open in PDF'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format PDF'),LANG_TEXT_TYPE('es_US', 'Abrir en PDF')),'/Reporting/el/pdf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in HTML'),LANG_TEXT_TYPE('en_CA', 'Open in HTML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format HTML'),LANG_TEXT_TYPE('es_US', 'Abrir en HTML')),'/Reporting/el/html/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in TXT'),LANG_TEXT_TYPE('en_CA', 'Open in TXT'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format TXT'),LANG_TEXT_TYPE('es_US', 'Abrir en TXT')),'/Reporting/el/txt/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in CSV'),LANG_TEXT_TYPE('en_CA', 'Open in CSV'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format CSV'),LANG_TEXT_TYPE('es_US', 'Abrir en CSV')),'/Reporting/el/csv/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Open in XML'),LANG_TEXT_TYPE('en_CA', 'Open in XML'),LANG_TEXT_TYPE('fr_CA', 'Ouvrir au format XML'),LANG_TEXT_TYPE('es_US', 'Abrir en XML')),'/Reporting/el/xml/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL),func_j23k_TYPE_ACTION_TYPE(LANG_TEXT_ARRAY(LANG_TEXT_TYPE('en_US', 'Download Data Extract File'),LANG_TEXT_TYPE('en_CA', 'Download Data Extract File'),LANG_TEXT_TYPE('fr_CA', 'TÃ©lÃ©charger le fichier d''extraction de donnÃ©es'),LANG_TEXT_TYPE('es_US', 'Descargar archivo de extracciÃ³n de datos')),'/Reporting/el/flf/',1,func_TYPE_ACTION_STATUS_ARRAY(),func_TYPE_ACTION_SCREEN_ARRAY(),'NWR',NULL, NULL)), 'MC');
SP2-0027: Input is too long (> 2499 characters) - line ignoredThanks,
OrauserN

It is an sqlplus error..
Did you try this?
begin
func_j23k_TYPE_ADD( 'coR-EXECUTION-SUCCEEDED-XLS-PDF-HTM-TXT-CSV-XML-FLF',
'co Reporting',
'NOT',
end;http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4789399600346029472

SP2-0027: Input is too long error during Apex 4.0 installation

I have come across an error while installing Apex 4.0.
The installation reached the point where it gave a SP2-0027 error
...PAGE 72: Workspace Schemas
...PAGE 73: &PRODUCT_NAME. Workspace Creation
...PAGE 74: Page Views By Day Report
...PAGE 75: Page Views by Application and Page
...PAGE 76: Hourly Usage
...PAGE 77: Usage by Application, for selected hour
...PAGE 78: Page Performance Dashboard
...PAGE 79: Database
SP2-0027: Input is too long (> 2499 characters) - line ignored
wwv_flow_api.create_report_region (
ERROR at line 16:
ORA-06550: line 16, column 1:
PLS-00703: multiple instances of named argument in list
ORA-06550: line 16, column 1:
PL/SQL: Statement ignored
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Following this, I looked up Apex help, and so checked dba_registry
C:\apex>C:\oraclexe\app\oracle\product\10.2.0\server\BIN\sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 13 15:40:05 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys as sysdba
Enter password:
Connected.
SQL> SELECT STATUS FROM DBA_REGISTRY
2 WHERE COMP_ID = 'APEX';
STATUS
LOADING
Please help
Edited by: user4477408 on Jul 19, 2010 3:35 PM
Edited by: user4477408 on Jul 26, 2010 11:29 AM

Did you keep any kind of external references to your pages/reports? From what it looks like, one of your report regions exceeds 2500 characters and APEX is having a hard time crunching it. See if you can find that page, then export that page, delete the region, and import the page on it's own later.
Not sure why it would be such a small area, though. I usually don't have any trouble until I hit 32K characters.

Using DBMS_REDEFINITION.START_REDEF_TABLE I get SP2-0027: Input is too long

Hello, I am using the DBMS_REDEFINITION.START_REDEF_TABLE to migrate a large table to unicore data types. When I attempt this the list of columns is too long and it generates:
SP2-0027: Input is too long (> 2499 characters) - line ignored
Below is the procedure call. Is there a way to over come this?
EXECUTE DBMS_REDEFINITION.START_REDEF_TABLE( -
'FOCUS',
'PREFERRED_CUSTOMER',
'INT_PREFERRED_CUSTOMER', -
'PREFERRED_CUST_KEY PREFERRED_CUST_KEY,SIGNUP_STORE_KEY SIGNUP_STORE_KEY,SIGNUP_ASSOC_EMPKEY SIGNUP_ASSOC_EMPKEY,PREFERRED_CUST_NUM PREFERRED_CUST_NUM, -
ALT_PREFERRED_CUST_NUM ALT_PREFERRED_CUST_NUM,TAX_EXEMPT_NUMBER TAX_EXEMPT_NUMBER,EMPLOYEE_KEY EMPLOYEE_KEY,SIGNUP_DATE SIGNUP_DATE,ALLOW_CONTACT_IND ALLOW_CONTACT_IND, -
ALLOW_DISTRIB_IND ALLOW_DISTRIB_IND, ALLOW_EMAIL_IND ALLOW_EMAIL_IND, ALLOW_EMAIL_IND_EFF_DATE ALLOW_EMAIL_IND_EFF_DATE, ALLOW_MAIL_IND ALLOW_MAIL_IND, -
ALLOW_MAIL_IND_EFF_DATE ALLOW_MAIL_IND_EFF_DATE, ALLOW_TELEMARKET_IND ALLOW_TELEMARKET_IND, ALLOW_DIRECT_MAIL_IND ALLOW_DIRECT_MAIL_IND, ALLOW_STMT_INSERT_IND ALLOW_STMT_INSERT_IND, -
CUST_SOURCE_CD CUST_SOURCE_CD, NAME_ADDR_SOURCE_CD NAME_ADDR_SOURCE_CD, NAME_ADDR_EFF_DATE NAME_ADDR_EFF_DATE, TO_NCHAR(LAST_NAME) LAST_NAME, TO_NCHAR(FIRST_NAME) FIRST_NAME, -
TO_NCHAR(MIDDLE_INIT) MIDDLE_INIT, TO_NCHAR(NAME_PREFIX) NAME_PREFIX, TO_NCHAR(NAME_SUFFIX) NAME_SUFFIX, TO_NCHAR(ADDRESS1) ADDRESS1, TO_NCHAR(ADDRESS2) ADDRESS2, -
TO_NCHAR(ADDRESS3) ADDRESS3, TO_NCHAR(CITY) CITY, TO_NCHAR(STATE) STATE, COUNTRY COUNTRY, ZIP ZIP, ZIP ZIP, ZIP5 ZIP5, HOME_PHONE HOME_PHONE, AREA_CODE AREA_CODE, -
AREA_CODE_EXCHNG AREA_CODE_EXCHNG, WORK_PHONE WORK_PHONE, DATE_OF_BIRTH DATE_OF_BIRTH, GENDER_CD GENDER_CD, INSTORE_CONTACT_EMPKEY INSTORE_CONTACT_EMPKEY, -
LAST_TRANSACTION_TIME LAST_TRANSACTION_TIME, LAST_TRANS_AMT LAST_TRANS_AMT, LAST_RETAIL_TRANS_TIME LAST_RETAIL_TRANS_TIME, LAST_CATALOG_TRANS_TIME LAST_CATALOG_TRANS_TIME, -
LAST_INTERNET_TRANS_TIME LAST_INTERNET_TRANS_TIME, LIFETIME_AMT LIFETIME_AMT, LIFETIME_RETAIL_AMT LIFETIME_RETAIL_AMT, LIFETIME_CATALOG_AMT LIFETIME_CATALOG_AMT, -
LIFETIME_INTERNET_AMT LIFETIME_INTERNET_AMT, LIFETIME_UNIT_CNT LIFETIME_UNIT_CNT, LIFETIME_RETAIL_UNIT_CNT LIFETIME_RETAIL_UNIT_CNT, LIFETIME_CATALOG_UNIT_CNT LIFETIME_CATALOG_UNIT_CNT, -
LIFETIME_INTERNET_UNIT_CNT LIFETIME_INTERNET_UNIT_CNT, LIFETIME_RETURN_AMT LIFETIME_RETURN_AMT, LIFETIME_RETAIL_RETURN_AMT LIFETIME_RETAIL_RETURN_AMT, -
LIFETIME_CATALOG_RETURN_AMT LIFETIME_CATALOG_RETURN_AMT, LIFETIME_INTERNET_RETURN_AMT LIFETIME_INTERNET_RETURN_AMT, LIFETIME_RETURN_UNIT_CNT LIFETIME_RETURN_UNIT_CNT, -
LIFETIME_RETAIL_RTRN_UNIT_CNT LIFETIME_RETAIL_RTRN_UNIT_CNT, LIFETIME_CATALOG_RTRN_UNIT_CNT LIFETIME_CATALOG_RTRN_UNIT_CNT, LIFETIME_INTERNT_RTRN_UNIT_CNT LIFETIME_INTERNT_RTRN_UNIT_CNT, -
LIFETIME_VISIT_CNT LIFETIME_VISIT_CNT, LIFETIME_RETAIL_VISIT_CNT LIFETIME_RETAIL_VISIT_CNT, LIFETIME_CATALOG_VISIT_CNT LIFETIME_CATALOG_VISIT_CNT, -
LIFETIME_INTERNET_VISIT_CNT LIFETIME_INTERNET_VISIT_CNT, LIFETIME_RTRN_VISIT_CNT LIFETIME_RTRN_VISIT_CNT, LIFETIME_RETAIL_RTRN_VISIT_CNT LIFETIME_RETAIL_RTRN_VISIT_CNT, -
LIFETIME_CATALG_RTRN_VISIT_CNT LIFETIME_CATALG_RTRN_VISIT_CNT, LIFETIME_INTRNT_RTRN_VISIT_CNT LIFETIME_INTRNT_RTRN_VISIT_CNT, LAST_CONTACT_DATE LAST_CONTACT_DATE, -
LAST_CONTACT_TYPE LAST_CONTACT_TYPE, LAST_CATALOG_SENT_DATE LAST_CATALOG_SENT_DATE, LIFETIME_CATALOG_SENT_CNT LIFETIME_CATALOG_SENT_CNT, PRIVATE_CC_ACCT_NUM PRIVATE_CC_ACCT_NUM, -
PRIVATE_CC_FIRST_USE_DATE PRIVATE_CC_FIRST_USE_DATE, PRIVATE_CC_ACCT_BALANCE PRIVATE_CC_ACCT_BALANCE, PRIVATE_CC_LIMIT_AMT PRIVATE_CC_LIMIT_AMT, PRIVATE_CC_LIMIT_SET_DATE PRIVATE_CC_LIMIT_SET_DATE, -
PRIVATE_CC_LIMIT_EXPIRES_DATE PRIVATE_CC_LIMIT_EXPIRES_DATE, PRIVATE_CC_NUM_CARDS_ISSUED PRIVATE_CC_NUM_CARDS_ISSUED, PRIVATE_CC_JC_FIRST_NAME PRIVATE_CC_JC_FIRST_NAME, -
PRIVATE_CC_JC_MIDDLE_INIT PRIVATE_CC_JC_MIDDLE_INIT, PRIVATE_CC_JC_LAST_NAME PRIVATE_CC_JC_LAST_NAME, PRIVATE_CC_APP_STORE_KEY PRIVATE_CC_APP_STORE_KEY, -
ALT_ACCT_NUMBER ALT_ACCT_NUMBER, SOCIAL_SEC SOCIAL_SEC, COMPANY_NAME COMPANY_NAME, BUSINESS_TITLE BUSINESS_TITLE, HOW_DID_YOU_HEAR_CD HOW_DID_YOU_HEAR_CD, -
HOW_DID_YOU_HEAR_EFF_DATE HOW_DID_YOU_HEAR_EFF_DATE, PREFERRED_PROMO_METHOD_CD PREFERRED_PROMO_METHOD_CD, PREF_CUST_STATUS1_CD PREF_CUST_STATUS1_CD, PREF_CUST_STATUS1_EFF_DATE PREF_CUST_STATUS1_EFF_DATE, -
PREF_CUST_STATUS2_CD PREF_CUST_STATUS2_CD, PREF_CUST_STATUS2_EFF_DATE PREF_CUST_STATUS2_EFF_DATE, PREF_CUST_STATUS3_CD PREF_CUST_STATUS3_CD, PREF_CUST_STATUS3_EFF_DATE PREF_CUST_STATUS3_EFF_DATE, -
EMAIL_ADDR EMAIL_ADDR, COUNTRY_CD COUNTRY_CD');--
Thank you,
David

I am not familiar with this. How would you recommend doing this?
David

RSYST-CODE-input data too long

we have implemented ESS on EP 7..when we try to naviagte through my workspace and if select any services such as Performance Mangement , Leraning and development it will take us to a screen where prompt us to log for Production system ,,...
Service :WEBGUI
RSYST-CODE-input data too long
if i give necessary acces it will connects to the R/3 ..
is there any coonection based configuration to be check in order to by pass getting this screen..
regards
Buddhike

Hi Lynton,
As mentioned in the thread you listed, it is possible that this error is being caused by using certain characters, such as ü, á, $, &, -. In order to check if any catalog has strange characters, please check in transaction SPRO -> Supplier Relationship Management -> SRM Server -> Master Data -> Define External Web Services. Check in "Web Service ID" if any catalogs contain strange characters.If so, remove them and retest the issue.
Kind Regards,
Conor Harkin

XML Input String too long to Test Web Service in App Server

We have a Web Service that accepts an XML input string but when we deploy this web service and try to test it through the Application Server it errors out because the input string is too long. Is there any way around this??
Thanks...

Update:
Now I see that there are in fact two error messages. The second one is the one presented above. But the first one says:
Line: 145
Char: 97
Error: Expected ';'
Code: 0
My question now is to what file it is referring?? Is it to ProjectAccountingPort.js that is automatically created? THen why is it not properly created??
Please, please help me with this! The deadline is in a few days...

Nawk message input record too long

I am running a shell script which uses nawk.
I am processing a huge input file.
I get a message that an input record is too long.
What am I supposed to do to indicate to nawk the max record line length ?
My e-mail is [email protected]
Any info will be appreciated

The 6144 limit can be verified with:
% perl -e 'print "A"x6145, "\n"' | nawk '{ print length($0); }'
nawk: input record `AAAAAAAAAAAAAAAAAAAA...' too long
source line number 1
(it works, when you change the perl print statment to
6144 x "A").
Quick solution could be to use gawk instead of nawk
(/opt/sfw/bin/gawk, if you have the Solaris 8 companion
CD installed).

Error SP2-0027 while using explain plan

I'm using explain paln command in order to get the tables
acceeded by a SQL query.
When I use the command with some of them, that's OK.
But when I use it with a query of 4999 characters, it gives me
this error message:
SP2-0027: Input is too long (> 2499 characters) - line ignored
Has anybody an idea to solve this problem or to change this
limit of 2499?

user12043927 wrote:
Open the file (or copy the sql) in a text editor and then resave the file as a different file type.
In Microsoft Word, you click on File, Save As, then select file type 'text only with line breaks' and save the file. Once this is done, you can successfully run the script from SQL*Plus or Server Manager.You never get a second chance for your first impression.
As your first post you resurrect a ten year dead zombie post.
SWEET!
Can you find a post that is older & dormant to boost your post count?

Sqlplus copy error SP2-0027

I am getting a SP2-0027 (input too long - over 2499 characters) when trying to do a table copy.
essentially:
COPY TO user/pass@db CREATE Table1 USING SELECT field1, field2,....fieldn where so many fields make the string too long.
Is there a way i can break this up to put on multiple lines?

Do you need to list all fields ? Can you just say "select *" ?
Other options are :-
create a database link
create table mytable@remotedb as select * from mytable"
or
create the remote table and database link, then
insert into mytable@remotedb select * from mytable
Edited by: Robert Geier on Oct 15, 2009 4:29 PM

PLS-00114: identifier too long error (Oracle 10g)

Hi All,
Hi All,
I have created procedure called "p_procedure_for_cals_annual_sal_oracle_proprierty.lib".
It is must to give the procedure name as mentioned.(>30 Chars)
But while executing I am getting following error.
SQL> exec p_procedure_for_cals_annual_sal_oracle_proprierty.lib
BEGIN p_procedure_for_cals_annual_sal_oracle_proprierty; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00114: identifier 'p_procedure_for_cals_annual_sal_' too long.Please give me suggestion to execute this procedure.
Thank you.
Edited by: user636482 on Mar 22, 2009 9:57 PM

I think you've mistaken EXEC(UTE) with START or @
Execute
Executes a single PL/SQL statement. The EXECUTE command is often useful when you want to execute a PL/SQL statement that references a stored procedure.
Start
STA[RT] {url | file_name[.ext] } [arg...]
Runs the SQL*Plus statements in the specified script. The script can be called from the local file system or from a web server. Only the url form is supported in iSQL*Plus. You can pass values to script variables in the usual way.
Here's a copy/paste of a test:
the file (some_long_name_with_many_characters.sql)
set serverout on
Begin
dbms_output.put_line('A line of text...');
End;
/The SQL*Plus session:
SQL> exec some_long_name_with_many_characters.sql
BEGIN some_long_name_with_many_characters.sql; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00114: identifier 'SOME_LONG_NAME_WITH_MANY_CHARA' too long
ORA-06550: line 1, column 43:
PLS-00103: Encountered the symbol "SQL" when expecting one of the following:
<an identifier> <a double-quoted delimited-identifier> delete
exists prior <a single-quoted SQL string>
The symbol "<an identifier> was inserted before "S
SQL> @some_long_name_with_many_characters.sql
A line of text...
PL/SQL procedure successfully completed.
SQL> sta some_long_name_with_many_characters.sql
A line of text...
PL/SQL procedure successfully completed.
SQL>

Error on the reports with drill-through links on SSRS 2012 SP2 -- Invalid URI: The Uri string is too long

Hi, We are migrating SSRS 2008 R2 reports to SSRS 2012 SP2. (PS. SSRS 2012 SP2 has been applied.) Everything went smooth expect some reports which were using reporting services. These reports have some drilin-through actions and was passing in a huge
xml parameter. I referred to some other posts in which there were also some similar issues like "The Uri string is too long." but they're different. My reports can be opened and the error only occurred when accessing the drill-through actions.
As I know, Microsoft has provided the fix for the known issue "The Uri string is too long." in sp1 but it looks it can't cover this kind of situation since I have installed the SSRS SP 2. Is there any solution? In addition, there's no such
issue on SSRS 2008 R2.
Thanks,
onizga

Hi onizga,
According to your description that you are migrating SSRS 2008 R2 reports to SSRS 2012 SP2, after migration you got some error like “The Uri string is too long” which only occurred when accessing the drill-through actions, right?
Usually, the issue can be caused when you try to pass some parameters that cause the URL length to exceed 65,520 characters for a Microsoft SQL Server 2012 Reporting Services (SSRS 2012), you cannot render the report, and you may receive the following error
message:
The value of parameter 'param' is not valid. (rsInvalidParameter).Invalid URI: The Uri string is too long.
This is an known issue and already have the hotfix SQL Server 2012 Service Pack1 Cumulative Update 9 (CU9) as you know, you can try to reinstall this hotfix to fixed this issue:
http://support.microsoft.com/kb/2916827 .Any issue after applying the update, please post it on the following thread or you can submit an feedback:
http://connect.microsoft.com/SQLServer/feedback/details/788964/ssrs-2012-invalid-uri-the-uri-string-is-too-long
Similar threads for your reference:
SSRS - The value of parameter 'param' is
not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long.
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException:
The value of parameter 'pSetOfScopes' is not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long
If you still have any question, please feel free to ask
Regards
Vicky Liu
If you have any feedback on our support, please click here

Input parameter error: "string too long"

Hi,
SAP4Rails and SAPNWRFC run really well now, and I have not experienced a problem for a long, long time.
However, in an RFC I want to use, there is an import parameter (a plain value), which is of the type SYSUUID. The definition of this type says
<Format - Data Type "RAW" - No. characters "16"> and <Output Characteristics - Output Length "32">. Locally it works with 32 characters of input, but if I try to call the RFC through SAP4Rails, the error "RfcSetByte string too long" occurrs. Any idea, why this could be?
Thanks a lot in advance,
Bernd

This maybe a bug - if you can compile your own sapnwrfc can you try finding the following code:
    if (RSTRING(value)->len > max)
        rb_raise(rb_eRuntimeError, "RfcSetByte string too long: %sn", StringValueCStr(value));
and changing it to:
code]
    if (RSTRING(value)->len > max*2)
        rb_raise(rb_eRuntimeError, "RfcSetByte string too long: %s\n", StringValueCStr(value));
[/code]
and let me know what effect that has.
Cheers.

SharePoint 2010, Visual Studio 2010, Packaging a solution - The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Hi,
I have a solution that used to contain one SharePoint 2010 project. The project is named along the following lines:
<Company>.<Product>.SharePoint - let's call it Project1 for future reference. It contains a number of features which have been named according
to their purpose, some are reasonably long and the paths fairly deep. As far as I am concerned we are using sensible namespaces and these reflect our company policy of "doing things properly".
I first encountered the following error message when packaging the aforementioned SharePoint project into a wsp:
"The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
I went through a great deal of pain in trying to rename the project, shorten feature names and namespaces etc... until I got it working. I then went about gradually
renaming everything until eventually I had what I started with, and it all worked. So I was none the wiser...not ideal, but I needed to get on and had tight delivery timelines.
Recently we wanted to add another SharePoint project so that we could move some of our core functinality out into a separate SharePoint solution - e.g. custom workflow
error logging. So we created another project in Visual Studio called:
<Company>.<Product>.SharePoint.<Subsystem> - let's call it Project2 for future reference
And this is when the error has come back and bitten me! The scenario is now as follows:
1. project1 packages and deploys successfully with long feature names and deep paths.
2. project2 does not package and has no features in it at all. The project2 name is 13 characters longer than project1
I am convinced this is a bug with Visual Studio and/or the Package MSBuild target. Why? Let me explain my findings so far:
1. By doing the following I can get project2 to package
In Visual Studio 2010 show all files of project2, delete the obj, bin, pkg, pkgobj folders.
Clean the solution
Shut down Visual Studio 2010
Open Visual Studio 2010
Rebuild the solution
Package the project2
et voila the package is generated!
This demonstrates that the package error message is in fact inaccurate and that it can create the package, it just needs a little help, since Visual Studio seems to
no longer be hanging onto something.
Clearly this is fine for a small time project, but try doing this in an environment where we use Continuous Integration, Unit Testing and automatic deployment of SharePoint
solutions on a Build Server using automated builds.
2. I have created another project3 which has a ludicrously long name, this packages fine and also has no features contained within it.
3. I have looked at the length of the path under the pkg folder for project1 and it is large in comparison to the one that is generated for project2, that is when it
does successfully package using the method outlined in 1. above. This is strange since project1 packages and project2 does not.
4. If I attempt to add project2 to my command line build using MSBuild then it fails to package and when I then open up Visual Studio and attempt to package project2
from the Visual Studio UI then it fails with the path too long error message, until I go through the steps outlined in 1. above to get it to package.
5. DebugView shows nothing useful during the build and packaging of the project.
6. The error seems to occur in
CreateSharePointProjectService target called at line 365 of
Microsoft.VisualStudio.SharePoint.targetsCurrently I am at a loss to work out why this is happening? My next task is to delete
project2 completely and recreate it and introduce it into my Visual Studio solution.
Microsoft, can you confirm whether this is a known issue and whether others have encountered this issue? Is it resolved in a hotfix?
Anybody else, can you confirm whether you have come up with a solution to this issue? When I mean a solution I mean one that does not mean that I have to rename my namespaces,
project etc... and is actually workable in a meaningful Visual Studio solution.

Hi
Yes, I thought I had fixed this my moving my solution from the usual documents to
c:\v2010\projectsOverflow\DetailedProjectTimeline
This builds ok, but when I come to package I get the lovely error:
Error 2 The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\VS2010\ProjectsOverflow\DetailedProjectTimeline\VisualDetailedProjectTimelineWebPart\Features\Feature1\Feature1.feature VisualDetailedProjectTimeline
Now, the error seems to be related to
Can anyone suggest what might be causing this. Probably some path in an XML file somewhere. Here is my prime suspect!
<metaData>
<type name="VisualDetailedProjectTimelineWebPart.VisualProjectTimelineWebPart.VisualProjectTimeline, $SharePoint.Project.AssemblyFullName$" />
<importErrorMessage>$Resources:core,ImportErrorMessage;</importErrorMessage>
</metaData>
<data>
<properties>
<property name="Title" type="string">VisualProjectTimelineWebPart</property>
<property name="Description" type="string">My Visual WebPart</property>
</properties>
</data>
</webPart>
</webParts>
.... Unless I can solve this I will have to remove the project and recreate but with simple paths. Tho I will be none the wiser if I come across this again.
Daniel

Compile error "input line is too long" when using useLegacyAOT

I'm using FlashBuilder 4.7 and the release of AIR 4 on Windows 7 to package for iOS...As soon as I include 3 or more ANEs I can no longer compile to iOS (and also use the new "useLegacyAOT no" command). When I try I get an error "The input line is too long. Compilation failed while executing : compile-abc"
I found a couple other similar issues. One post suggested instead of pointing to individual ANEs (in Package Contents) to point to a folder instead--but this doesn't fix the
Another post for a slightly different problem said it was fixed in the release of AIR 4.
Any ideas? I wonder if I move my AIR SDK to a simple path (like "c:\air\adt.jar" instead of "C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\adt.jar") if it'd help.
Thanks in advance!

Awesome! I got used to the new useLegacyAOT thing very fast. In the meantime, I have to decide whether to remove all my ANEs and test or sit through an interminable build sequence.
What's the current plan for a new release? Is there any way I could get a beta copy just to use during development?
Thanks!

TFS Build Error - Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters

I am trying to set-up CI of Orchard CMS and deploy it on Azure using TF service. I am stuck at following error for path being
longer than 260 characters. However, when counted the total characters in path are 235. Please see the below error :
Other Errors and Warnings
1 error(s), 1 warning(s)
Exception Message: TF400889: The following path contains more than the allowed 259 characters: drop/_PublishedWebsites/Orchard.Web_Package/Archive/Content/C_C/a/src/projects/Orchard/dev/DevAltaf/Orchard/src/Orchard.Web/obj/Debug/Package/PackageTmp/Modules/BrentApart.BannerManager/Scripts/controllers/bannerAssignmentController.js. Specify a shorter path. (type VssServiceException)
Exception Stack Trace: at Microsoft.TeamFoundation.Build.Workflow.Activities.FileContainerDropProvider.EndCopyDirectory(IAsyncResult result)
at Microsoft.TeamFoundation.Build.Workflow.Activities.CopyDirectory.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
Inner Exception Details:
Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. (type PathTooLongException)
Did anyone came across such issue while deploying Orchard on Azure with TF service? If yes, how did you sort this freaking error?
Thanks,
Altaf B.

Hi AltafB,
For your situation, you can short the path for the source code. Or use a short path for build agent folder in your build definition. You can refer to the links below to solve your problem:
http://blogs.msdn.com/b/aaronhallberg/archive/2007/06/20/team-build-and-260-character-paths.aspx
https://social.msdn.microsoft.com/Forums/vstudio/en-US/1638a5f0-9321-4ff9-9ee7-6d347badb972/please-some-solution-to-the-specified-path-file-name-or-both-are-too-long?forum=tfsbuild
Besides, since you deploy Orchard to Azure, you can also publish it directly using publish profile in Visual Stduio or WebMatrix directly.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SP2-0027: Input is too long ( 2499 characters) - line ignored

Similar Messages

Maybe you are looking for