CV03N error

Hi Gurus,
Please help.
Users are encountering error upon viewing of JPG in tcode CV03N. error "File c:\temp\img\_XXXX.jpg cannot be created"
Please advice on what caused the error.
Thank you.

hi
check the customization setting for the document type used.
Cross-Application Components -> Document Management --> General Data -->
--> Define Data Carrier

Similar Messages

  • XML file opening error using CV03N in ECC6

    Experts, I am getting below error while opening an XML file in ECC6 using transaction CV03N. File was generated in 4.6C and system is upgraded to ECC6.
    " The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
    A name contained an invalid character. Error processing resource 'file:///C:/temp/ABC.xml'. Line 1, Position 35 "

    Experts, I am getting below error while opening an XML file in ECC6 using transaction CV03N. File was generated in 4.6C and system is upgraded to ECC6.
    " The XML page cannot be displayed
    Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
    A name contained an invalid character. Error processing resource 'file:///C:/temp/ABC.xml'. Line 1, Position 35 "

  • While trying to open document getting error msg

    Hi
    While i am trying to open document thru cv03n it sending error messsage please help.
    File c:\temp\_10097601.doc cannot be created
    Message no. 26172

    Hi,
    IF the issue is user specific: Please check the access rights in C:\ folder.
    If the issue is common: Check the RFC connection and ensure the test results are in green.
    If the PROD system was working properly earlier and you face the issue suddenly: Check the port setting (Check with the server team-They may lock the port some times during upgrade/Maintenance).
    If your issue not solved send the connections screen shots.
    Rgds,
    Nayeem.

  • Error while creating document in cv01n

    In cv01n while attaching excel,word etc.file,at the time of saving error massege given is document can not change.Please provide me solution

    I have checked the img setting ,img setting is ok,still it gives program error  as below,can you suggest me whether reccomndations can implemented or not.
    Note 964021 -Update Task Fails When New Version Created
    Note Language: English Version: 2 Validity: Valid from 07.11.2006
    Summary
    Symptom
    Update task fails when a new version of an old document info record is
    created using CV02n transaction.The system throws an update terminate
    error.
    More Terms
    UPDATE TERMINATE, MESSAGE 26 178, CV200_DB_DOC_UPDATE, CV02N
    Cause and Prerequisites
    Program Error
    Solution
    Implement the note
    Header Data
    Release Status: Released for Customer
    Released on: 07.11.2006 12:13:26
    Priority: Correction with medium priority
    Category: Program error
    Main Component CA-DMS Document management
    Valid Releases
    Software Component Release From
    Release
    To Release and Following
    SAP_APPL 500 500 500
    SAP_APPL 600 600 600
    Support Packages
    Support Packages Release Package Name
    SAP_APPL 500 SAPKH50016
    SAP_APPL 600 SAPKH60008
    Attributes
    Attribute Value
    SAP objects CV200_DB_DOC_UPDATE
    Transaction codes CV02N,CV03N
    Transaktionscodes - manuell CV02N,CV03N
    SAP-Objekte - manuell CV200_DB_DOC_UPDATE
    DownPort/UpPort-WF UpPort check done, symptom
    repaired
    Correction Instructions
    19.06.2008 Page 1 of 2
    Note 964021 -Update Task Fails When New Version Created
    Correction
    Instructio
    ns
    Valid
    from
    Valid
    to
    Software
    Component
    Typ
    e
    Reference
    Correction
    Last
    Changed
    518092 500 500 SAP_APPL C P6DK093226 07.11.2006 17:30:29
    807328 600 600 SAP_APPL C P7DK042952 13.07.2006 14:50:41
    *) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined
    19.06.2008 Page 2 of 2

  • Error while attaching document in cv01n

    Hi,
    We are attaching document in transaction cv01n,at the time of saving it gives error  massege change is not allowed,but still system is saving saving that documet.can anybody suggest solution to avoid error massege.
    Thanks,
    Vikas warke

    I have checked the img setting ,img setting is ok,still it gives program error  as below,can you suggest me whether reccomndations can implemented or not.
    Note 964021 -Update Task Fails When New Version Created
    Note Language: English Version: 2 Validity: Valid from 07.11.2006
    Summary
    Symptom
    Update task fails when a new version of an old document info record is
    created using CV02n transaction.The system throws an update terminate
    error.
    More Terms
    UPDATE TERMINATE, MESSAGE 26 178, CV200_DB_DOC_UPDATE, CV02N
    Cause and Prerequisites
    Program Error
    Solution
    Implement the note
    Header Data
    Release Status: Released for Customer
    Released on: 07.11.2006 12:13:26
    Priority: Correction with medium priority
    Category: Program error
    Main Component CA-DMS Document management
    Valid Releases
    Software Component Release From
    Release
    To Release and Following
    SAP_APPL 500 500 500
    SAP_APPL 600 600 600
    Support Packages
    Support Packages Release Package Name
    SAP_APPL 500 SAPKH50016
    SAP_APPL 600 SAPKH60008
    Attributes
    Attribute Value
    SAP objects CV200_DB_DOC_UPDATE
    Transaction codes CV02N,CV03N
    Transaktionscodes - manuell CV02N,CV03N
    SAP-Objekte - manuell CV200_DB_DOC_UPDATE
    DownPort/UpPort-WF UpPort check done, symptom
    repaired
    Correction Instructions
    19.06.2008 Page 1 of 2
    Note 964021 -Update Task Fails When New Version Created
    Correction
    Instructio
    ns
    Valid
    from
    Valid
    to
    Software
    Component
    Typ
    e
    Reference
    Correction
    Last
    Changed
    518092 500 500 SAP_APPL C P6DK093226 07.11.2006 17:30:29
    807328 600 600 SAP_APPL C P7DK042952 13.07.2006 14:50:41
    *) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined
    19.06.2008 Page 2 of 2

  • Preview of DMS document error

    Dear all,
    I am a QM guy and using DMS.
    Now, I have a issue for DMS.
    Our vendor upload excel file to vendor inspection LOT using Supply portal.
    Then we can see the document in CV03N.
    When we click the file in CV03N, we can open the excel file.
    Vendor uploaded the 4 document under the same file name as below.
    Lot          DMS NO.               Quantity     filename
    10004238493          30001926280            30          abc.xls
    10005126544          30002442887            10          abc.xls
    10005249439          30002527693            13          abc.xls
    10005525013          30002732147              7          abc.xls
    When I try to see the first document (its quantity is 30 )in CV03N, everything is O.K.
    But When I try to see the other document (its qunatity is 7 ), I can see wrong document .
    For example, I want to see 30002527693 but 30001926280 is shown.
    I think same  filename cause the error.
    Somebody help me ?

    Hi,
    As per your reply i understood that you are not able to differentiate the old and new file.
    Can you please check whether the content version option is checked while creating the document type.
    Also check the version of the DIR created.if there is any change in the  version numbers,start searching with that particular entries in CV03N.
    Hope this will solve.If not do let me know.
    Regards
    Praveen

  • Error when open DMS document

    Dear DMS experts,
    After migration DMS server from one server to another an error has occurred in transaction CV03N when try open original document I got next error massage: File C:\temp\file_name cannot be created (Message no. 26172).
    This happens when I try to open the documents that have already been previously saved, the documents are saved now - open normally.
    In tr. SLG1 I see the following errors:
    1. Error
    Long Text:
    An error occurred when calling module SCMS_DOC_READ_FILES
    Message no. 1R579
    Diagnosis
    Exception number 14 occurred when function module SCMS_DOC_READ_FILES was called with document 0050569339A51ED4828753F4B06C13F3.
    Details:
    In tr. SLG1
    MANDT      200
    STOR_CAT    ZDMS_C1_ST
    PATH       C:\temp\
    FRONTEND   X
    COMP_NAMES %D0%9D%D0%B0%D0%BA%D0%B0%D0%B7 1029 26122012.tif
    COMP_NAMES File_name
    ERRMSG     Content repository DMS_C1 does not exist
    V1 SCMS_DOC_READ_FILES
    V2 14
    V3         DMS_PCD1
    V4         0050569339A51ED4828753F4B06C13F3
    %LOGNUMBER 00000000000000111877
    2. Error
    Connect Error: Connect to Host IP_HOST_DMS_SERVER Port 1090 error: NIECONN_REFUSED
    Message no. 04100
    I run Programs, and get next result:
    1. Program RSIRCCON. My location is spelled correctly but when I run program, chose my repository and run Single_Test I receive next result:
    Error when setting up connection.
    2. Program RSHTTP05
    SAPHTTP check
    Check RFC destination SAPHTTP...
    ... OK.
    Ping RFC destination SAPHTTP...
    ... OK.
    Check RFC destination SAPHTTPA...
    ... OK.
    Ping RFC destination SAPHTTPA...
    ... OK.
    3. Program RSHTTP20
    Connect Error: NiHostToAddr  error: NIEHOST_UNKNOWN
    Message no. 04100
    In SMICM->trace file -> display all.
    I see many massage like this:
    [Thr 5196] Wed Apr 08 09:11:00 2015
    [Thr 5196] *** WARNING => Connection request from (13/14/0) to host: IP_HOST, service: 1090 failed (NIECONN_REFUSED)
    [Thr 5196]  {000105f9} [icxxconn.c 2271]
    [Thr 4904] *** WARNING => Connection request from (13/14/0) to host: pwdf2625, service: 1090 failed (NIEHOST_UNKNOWN)
    [Thr 4904]  {000105fc} [icxxconn.c 2271]
    I do not know this problem relates to the existing or not yet, but I don’t know what is IP_HOST, none of my server does not have this address.
    My Storage Categories: ZDMS_C1_ST
    In SM59 SAPFTPA is working, but SAPHTTP don’t work. After change program SAPHTTP  on a SAPGUI front-end, SAPHTTP is working.
    I try ping my DMS – ok
    In tr. CSADMIN I checked connection - all good.
    Status: Running
    Try test «nipping» on both servers all fine.
    Tried to change the version of SAPGUI - did not help.
    My system parameters DMS server:
    OS: Windows Server 2012
    DB: MAXDB Database Studio
    I can not understand what the problem is because already migrate  the server and it was all good
    Thank you in advance.
    Regards,
    Vitaliy

    Hi S S B ,
    I'm sorry, I have laid out a mistake with the old Content  repository DMS_C1, my new new  Content  repository ZDMS.
    In SLG1 I have next error:
    1. Error: Problem class Other:
    Connect Error: Connect to Host My_DMS_HOST Port 1090 error: NIECONN_REFUSED
    Message no. 04100
    2. Error: Problem class Additional Information
    Long Text exists:
    An error occurred when calling module SCMS_DOC_READ_FILES
    Message no. 1R579
    Diagnosis
    Exception number 14 occurred when function module SCMS_DOC_READ_FILES was called with document 0050569339A51ED482808B4B77CD53F3.
    Detail exists:
    MANDT      200
    STOR_CAT   ZDMS_C1_ST
    PATH       C:\temp\
    FRONTEND   X
    COMP_NAMES %D0%9D%D0%B0%D0%BA%D0%B0%D0%B7 1029 26122012.tif
    COMP_NAMES Наказ 1029  26122012.tif
    ERRMSG     HTTP error: 404 (Not Found)  ""
    V1         SCMS_DOC_READ_FILES
    V2 14
    V3         DMS_PCD1
    V4         0050569339A51ED482808B4B77CD53F3
    %LOGNUMBER 00000000000000111957
    Regards,
    Vitaliy

  • WEB DMS Error uploading file  / create DIR

    Hi SapGurus,
    I have a problem creating new documents using WEB DMS, i remember trying to do it some time ago, and i could manually create the documents through WEB-DMS Create option choosing the configured document type,
    but right now iam not able to upload any original file and create a NEW DIR, as it gives me an error message "an Error occurred while loading file" please suggest me what may be wrong with this now.
    Also can we maintain standard SAP Object links while creating the DIR through WEBDMS, as iam not able to find the SAP Object link Tab / field while creating the DIR In WEB DMS,
    (FYI, in the find documents we could find the document based on the SAP Object link Reference,) so i think there is an option to maintain SAP Object link details for the DIR getting created.
    Thanks and regards
    Priya S

    Hi Priya,
    please note that in WebDocuments only the existing object links are displayed. Therefore not all maintained objects are visible but only those where links exists.                                                                               
    There are certain selected data sections in WebDocuments that are shown in display mode or in change mode. The following sections can only be displayed and not changed
    - Data for Document key
    - Data for Object Links
    The following sections can be changed in WebDocuments
    - Document Data
    - Additional Data
    - Originals
    - Description
    Hence when a Document Info Record is created or changed, the object links data are not shown. It is shown only in search and display mode. This is the way system is designed. You can look at the application help for more information on the web documents. Also kindly note that WebDocuments is not the complete replica of SAP GUI CV01n, CV02n or CV03n. It has some limitations when compared to SAP GUI transactions. So as no new links could be created in WebDocuments not all available objects are displayed. 
    I hope this information could be useful regarding the object link behavior in WebDMS.
    Best regards,
    Christoph

  • PLM 7.0  PLMWGUI viewer error

    Hi,
    I have document that is checked into the standard rep DMS_C1S_ST. Using the SAP GUI I can display it with no problems using cv03n. Upon trying to display the same document using the SAP PLMWUI  (PLM 7.0) I get the following error
    "Workstation application EAIWEB.WEBVIEWER2D.1 %SAP-CONTROL% is invalid. Starting external application.
      Error while checking out: "
    I have the new viewer installed on my local machine and  also have the white list configured.
    appreciate any help
    Rahul

    Hi,
    Thanks to all of you, I was able to configure the white list correctly. The file now does download from the server. The viewer loads  but it displays this error when trying to display the file
    "An attempt was made to load a program with an incorrect format". The rest of the screen area is white. During the first run there was a popup which came up to select rendering options. I selected DIrect x 9. Since then even in spite of uninstalling and reinstalling the viewer the popup does not come  up. I don't know if the error is related to this or something entirely different.
    Please help.
    Rahul
    I am not getting another error
    " Scene creation failed.File may be corrupt"
    I have checked the file and its fine. It is a pdf.
    Edited by: Rahul Patel on May 2, 2010 10:37 PM

  • ITS service interpreter failed error code 0x2101

    Hi!
    I am trying to access a transaction without a user having to logon manually. When opening the following link in the browser I am able to access the transaction without manual login:
    http://itshostname:port/scripts/wgate/cv03n/!?client=010&login=username&password=test&language=DE&draw-doknr=10000009472&draw-dokar=999&draw-dokvr=02&~okcode=/0
    However, the user and passwort are shown in cleartext and I do not want that for security reasons. AFAIK the way to achieve this is setting the parameters in a service file on the agate. Put the file cv03n.srvc in the service directory:
    ~client         010
    ~login          username
    ~password       test
    ~language       DE
    ~transaction       CV03N
    After restarting the agate service and opening the follwing url I expected to see the same transaction as before when I put the parameters inside the url:
    http://itshostname:port/scripts/wgate/cv03n/!?draw-doknr=10000009472&draw-dokar=999&draw-dokvr=02&~okcode=/0
    Instead I got the error message:
    Interpreter Failed
    The Internet Transaction Server failed to generate the response for current request.
    Please contact the system administrator.
    Internal error code: 0x2101
    I also tried to crypt the password. Additionally I tried to set only one parameter in the srvc file (client). Always the same error. Does anyone have an why I get this error as soon as a parameter is put into the service file?
    SAP ITS 6.20 Patchlevel 18
    SAP R/3 4.7
    Browser IE 6.0 SP1
    Greets
    Christian

    Hi Christian,
    as far as I can see you did anything right. Do you find further hints in your trace files when this error occurs?
    Regards Ralph
    EDIT
    I just saw you created this service new? If yes you need to copy the other values from your webgui.srvc to your new service file, too (esecially ~webgui 1)
    /EDIT
    Message was edited by: Ralph Resech

  • Error in CV01n

    hi ppl,
             Actually iam new to DMS.I have some queries like-
    1) Is it necessary to have DMS server..with out DMS server cant we store the documents.
    2) I have created a simple docu in cv01n ..but iam facing errors like-Network address DEFAULT of your computer is not maintained.
    3)what is data carrier..i have tried to give the input as zcarrier:(..its displaying 'does not exist in TDWD table.so do i need to configure the TDWD table or its BASIS consultants work.
    4) please give me the clear picture of CV01n,CV02n,CV03n steps and for keeping Material creation for req.

    Hi Priyank
    You can save your documents in sap server itself if you dont need to store many documents.
    I think you have to maintain the path In Define data carrier typeserver front end: c:/temp like that for that error. You have to define the data carriers like server, frontend pc, vault, archive link etc in spro.
    cv01n--used for creating the document
    cv02n- change the document
    cv03n- Display the document
    Regards
    Prasad

  • Run time error CONVT_OVERFLOW

    dear Sir
    we have window 7 for new oc as soon runned teh program cv01n i got run time error msg  CX_SY_CONVERSION_OVERFLOW,plese guide
    Runtime Errors         CONVT_OVERFLOW                                                              
    Except.                CX_SY_CONVERSION_OVERFLOW                                                   
    Date and Time          03.05.2010 14:26:31                                                                               
    Short text                                                                               
    Overflow when converting from "-1"                                                           
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLCV120" had to be terminated because it has                     
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                       
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                     
        The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not               
         caught in                                                                               
    procedure "SYS_GET_WINDOW_SYSTEM" "(FORM)", nor was it propagated by a RAISING               
         clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                        
        exception would occur, the current program is terminated.                                    
        The reason for the exception is:                                                             
        When attempting to convert the value "-1", an overflow occurred.                             
    How to correct the error                                                                         
        If the error occurred in your own ABAP program or in an SAP                                  
        program you modified, try to remove the error.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                       
        find an interim solution in an SAP Note.                                                     
        If you have access to SAP Notes, carry out a search with the following                       
        keywords:                                                                               
    "CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"                                                 
        "SAPLCV120" or "LCV120F28"                                                                   
        "SYS_GET_WINDOW_SYSTEM"                                                                               
    If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                               
        "SYS_GET_WINDOW_SYSTEM" "(FORM)", or its possible occurrence must be declared                
         in the                                                                               
    RAISING clause of the procedure.                                                             
        To prevent the exception, note the following:                                                
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "APP2"                                                                 
        Network address...... "132.147.166.13"                                                       
        Operating system..... "Windows NT"                                                           
        Release.............. "5.2"                                                                  
        Hardware type........ "2x IA64 Level 3"                                                      
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "DB"                                                                      
        Database type..... "MSSQL"                                                                   
        Database name..... "ELP"                                                                     
        Database user ID.. "elp"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 23 2009 22:38:30"                                                     
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                             
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 221                                                                               
    Patch text.. " "                                                                               
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
        SAP database version. 700                                                                    
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows               
         NT 6.0"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 29328880                                                                               
    Heap.... 0                                                                               
    Page.... 655360                                                                               
    MM Used. 3095760                                                                               
    MM Free. 1091456                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                     
        User................ "CPTN_SAPC5"                                                            
        Language key........ "E"                                                                     
        Transaction......... "CV03N "                                                                
        Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"                                                                               
    Program............. "SAPLCV120"                                                             
        Screen.............. "SAPLCV110 0101"                                                        
        Screen line......... 3  
    regards
    kunal

    Hi Kunal,
    you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
    then you can display these files.
    Regards,
    Ravindra

  • While click on document shows error"document type not defined"

    HI
    we have folder structure in  DMS like:
    public folder->engineering folder->design folder->document(any)
    while i am clicking on document it shows error msg document type not defined
    please let me know why this error occur

    Hi,
    Since you are using document structure functionality, You are require to create an public folder initially and private folder for each user which is specific to user ID.
    If you dont want to create private folder you can select "Select document Via in CV03N screen and select only" Selection screen " and not browser.
    If the above changes is done then system will not through an error from CV03N screen"document type not defined"
    reward points if useful.
    Rgds,
    Nayeem.

  • Error in inserting field to CV01n

    Hello Dears,
    I should insert new Zfield to Tcode CV01n.
    Then,
    I created a new Zfield and added it to the tabel ( DRAT table ),
    and want add this Zfield to the screen layout.
    Program: SAPLCV110
    Screen No: 102
    I'm going to Layout Editor and try to change layout, but unfortunately after edit screen, some errors occur and some I/O fields hide and I can't find them into the layout and they deleted from element list.
    (For Exp: : "Input/output field "DRAT-DKTXT" not defined.")
    Therefore, kindly request you to guide me on this matter.

    Hi Dear Chandra,
    I added I/O field DART-DKTXT and other necessary fields to screen and I could activate screen.
    But status of my inserted fields (And other I/O fileds like DART-DKTXT) are not correct.
    For exp: in view mode (CV03n) these fields are editable.
    Regards,

  • CV03n - illegal original name

    Hi !
    We get an error at transaction CV03n.
    Here is the step by step description :
    The error appear with original names that contains ilegal charecter's like: space,#, @, etc.
    I execute transaction CV03n with the following parameters :
    Document: 8004434
    type : kp2
    Part 000
    Version 01
    Then i press Enter key i enter to document basic data and originals.
    At that screen when i prees the ICon print to print the original - " Motherboard e-2000210001.plt " i get the folowing error mesage :
    " Invalid file y:/Ts/Temp/17 Print server will be shut down "
    As we can see the original name contain invalid character space. however If i try to use an original that doesn't contain an invalid character it works proper and the error doesn't appear.
    We use external viewers to open our documents ( *.plt -> fastlook
    *.doc -> word, *.pdf-> acrobat ). The problem of " Invalid file y:/Ts/Temp/17 Print server will be shut down " appear when i also try to open a
    file that located at my local harddisk ( not at the context server ).
    Meaning the error appear at the level of R3 and the external viewers
    and not at the level of R3 and the context server.
    So i can i solve this problem ? How can i cause the system to recognize the invalid charecter's as valid ?
    Thanks
    moshe

    Hello Intern Support -- And thanks for participating in the Community. I've discussed this issue with Product Engineering and am sharing their response:
    The "Illegal SSID Name!" error message will be updated in next release and will be changed to "The SSID Name including spaces (i.e. blank symbols) is illegal in this AP implementation! ". Thank you for the input.
    As for the potential harm, according to some customer experiences, as well as our software baseline requirement study, "space" on SSID name will have some risks. For example, if my office announces a normal wireless SSID for Guest/Visitor, it's named "VIP". But if some guys set others AP that SSID name is "VIP ", "V I P" or " VIP" , it's too similar to"VIP". It might cause Wireless Station to associate an illegal AP unless the correct one used the encryption mode.
    Thanks again for sharing your concerns and special thanks for choosing Cisco Small Business.
    Stephanie Reaves
    Cisco Small Business Technology Group

Maybe you are looking for