SP06: The specified regulu00F6ar expression "([^%]*)%(..)(.*)" is too complex

Hi,
after upgrading from SRM7.0 SP04 to SP06 we get the following error, when we transfer items from mdm back to srm:
Error in the ABAP Application Program                                                                               
The current ABAP program "/SAPSRM/CL_CH_WD_INBOUND_HDLR=CP" had to be          
terminated because it has                                                     
come across a statement that unfortunately cannot be executed.                                                                               
The specified regulöar expression "([^%]*)%(..)(.*)" is too complex. Therefore,
it is                                                                         
not possible to determine the matches in the search text accroding to          
the leftmost-longest rule.                                                     
Any ideas?
Thanks and best regards,
Roman

There is one pilot note  1457627which solved this error previously.
The coding is as below, only customers which added as pilot customer will see it.
$ Valid for       :                                                  $
$ Software Component   SRM_SERVER SAP SRM SERVER                     $
$  Release 700          All Support Package Levels                   $
$$                                                                $$
*& Object          METH /SAPSRM/CL_CH_WD_INBOUND_HDLR
*&                      DECODE_PARAMETER
*& Object Header   CLAS /SAPSRM/CL_CH_WD_INBOUND_HDLR
  conv_in->convert( EXPORTING input = iv_request_data  IMPORTING data =
request_data_c ).
  WHILE request_data_c IS NOT INITIAL.
*>>>> START OF DELETION <<<<<
    " ABC%F4...
           ABC           F4
    FIND FIRST OCCURRENCE OF REGEX '([^%])%(..)(.)' IN request_data_c
SUBMATCHES not_encoded_c encoded_xc rest.
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
    " ABC%F4...
                  ABC           F4
    FIND FIRST OCCURRENCE OF REGEX '(?:^ %)([^%])%(..)(.)' IN request_
data_c SUBMATCHES not_encoded_c encoded_xc rest.
*>>>> END OF INSERTION <<<<<<

Similar Messages

  • SSAS DRILLTHROUGH - Specified query is too complex error.

    Hi Guys,
    I'm working on an SSAS 2012 OLAP cube with around 100 dimensions and a single measures group. When I try to run a simple DRILLTHROUGH query such as:
    DRILLTHROUGH
    MAXROWS 1000 SELECT
    FROM [Cube] WHERE ([Measures].[Fact_Count])
    I get an error as below.
    The specified query is too complex to be evaluated as a single statement.
    Does anyone have any experience of this error and how to work around it? If I remove the majority of the dimensions from the cube I can run this query successfully. Looking at the limits set for analysis services I should be well within these.
    Thanks in advance 
    Sean

    Hi Scaneyw,
    Based on my research, this is a SQL Server Analysis Services (SSAS) design limitation. In SSAS, Drillthrough” generates internal CrossJoin query that contains all attribute hierarchies in measure group. So the error appear when MDX parser receives statement
    with> 1000 nodes.
    Here are some tips for you to avoid this error.
    Reduce number of dimension attribute hierarchies in measure group below 1000.
    Delete unneeded attributes and disable Hierarchy for attributes that are only used as properties.
    Consider creating smaller Measures Groups with less dimensions + attribute hierarchies.
    If you have any concerns about this feature, you can submit a feedback at
    http://connect.microsoft.com/SQLServer/Feedback and hope the complete “drillthrough” feature is will be improved in future SQL Server Versions.
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • Expression too complex in query expression

    Page code creates a string of all ManufacturerPartNumbers
    that share a common ProductFamilyID based on a
    ManufacturerPartNumber form selection. This string is then included
    in the recordset query.
    The following error message only occurs when the
    ManufacturerPartNumber string has numerous listings. When the
    string contains only 3 listings of ManufacturerPartNumbers, this
    error message does not appear.
    [Microsoft][ODBC Microsoft Access Driver] Expression too
    complex in query expression 'LATITUDE &amp;lt;=
    40.8210861895984 AND latitude &amp;gt;= 40.3865898104016 AND
    longitude &amp;gt;= -74.2737786508004 AND longitude
    &amp;lt;= -73.7014913491996 AND
    (((((((((((((((((((((((((((((ManufacturerPartNumber = '3408H')) OR
    ((ManufacturerPartNumber = '4608H'))) OR ((Manufacture'.
    /customer_locator/testprocessform2.asp, line 233
    Is there a size limit to a recordset query that is causing
    this error or is there a possible syntax issue with my query
    code?

    That doesn't sound like an error that would normally occur on a lot of pages... Do you have AdBlock (Plus), or any Greasemonkey userscripts, or any similar add-ons that customize sites? I wonder whether one of those might have some faulty logic.

  • 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

  • Could not complete the new 3D extrusion from selected layer command because the path is too complex.

    I was trying to do a photo of mine like in this video but its not working help needed. thanks.
    http://www.youtube.com/watch?v=egyLY78H7nE
    When I tried the 3D I got an error message that said (could not complete the new 3D extrusion from selected layer command because the path is too complex.) what does this mean and how can i fix it?

    There was a bug at one time where really simple paths (like a triangle, for example) could cause that error.
    Is your path really simple (I don't plan to go watch the video)?  If so, have you installed the latest update for Photoshop?  That bug may have been fixed already.
    If it's not that, it's possible that if your path is really complex and simply exceeding Photoshop's capability.
    -Noel

  • 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.

  • Powershell Get-childItem: The specified path, file name, or both are too long.

    Hey Scriping Guys!
    I've been using a PowerShell script for a couple of years now to generate a monthly report showing the size of user folders on a number of departmental file servers.  It's working just fine on all file servers except one where the users have gotten carried away with creating sub-folders and using realy long descriptive file names.  The problem piece of script is this:
    $colItems = (Get-ChildItem \\192.168.10.5\marketing -recurse | Measure-Object -property length -sum)
    "marketing-serv\marketing: "+"{0:N2}" -f ($colItems.sum / 1GB) + " GB"
    The reply I get is:
    Get-ChildItem : 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 mu
    st be less than 248 characters.
    At G:\data\Server_space_Report\serverspace2.ps1:37 char:27
    + $colItems = (Get-ChildItem  <<<< \\192.168.10.5\marketing -recurse | Measure-Obje
    ct -property length -sum)
    Yes, the message is correct, however, when I connect to the server, right click the folder and chose properties it returns a size of 128 GB.  My questions are
    1. Why does clicking on folder properties not produce an error (what is it doing differently from my script)?
    2. How can I fix my script?
    Thanks,

    I am trying to clear up the older open posts on this forum. If this is still an unresolved issue for you please let me know. If you do not post back within one week I will assume it is resolved and will close this thread.
    Thank you
    Ed Wilson
    Microsoft Scripting Guy

  • Get-ChildItem : 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, Im trying to get the whole path in my server, so i tried that with this following code
    Get-ChildItem $sourceFolder  -Recurse | ?{$_.PsIsContainer} |Get-Acl
    But then, it showed me somtehing like this :
    Get-ChildItem : 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 tried to find the solver everywhere and mostly they propose to change the path name, which is impossible, since I am working with my company server, and those folder have already there before i start to work here, then the other ask me to use robocopy,
    but all of the trick just dont work
    is there any way to solve this problem? thanks

    There is no simple solution to this. And it is not a limitation of powershell itself, but of the underlying NTFS file system.
    If the problem is that a folder with a name longer than 248 exists anywhere within your directory structure, you are hooped.
    If the problem is that some fully qualified path names exceed 260 characters, then, in those cases, the solution already given is to create a psdrive partway up the path from the drive letter or server/share root of the path. Unfortunately, the output produced
    will be relative to that psdrive and not to what is specified as the $sourcefolder.
    unless you already know where those problematic paths are, you might consider trying to trap those errors and have your script figure out where it needs to create psdrives. You might then be able to calculate the equivalent path for each file or folder and
    output that. the programming effort would be simpler to just created a psdrive for each folder encountered, however I expect that would be very inefficient.
    Al Dunbar -- remember to 'mark or propose as answer' or 'vote as helpful' as appropriate.

  • "Can not perform this operation because the layout is too complex"

    "Can not perform this operation because the layout is too complex"
    to create a 3D extrusion
    Hello
    Is it possible to work around and solve this problem?
    Without going through the box: cutting 4 part
    please
    xavier.

    Merci Violon popur tes conseilles, cool !
    After clipping of an object on a photo
    I want to make a 3D extrusion.
    With a picture of this size that does not work :
    1979/2765 300PP 31,3Mo
    I have this error message appears: “ Can not perform this operation because the layout is too complex ”
    For successful operation
    I must necessarily reduce the size of the photo to
    597/834 300PP 2,85Mo !!!
    How not to lose the pixel ?
    I need it additional plugins ?
    Version Adobe Photoshop : 14.2 (14.2 20131211.r.515 2013/12/11:23:00:00) x64
    Système d'exploitation : Mac OS 10.9.1
    Architecture système : UC Intel Famille :6, modèle :44, niveau :2 avec MMX, SSE Entier, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Nombre de processeurs physiques : 12
    Nombre de processeurs logiques : 24
    Vitesse du processeur : 2930 MHz
    Mémoire intégrée : 32768 Mo
    Mémoire libre : 27285 Mo
    Mémoire disponible pour Photoshop : 31299 Mo
    Mémoire utilisée par Photoshop : 90 %
    Taille de la mosaïque d'images : 1024K
    Niveaux de mémoire cache de l'image : 4
    2 X 2,93 GHz 6-Core Intel Xeon
    NVIDIA Quadro 4000 2048 Mo
    4 X 8 (32 Go) DDR3 @ 1066Mhz
    2 X OWC Mercury Extreme Pro 6G SSD Media (System acquisition / Projects)
      2 x 2 To de DD (5400tr/min)

  • CS6 3D error (bug?) "Could not complete your request because the path is too complex."

    I'm running into a bit of a problem with having a shape extruded in 3D.
    If I draw a rectangle shape set to path over an image and then choose "source - work path" and "3D extrusion" I will get a 3D rectangle with the image on the front side.
    If I draw a 3 sided polygon (triangle) set to path over an image and then choose "source - work path" and "3D extrusion" I will get a error telling me that the path is too complex.
    I'm doing the exact same thing.
    Now, if I have 4 sides plus, on the polygon it will extrude just fine.
    Something seems to be happening with 3 sided polygons.
    This holds true with the pen tool as well. Three points will give you the error, 4 and above seem not to.
    Any ideas and to why this is happening?
    Thanks!
    Lux
    CS6 - latest build
    Mac 12 core
    24gigs Ram
    Cloud subscriber

    Work around. (CS6)
    (1) Draw your trangle shape.
    (2) Convert one of the corners to a smooth corner (just barely). If you doesn't work, bend flex it a little more, and try again.
    (3) 3D/New 3D extrusion from selected layer.
    (4) Switch camera to top view.
    (5) With 3D layer selected, in the coordinates menu of Properties panel, set X angle to 90.
    (6) Snap object to ground plane.
    (7) Set depth to 0.
    (8) In the Cap menu of the Properties panel, adjust cap width to 100%.

  • "Could not complete your request because the path is too complex"

    I'm trying to render 24 characters of text with line breaks in 3D, because, as we know, 3D can be very spiffy... but I get:
    "Could not complete your request because the path is too complex"
    Interesting, I'm on a rocketship workstation with a fairly stealthy config. All is updated to the latest ver., 13.1.2.. Not the greatest card in the world (Quadro 2000), but it seems more than ample for this task..
    It works fine with 9 characters on one line... Ok, possibly (or rather likely) I have too much text (24 characters? Line breaks? Trebuchet?), but frankly, I'd be surpised... What are the limitations here? Tips?
    Thank you!

    In this case, I have photoshop doing all the number crunching through GPU:
    Also, my performace settings (this is 32-bit PS, so it only sees 4GB):
    We'll see what any Adobe folks say, thank you very much for your time and insights!

  • BT Mapper error : The style sheet is too complex

    Hi Guys,
    I am trying to test the map in visual studio and I immediately prompted with the error “XSLT exception: The style sheet is too complex”. I have searched for this on the web and came to know that this might be caused by number of lines in XSLT and my BT mapper
    is very big. And I can confirm that this is not due to any mapping errors or syntax errors because I checked the same mapping using few lines of xslt and it worked.
    Does anyone has seen this error in BizTalk mapper? I am testing the map using “Test map” in visual studio.
    I am using BizTalk server 2013 R2 Dev with visual studio 2013.
    Thanks
    JB

    Hi JB,
    There is a known issue with framework 4.5 as mentioned in the given article:
    http://support.microsoft.com/kb/2828841/en-us
    Trying applying this hotfix and make the config changes as mentioned in the below article.
    BizTalk
    2013 Orchestration fails with Error "The Stylesheet is too Complex"
    Rachit
    Please mark as answer or vote as helpful if my reply does

  • Could not complete the new 3D extrusion because the path is too complex

    I'm using Photoshop CS6 in Windows 7 64bit. I've seen other posts about a bug if you are trying to complete a 3D extrusion when a triangle is present, but my issue seems even more basic.
    I'm drawing a simple wave shape with the pen tool set to shape, no fill, 1px stroke. I'm simply drawing three points to create a simple sine wave - the idea being to create a wavy piece of 35mm film. The image size is quite big - 6000 x 4000 px. The first time I did it, the rendering worked fine but I didn't like the curve I had drawn, so I stepped back and tried again. Now, whatever I do, I get the "Could not complete because the path is too complex" message.
    Is this a known bug and are there any workarounds to create a single pixel wide wavy shape in 3D that looks like a piece of film.
    Steve

    I have run across this also, but my path was more complex.  As far as creating a single pixel wavy shap, I would use the depth map 3D feature of  converting a depth map to a plane.  Create a gradient in 32bit mode, so the transistion are smooth, and then go to the 3D menu and select new mesh from depth map>plane.  You can later go in and edit the depth map to tweak it.

  • The Subtitle or menu subpicture is too complex !

    I am running Encore version 2.0 and almost completed a project. The final stage is to add subtitles. When I try to create an iso file or burn to DVD, the encoding process goes OK until it comes to encoding subtitles. It then comes up with "The subtitles or menui sub-picture is too complex to be encoded" and gives up.
    I have tried replacing the subtitle text for the clip that seems to have the problem. When the text is removed, all is OK. When I re-type the text for the clip, the problem returns.
    Anyone any idea what the problem could be?
    I am running Windows XP with a 3GHz processor and 2GB RAM
    Thanks in advance
    Chris Walsh

    The quickest solution would be to split up the offending subtitle. E.g. if it was originally
    i "The quick brown fox jumped over the lazy dog"
    for 10 seconds, change it to 5 seconds of
    i "The quick brown fox jumped..."
    followed by
    i "...over the lazy dog"
    for the remaining 5 seconds.

  • What happened to the 24/7 live chat for mobile me? I need help right now. Too complex for this. Crime involved., What happened to the 24/7 live chat for mobile me? I need help right now. Too complex for this. Crime involved.

    What happened to the 24/7 live chat for mobile me? I need help right now. Too complex for this. Crime involved., What happened to the 24/7 live chat for mobile me? I need help right now. Too complex for this. Crime involved.

    Hi Tmswrite,
    Here is what you want to do to protect yourself and your device:
    Find My iPhone Basics  - Apple Support
    iCloud: Find My iPhone overview
    Here's some information on how the Activation Lock protects you:
    Find My iPhone Activation Lock in iOS 7
    Sorry for your troubles. Hope it turns out OK for you!
    GB

Maybe you are looking for

  • Creation of a (cost effective) Operational Data Store

    I already have a db schema with staging and ods tables and would like to duplicate this environment (almost). The duplication would involve me creating a "separate" schema with all persistent data tables. Central to the "duplication" idea is economy

  • File Content Conversion for complex structure

    Hi I have a requirement to repeat a structure consisting of three lines i.e the segment  containing these 3 lines will have occurrence 0....unbounded and will be repeated in the File multiple times , What is the level that can be handled in File Cont

  • Convince me to buy a zen mi

    Hi, I'm using a zen touch which is great and now my son wants a zen micro, having read the posts on here, I get the impression that it is a pile of junk! However I do realize that most people posting here are looking for answers to problems and there

  • ICR process 002 - rules for S-L

    Dear all When I try to enter a rule, saying: BSEG-XOPVW = '' for my S-L for the IC reconciliation process 002, the system gives an error (GU103), saying: "Die Tabelle bzw. das Feld des eingetragenen Objektes, z.B. der Regel, des Feldes oder des Sets,

  • Help me set fingerprint function on phone

    how can I set speed dial?