Product Description too short

The product description in the back end is too short! When you have multiple attributes for a product, it is impossible to view which the customer chose when you open up the order.
Where can I view each attribute(which are in the form of dropdowns on the frontend) that the client chose?
I have attached an image for you to view. You'll see the description only allows for certain amount of characters!
Thank you!

I think you should try to use expert mode for building Alternative id for your requirement.
Select the expert mode in the initial screen , then in the expert mode select the Do Not Generate check box.. Next build your own class by copying the CL_ALTID_PRODUCT_CUSTOMER_ID and in this class try to modify the methods to read the product descriptions for alternative id. You may look at the standard class for more details.
The idea is to create an ID that needs to reference particular table ( in your case , the product descriptions table )
I guess you have to explore more on this. It is not straight forward.
Hope it helps.
Regards,
Shaik

Similar Messages

Creation of a product description field of length 250 car. used for search?

Hi all,
we need to create a specific description field for products with a length of 250 (the standard description is too short at 40 car, =>table COMM_SHTXT) . That field should also be added to the search criteria.
What would be the best solution for this creation , given that the field must exist also in ECC SD from where the product is replicated to CRM :
-creation of a Z-append to the product table in ECC (table MARA?) and a corresponding include in the product table in CRM (COMM_PRODUCT) ?
-creation of an attribute in ECC (or Z-append) and creation of a "set attribute" in CRM (i.e transaction COMM_ATTRSET), but there are warning in CRM when you create an attribute of length > 132.
-using the standard Texts (no limitation of lenght) attached to products : is a search possible on these texts?or too complicated/poor performance ?
Regarding the display in CRM UI, is it possible to display all the 250 caracters if the field is a customized "set attribute" or a Z-append? It seems that it is not possible to display a string field on more than one line in the UI configuration, or even, on more than 8 columns in an assignment block?
thanks for your help
Ludovic

well, I have found at least how to replace the error message (length of max 75 car for PC UI) . Instead of trying to edit manually table T100C, there is an entry in customizing SPRO (cross appl/SAP Product/basic settings/Define Characteristics of System Messages
) which allows to customize standard messages , and so change from Error to Warning.

Libclntsh.so.10.1: file too short

Hello All,
I am reinstalling clusterware 10g R2 at REL 5.1 at last when trying to execute root.sh script with 'root' user following error is raising
can any one help me out to fix it please.
+++++++++++Error Description++++++++++++++
/u01/app/oracle/product/10.2.0/crs/bin/ocrconfig.bin: error while loading shared libraries: /u01/app/oracle/product/10.2.0/crs/lib/libclntsh.so.10.1: file too short
Failed to upgrade Oracle Cluster Registry configuration
Regards,
Farrukh Salman,

i wrote a script which uses the connection method you describe like this:
To connect to a local database with a user which has been set-up to
authenticate via the OS ("ALTER USER username IDENTIFIED EXTERNALLY"):
$dbh = DBI-> connect('dbi:Oracle:','/','');
Note the lack of a connection name (use the ORACLE_SID environment
variable).
My tnsnames.ora looks like:
BBA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dhcp-144.int.consol.de)(PORT = 1521))
"tnsping bba" worked fine, but my perl-script (where is set $ENV{ORACLE_SID}
= "bba") always said:
CRITICAL - cannot connect to . ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory (DBD ERROR: OCISessionBegin)
What i didn't know, tnsping seems to try also the upper case, that's why i
blindly set ORACLE_SID also to "bba".
Now, 13 hours later (reading half of the internet, reading process and
network traces), i accidentially typed the ORACLE_SID in upper case and it
worked.
In order to save other people from spending hours in desperation, i propose
to add a warning message on the cpan webpage:
The ORACLE_SID is case sensitive, use the exact copy of the value from
tnsnames.ora or forget it.

DVI to VGA adapter Isn't it too short

I bought a MB Pro and I wanted to use the DVI to VGA adapter but it's too short, is there a longer one or is this it?

Maybe http://www.microcenter.com/singleproduct_results.phtml?productid=0201448 if you need a male-to-female. In other words, that product should work if the port on the TV has pins sticking out. If it has holes that pins should be stuck into, then http://www.microcenter.com/singleproduct_results.phtml?productid=0201735 is a male-to-male. Make sure you double check the photos against your adapter and your TV before you buy. Also try your local electronics or computer store.
dapeter2: Thanks for your clarification.

Error "602" System error: AK Datapart too short

Hi all,
Ok, I have looked just about everywhere for an answer to this but to no avail...I even tried under a few rocks we have laying around.
Anyway here it is:
While running a compression in BW we get Error "602" System error: AK Datapart too short.
This is happening while doing a select statement during the compression of the infocube. It does not happen all the time, just kind like when ever it feels like. The only note I could find in OSS was one about Live Cache and it does not seem to apply.
Here is the dump which I really hate doing this, but it gives all the info needed :
untime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          08/15/2007 12:23:09
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error "-602" occurred in the current database connection "DEFAULT".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "System error: AK Datapart too short"
Database error code .......: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/EZPSD_C03" ( "KEY_ZPSD_C03P",
"KEY_ZPSD_C03T", "KEY_ZPSD_C03U", "KEY_ZPSD_C031", "KEY_ZPSD_C032",
"KEY_ZPSD_C033", "KEY_ZPSD_C034", "/BIC/ZNET_ASP" ) SELECT ? ,
F."KEY_ZPSD_C03T", F."KEY_ZPSD_C03U", F."KEY_ZPSD_C031", F."KEY_ZPSD_C032","
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"GP31VIZWJDTT90894L1IA5YAC7G" or "GP31VIZWJDTT90894L1IA5YAC7G"
"TRANSFER_ALL"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"TRANSFER_ALL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "sdcbw03"
Network address.......... "10.64.18.76"
Operating system......... "Linux"
Release.................. "2.6.9-55.ELsmp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 21
Short dump setting....... "full"
Database server.......... "sdcbw03"
Database type............ "ADABAS D"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 5 2006 19:46:34"
Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version......... "SAPDB 7.5.0.030 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 20949280
Heap..................... 0
Page..................... 24576
MM Used.................. 9235016
MM Free.................. 3331560
SAP Release.............. "640"
User and Transaction
Client.............. 011
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "GP31VIZWJDTT90894L1IA5YAC7G"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "GP31VIZWJDTT90894L1IA5YAC7G" in
"TRANSFER_ALL".
The main program was "RSPROCESS ".
The termination occurred in line 573 of the source code of the (Include)
program "GP31VIZWJDTT90894L1IA5YAC7G"
of the source code of program "GP31VIZWJDTT90894L1IA5YAC7G" (when calling the
editor 5730).
The program "GP31VIZWJDTT90894L1IA5YAC7G" was started as a background job.
Job name........ "BI_PROCESS_COMPRESS"
Job initiator... "ALEREMOTE"
Job number...... 12185102
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "TRANSFER_ALL" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GP31VIZWJDTT90894L1IA5YAC7G ". Its source code
starts in line 557
of the (Include) program "GP31VIZWJDTT90894L1IA5YAC7G ".
Source Code Extract
Line
SourceCde
543
ENDIF.
544
545
COMMIT WORK.   " commit and close cursors
546
547
l_str = i_max_requid.
548
PERFORM msg_append(saplrscondense)
549
USING    'S' '355' l_str space space space
550
CHANGING c_t_msg.
551
552
ENDFORM.                               " CONDENSE_FACTTABLE_NEW
553
554
555
     Form TRANSFER_ALL
556
557
FORM TRANSFER_ALL USING i_ref_update       TYPE rs_bool
558
i_pdimid           TYPE I
559
i_pdimid_ref_point TYPE rsd_sid
560
i_pdimid_normal    TYPE rsd_sid
561
i_recordtp         TYPE rsd_sid
562
CHANGING e_ref_ins_cnt TYPE I
563
e_ins_cnt     TYPE I
564
c_t_msg       TYPE rs_t_msg.
565
566
CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_DROP'
567
EXPORTING
568
I_INFOCUBE = 'ZPSD_C03'
569
I_FACTTAB = '/BIC/EZPSD_C03'.
570
571
572
EXEC SQL.
>>>>>
INSERT INTO "/BIC/EZPSD_C03"
574
( "KEY_ZPSD_C03P"
575
, "KEY_ZPSD_C03T"
576
, "KEY_ZPSD_C03U"
577
, "KEY_ZPSD_C031"
578
, "KEY_ZPSD_C032"
579
, "KEY_ZPSD_C033"
580
, "KEY_ZPSD_C034"
581
, "/BIC/ZNET_ASP"
582
583
SELECT :i_pdimid_normal
584
, F."KEY_ZPSD_C03T"
585
, F."KEY_ZPSD_C03U"
586
, F."KEY_ZPSD_C031"
587
, F."KEY_ZPSD_C032"
588
, F."KEY_ZPSD_C033"
589
, F."KEY_ZPSD_C034"
590
, SUM( F."/BIC/ZNET_ASP" )
591
FROM "/BIC/FZPSD_C03" F
592
WHERE F."KEY_ZPSD_C03P" = :i_pdimid
Any thoughts would be helpful,
Thanks,
David

This error usually occurs when there is a database lock or no space in teh database. Got DB02 and Click on Space critical objects to see whether any entries are there. If yes contact your basis to increase the space.
Hope this helps
Thanks,
Satish

Can't connect to wifi password too short

Two of my local cafes have free wifi but their passwords are too short.
I enter their passwords correctly but he join button stays greyed out.
Is there a work around or not.
Answers like hey get them to upgrade their security aren't helpful.

Have you asked them?
What is the key the gave you?
If you have a Windows 8, 7, Vista or Mac laptop you can also use the free inSSIDer utility to tell you the encryption type.
http://www.metageek.net/products/inssider/
http://www.metageek.net/products/inssider-for-mac/

/lib/i386/libawt.so: /usr/lib/libXtst.so.6: file too short occurred. error

I am doing 10AS(10.1.3.5) upgrade on 64bit OL 5 os with R1211/11.2.0.3 database.
I set the environment file and trying to run runinstaller, i am getting below error.
=====================
[applmgr@apps Disk1]$ ./runInstaller -ignoreSysPrereqs
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be redhat-Red Hat Enterprise Linux AS release 3, redhat-Red Hat Enterprise Linux AS release 4, redhat-Red Hat Enterprise Linux ES release 3, redhat-Red Hat Enterprise Linux ES release 4, redhat-3, redhat-4, redhat-5, SuSE-9 or SuSE-10
Passed
All installer requirements met.
Checking Temp space: must be greater than 400 MB. Actual 6491 MB Passed
Checking swap space: must be greater than 512 MB. Actual 5122MB Passed
Checking monitor: must be configured to display at least 256 colors Failed <<<<
>>> Could not execute auto check for display colors using command /usr/X11R6/bin/xdpyinfo. Check if the DISPLAY variable is set.
Checking if CPU speed is above 300 MHz. Actual 2666 MHz Passed
Ignoring optional pre-requisite failures. Continuing...Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-03-11_08-05-11PM. Please wait ...[applmgr@apps Disk1]$ Oracle Universal Installer, Version 10.1.0.6.0 Production
Copyright (C) 1999, 2009, Oracle. All rights reserved.
Exception java.lang.UnsatisfiedLinkError: /tmp/OraInstall2013-03-11_08-05-11PM/jre/1.4.2/lib/i386/libawt.so: /usr/lib/libXtst.so.6: file too short occurred..
java.lang.UnsatisfiedLinkError: /tmp/OraInstall2013-03-11_08-05-11PM/jre/1.4.2/lib/i386/libawt.so: /usr/lib/libXtst.so.6: file too short
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at sun.security.action.LoadLibraryAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
at sun.awt.DebugHelper.<clinit>(Unknown Source)
at java.awt.Component.<clinit>(Unknown Source)
at oracle.sysman.oii.oiif.oiifm.OiifmGraphicInterfaceManager.<init>(OiifmGraphicInterfaceManager.java:193)
at oracle.sysman.oii.oiic.OiicSessionInterfaceManager.createInterfaceManager(OiicSessionInterfaceManager.java:174)
at oracle.sysman.oii.oiic.OiicSessionInterfaceManager.getInterfaceManager(OiicSessionInterfaceManager.java:183)
at oracle.sysman.oii.oiic.OiicInstaller.<init>(OiicInstaller.java:279)
at oracle.sysman.oii.oiic.OiicInstaller.runInstaller(OiicInstaller.java:739)
at oracle.sysman.oii.oiic.OiicInstaller.main(OiicInstaller.java:653)
Exception in thread "main" java.lang.NoClassDefFoundError
at oracle.sysman.oii.oiif.oiifm.OiifmGraphicInterfaceManager.<init>(OiifmGraphicInterfaceManager.java:193)
at oracle.sysman.oii.oiic.OiicSessionInterfaceManager.createInterfaceManager(OiicSessionInterfaceManager.java:174)
at oracle.sysman.oii.oiic.OiicSessionInterfaceManager.getInterfaceManager(OiicSessionInterfaceManager.java:183)
at oracle.sysman.oii.oiif.oiifm.OiifmAlert.<clinit>(OiifmAlert.java:112)
at oracle.sysman.oii.oiic.OiicInstaller.runInstaller(OiicInstaller.java:797)
at oracle.sysman.oii.oiic.OiicInstaller.main(OiicInstaller.java:653)
here is /usr/lib information.
wxrwx 1 root root 20 Feb 21 17:07 libodbcpsql.so -> libodbcpsql.so.2.0.0
lrwxrwxrwx 1 root root 19 Feb 21 17:07 libodbcnnS.so.1 -> libodbcnnS.so.1.0.0
lrwxrwxrwx 1 root root 19 Feb 21 17:07 libodbcmyS.so.1 -> libodbcmyS.so.1.0.0
lrwxrwxrwx 1 root root 19 Feb 21 17:07 libodbcmyS.so -> libodbcmyS.so.1.0.0
lrwxrwxrwx 1 root root 21 Feb 21 17:07 libodbcminiS.so.1 -> libodbcminiS.so.1.0.0
lrwxrwxrwx 1 root root 20 Feb 21 17:07 libodbcinst.so.1 -> libodbcinst.so.1.0.0
lrwxrwxrwx 1 root root 24 Feb 21 17:07 libodbcdrvcfg2S.so.1 -> libodbcdrvcfg2S.so.1.0.0
lrwxrwxrwx 1 root root 24 Feb 21 17:07 libodbcdrvcfg1S.so.1 -> libodbcdrvcfg1S.so.1.0.0
lrwxrwxrwx 1 root root 18 Feb 21 17:07 libodbccr.so.1 -> libodbccr.so.1.0.0
lrwxrwxrwx 1 root root 14 Feb 21 17:07 libnn.so.1 -> libnn.so.1.0.0
lrwxrwxrwx 1 root root 18 Feb 21 17:07 libmimerS.so.1 -> libmimerS.so.1.0.0
lrwxrwxrwx 1 root root 18 Feb 21 17:07 libgtrtst.so.1 -> libgtrtst.so.1.0.0
lrwxrwxrwx 1 root root 18 Feb 21 17:07 libesoobS.so.1 -> libesoobS.so.1.0.0
lrwxrwxrwx 1 root root 22 Feb 21 17:07 libboundparam.so.1 -> libboundparam.so.1.0.0
lrwxrwxrwx 1 root root 14 Feb 22 19:22 libXp.so.6 -> libXp.so.6.2.0
lrwxrwxrwx 1 root root 25 Mar 5 23:10 libdb.so.2 -> /usr/lib/libgdbm.so.2.0.0
-rwxr-xr-x 1 root root 0 Mar 11 03:21 libXtst.so.6.1.0
lrwxrwxrwx 1 root root 29 Mar 11 03:22 libXtst.so.6 -> /usr/X11R6/lib/libXtst.so.6.1

Hi;
Please review:
Oracle Application Server 10g (10.1.2) Installation Requirements for Linux OEL 5 and RHEL 5 [ID 564174.1]
Regard
Helios

1.2.1 to EA2: connection list too short

Hi,
clicking on the button located in the main tool bar to chose a db connections provides a list showing all my defined connections is too short depending on the size an solution of the screen. To have the ability to select all of the many defined db connections there should be a vertical slide bar in this list.
This behavior exists in the actual production version and the new EA1 and EA2 as well.
Is that important enough going to get fixed in the current version?
Regards
Peter M.

Did you know that you can click on either the little drop black arrow, which drops a list (not scrollable) or you can click just the the left of that. This gives you a small dialog window with a scrollbar. The dialog window is re-sizable (width-wise) and has a scrollbar.
These list will not use folders in 1.5. You can add an ER if you want that.
Sue

Channel length too short for calculation

I've just switched from 9.1 to 2010 and I was told that our VBS scripts wouldn't need updating - not so it seems.
I have the following piece of code:
Call ChnAlloc("Input PSD")
L1=Cno("RealPart")
L2=Cno("ImaginaryPart")
Call FormulaCalc("Ch('Input PSD'):=Ch(L1)^2+Ch(L2)^2")
but this doesn't work anymore. I get an error message saying that channel 7 (Input PSD) is too short for calculation. Previously I would have checked the data matrix but I can't find this anymore so I assume DIAdem works in a different way know. The help files suggest that the channel length option for ChnAlloc is optional so I don't understand why it thinks the channel is too short.
Any help appreciated.
Thanks, Si.

Hi SI,
You only need a minor addition, and you get the benefit that all new channels can have their length(s) dynamically changed. Please add this line of code after creating the channel and before the FormulaCalc() command:
ChnLength("Input PSD") = NeededNumberOfRows
Back in the dark days of the DIAdem memory matrix, DIAdem would by default launch with 60 static channels of exactly 8196 rows each. As you apparently know, you could customize the memory matrix to have fewer or more channels, and you could change their static lengths assigned when DIAdem launched. The fully dynamic channel lengths are a vast improvement, but it does mean that for FormulaCalc() commands you need to tell the channel to be big enough first. Interestingly, none of the ANALYSIS commands require you to do explicitly set the channel length before writing to them-- just the channel calculator.
Ask if you have any further trouble,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

Paragraph Rules Run Too Short Under Text

I've noticed that when I select a paragraph rule to run under some text (instead of the whole column) that it runs a little too short if the text has been tracked. If there's no kerning or tracking, the rule runs the width of the text just fine. But soon as the text is stretched out the rule doesn't quite extend the entire way under the text. Is there a way to fix this? I have InDesign CS5 for Windows (ver. 7.0.4).
Ed Hedemann

@ Lilia,
Forced line breaks are special characters, too.
But here's the good news. I tested your theory this morning about not applying the tracking to the last character and it DOES work for all alignment options, and it does not move the last character's position, so it is viable, in fact excellent, when applied using the GREP style. So for headings (or any other tracked paragarph that needs a Rule Below set to text width and where the text is tracked with a positive value) you want to create a 0 tracking character style and apply it to the last character inthe paragraph using .$
The tracking value should be added to the basic character format of the paragraph style:
The character style should do nothing but assign a tracking value of 0:
And that character style should be applied as a GREP Style like this:
No special characters and comletely automatic, and the text can be edited at will, or the formatting in the style can be changed and it will continue to work.
Well done.
By the way, welcome to the forum. If you want to learn about GREP, and you should, both as a teacher and an obviously talented user, I highly recommend Peter Kahrel's primer from O'Reilly: http://shop.oreilly.com/product/9780596156015.do which is a real bargain at $9.99 and available as PDF, Mobi or ePub. GREP is incredibly powerful, and actually not terribly difficult to learn (and the Find/Change dialog in ID has most of the commonly used metacharacters in the dropdowns if you have trouble memorizing). There are many users here who will be glad to help you learn GREP, including Peter K, if you run into a stumbling block and post a question.
I'm also going to update my bug report from last night to include your workaround. It might point the engineers toward an easy way to fix the code so none of this will be necessary someday.

Occasional Task Sequence fail (1 out of 5) with Error 615 Your Password is too short

We have a task sequence that fails to install software and updates with an error liek this: Operation System Error 615: The password you provided was too short for the computers password policy. Please provide a longer password.
With all software installations I always tick the continue on failure. Consequently in a task sequence you see the entire list of installation requirements fail with this error. This includes Applications, Packages and Software Updates. Without any amendment,
the next time it is run, it runs successfully. Add to this the issue that the task sequence no longer displays the progress bar after rebooting into windows (x64) and it all points to the OSD process being a bit flaky.
By the way, we are installing Win7 x64 (No x86 anymore) over PXE.
So any pointers with this would be very gratefully received.
Anthony Sheehy - MCP, MCITP

Here is the status message sent to Configuration Manager:
The task sequence execution engine failed executing the action (Freefall Sensor) in the group (Install) with the error code 2278559764
Action output: 7"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)
0, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\WGS00137
reference count 1 for the source C:\_SMSTaskSequence\Packages\WGS00137 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\WGS00137
Released the resolved source C:\_SMSTaskSequence\Packages\WGS00137
pInstall->Install(sPackageID, sProgramName), HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Failed to invoke Execution Manager to Install Software for PackageID='WGS00137' ProgramID='Silent Installation' AdvertID='WES20013' hr=0x87d01014
InstallSoftware failed, hr=0x87d01014
Install Software failed, hr=0x87d01014. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
And here's the group policy that is applied to that OU:
Enforce password history
0 passwords remembered
Maximum password age
0 days
Minimum password age
0 days
Minimum password length
0 characters
Password must meet complexity requirements
Disabled
Of course, the password complexity issue is a non-starter: How come SCCM 2007 task sequences did not have the same problem? Why does the Task Sequence work
sometimes and not others. All passwords I provide to Configuration Manager all conform to complexity rules anyway.
The relevant SMSTS.log portion is below:
<![LOG[Variable name: _SMSSWDProgramName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsswd.exe /pkg:WGS00137 /install /basevar: /continueOnError:]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 90]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Applications]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_382fdd99-2228-452d-a6f0-63e543ce628d /basevar: /continueOnError:True]LOG]!><time="18:06:06.660-60"
date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 91]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Language Packs]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_9df3ec9a-e691-4106-b274-46c4c6c319b9,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_42e28566-b339-4773-92cf-05b8e748d996,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_305b4a34-0b5a-46fe-82dd-c57a5897e063,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_379afca3-f48e-486b-8848-296223481edd,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_502bf2db-e1c8-42ac-a499-61320d661cc3,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_455a6de9-fe98-47ed-8dab-e860dd4681ed,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_1707c97e-b4bb-4827-9117-02e79435213e,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_a17f2337-ad2e-42cb-9813-c9e167a85050
/basevar: /continueOnError:True]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 92]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[Processed all elements]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:333">
<![LOG[Adding end group instruction at 93]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:402">
<![LOG[The next instruction after group will be at 94]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:408">
<![LOG[
Parsing step node: Opt In to CEIP and WER]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
Anthony Sheehy - MCP, MCITP

Apple Mini DVI to DVI Adapter - Too short?

I want to connect my iMac 2.8 ghz, 24" screen to an external Philips 190B LCD monitor and use the Extended Desktop function.
The Philips Monitor model is the 190B6CG/00 and it is a single link monitor (Philips tell me it is DVI-D Receptacle Connector 24 pin = single link).
I'm looking at the Apple Mini DVI to DVI adapter here on the Apple Store. It looks like it should plug into my iMac one end then the other end into my Philips. However it looks like it is too short to reach my Philips Monitor. They are not a fantastic distance apart. In fact they are sat side by side - but I somehow can't see the Apple Adapter being long enough (unless it crosses a 3-sphere).
Presumably then, some sort of extension is required between the DVI end of the Apple adapter and the Philips Monitor's DVI input.
Does anyone know what this extension could be and where is may be purchased?
Regards

Hello to everyone who has replied to my cry for help.
Thank you all. I will apply points to everyone who has responded (so quickly too).
Scorpie
I totally agree. I have been thinking along these lines too. However, searching on the internet whilst researching, I found it difficult to decide what I needed because of the 'photos' supplied. They were ok as such but most didn't show very well the pin outs. Further research into the matter (and one website in particular - i.e. Maplin) made me realise that GENDER was involved. Also, with DVI, females look like males in web photos until you find a photo from the right angle. Same goes for VGA I reckon.
I'm certain most people looking at DVI (and VGA) cable/connectors can't tell the difference when the devices are only viewed from 'above' . In my opinion they need to be viewed more or less end-on to show where they have pins or holes. I mean full end-on, not at an angle where (as I found above) detail as to pin or hole is lost in digital or compression noise. This is what I have experienced in all but one of the web sites I have visited. Another thing, most websites have an 'enlarged version' button which, if selected, shows the same photo exactly the same size. No help whatsoever. But then there's no doubt you must already be well aware of this.
MyHighway
You are correct. The Philips did come with a VGA cable. However I want to connect to my iMac digitally (if I can) using DVI (it looks like a 'female' connector on inspection of the back of the Monitor). I have found it almost impossible to tell the difference from most photos on the web even with my new huge screen iMac. One of the reasons I'm am a little nonplussed I think.
mrtotes
Good point. If I take a photo of the back of my Philips and take the Apple connector down to Maplin perhaps I can compare and contrast with real specimens. Yo!!
I think I will give that a go.
You have all been very helpful indeed. Opened my eyes somewhat.
I wish a Merry Christmas to all my new Mac friends

DVI to VGA adapter. Too short?

Hello.
Please do not blame me for being ignorant, I recently had to do a project and in order to connect to the screen, I need to use a DVI to VGA adapter, which is provided when I bought my MBP.
But then, isnt it too short? How do I connect it then? Must I buy a extension? Do help me as my project is due next friday and I must present next friday. Thank you.

Allan Jones wrote:
The sequence would be:
Mac > Adaptor > VGA cable > Monitor or projector
Right - except when actually hooking them up, they should be connected in the reverse of that sequence; the projector should be on and seeking an input, the cable and adapter should be connected, and the final step is to connect the adapter to the MBP.

HT1920 I have got a Activation Lock on my iPhone and I need to get it activated. I don't know what Apple ID I was using with my iPhone. It shows as U***@h******.uk which is too short to be my email address. I have reset all my Apple ID passwords and none

I have got a Activation Lock on my iPhone and I need to get it activated. I don't know what Apple ID I was using with my iPhone. It shows as U***@h******.uk which is too short to be my email address. I have reset all my Apple ID passwords and none are activating my iPhone. I have also been into the apple store and they have tried to find out the Apple ID my iPhone was using but this was not successful. The serial number of my iPhone is: C32JN641DTWF

You are going to need to change the email address you use with your old ID. Once you have got access to your old account you will then log into both accounts at the same time on your Mac and transfer your data to a single account. We can do this later, but need you to get access to your old account first.
My Apple ID

Postal code is too short or invalid when trying to sign up for windows azure

https://account.windowsazure.com/signup?offer=ms-azr-0044p
language is Netherlands
country is Belgium
postal code is "8870" but is considered too short
I also tried "BE8870" or "BE-8870" but these are considered invalid
how do I continue?

HI
May be you can try "8870 Emelgem".
If still can't help Please contactsupport team by creating a support ticket at
http://www.windowsazure.com/en-us/support/contact/
Or if that doesn't work because you don't have an active subscription you will need to contact general customer support to have them create a support ticket for you
http://support.microsoft.com/gp/customer-service-phone-numbers?wa=wsignin1.0
Dino He
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Product Description too short

Similar Messages

Maybe you are looking for