Folder Directory Create

I recently Migrated our sharepoint from windows 2003 to 2008. In doing so I lost Cold fusion and a directory Wizard, This wizard was put in place to create a folder directory out on our network drive when used. Now I have Coldfusion 10 installed on my new sharepoint server, I have brought over all of these directory wizard files but it still does not work. Its like I am missing a certain link in the chain here. Can anyone shed some light on the topic?
The wizard opens up to the first page, which it says next to continue. You would select a company which the code is written to pull a companies list from the network drive, then it creates a folder directory with files in the on that network drive. Now when you lick the initital next button it buttons and takes us to a The website cannot display the page. I still have all the original code files, placed into the same exact directory on the sharepoint server. The sharepoint server is an identical match, but its like somewhere something isnt lined up correctly.
I also have downloaded Coldfusion builder also.

OKay since page 1 actually doesnt do anything I can skip that, and ill start on page 2 and the other esential code files that actually build the directory.
DIRECTORY.CFM
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
in Direct Input mode, no MIME Media Type is served to the validator
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
Using Direct Input mode: UTF-8 character encoding assumed
Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator's form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.
If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.
↑ Top
Validation Output: 27 Errors
Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"<HTML>
✉
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
Line 3, Column 11: cannot generate system identifier for general entity "I" <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 3, Column 11: general entity "I" not defined and no default entity <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3, Column 12: reference to entity "I" for which no system identifier could be generated <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 3, Column 10: entity was defined here <TITLE>C&I Engineering - Project Directory Wizard</TITLE>
Line 10, Column 21: there is no attribute "TEMPLATE"<CFINCLUDE TEMPLATE="HEADER.CFM">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 10, Column 33: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="HEADER.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 11, Column 45: invalid comment declaration: found name character outside comment but inside comment declaration<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
✉
Line 11, Column 1: comment declaration started here<!---<CFINCLUDE TEMPLATE="BUTTONBAR.CFM"> --->
Line 12, Column 35: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="MAINAREA.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 16, Column 3: invalid comment declaration: found name character outside comment but inside comment declaration--->
✉
Line 14, Column 1: comment declaration started here<!---
Line 20, Column 28: there is no attribute "HEIGHT"<TABLE WIDTH="100%" HEIGHT="100%" BGCOLOR="#D4D0C8">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 24, Column 21: there is no attribute "ACTION"<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 24, Column 38: there is no attribute "DIRECTORY"<CFDIRECTORY action="list" DIRECTORY="\\ci-data\shared\PROJECTS"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 25, Column 10: there is no attribute "NAME"    NAME="myDirectory"
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 26, Column 10: there is no attribute "SORT"    SORT="Name ASC">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 26, Column 20: element "CFDIRECTORY" undefined    SORT="Name ASC">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 27, Column 15: there is no attribute "NAME"<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 27, Column 43: there is no attribute "DEFAULT"<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 27, Column 45: element "CFPARAM" undefined<CFPARAM NAME="SELECTEDDIRECTORY" DEFAULT="">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 31, Column 17: there is no attribute "QUERY"<CFOUTPUT QUERY="myDirectory">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 31, Column 30: element "CFOUTPUT" undefined<CFOUTPUT QUERY="myDirectory">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 32, Column 12: "TYPE" is not a member of a group specified for any attribute<CFIF TYPE IS "Dir">
✉
Line 32, Column 15: an attribute value literal can occur in an attribute specification list only after a VI delimiter<CFIF TYPE IS "Dir">
✉
Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".
Line 32, Column 15: element "CFIF" undefined<CFIF TYPE IS "Dir">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 33, Column 8: an attribute specification must start with a name or name token <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
✉
An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).
Line 33, Column 8: element "CFIF" undefined <CFIF "#NAME#" IS "#UCASE(SELECTEDDIRECTORY)#">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 35, Column 9: element "CFELSE" undefined <CFELSE>
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 54, Column 40: element "CFINCLUDE" undefined<CFINCLUDE TEMPLATE="ACTIONBUTTONS.CFM">
✉
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 57, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this</BODY>
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 7, Column 1: start tag was here<CENTER>

Similar Messages

  • Error 7 occurred at Create Folder in Create Directory Recursive.vi-

    Recieved following message when attemoting to create source distribution
    Error 7 occurred at Create Folder in Create Directory Recursive.vi->ABAPI Dist Create Directory Recursive.vi->ABAPI Dist Chk for Destinations.vi->ABAPI Copy Files and Apply Settings.vi->SDBEP_Invoke_Build_Engine.vi->SDBUIP_Build_Invoke.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_Item_OnDoProperties.vi->SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.

    Hello,
    Could you please list which options you are selecting when building a
    source distribution (I am assuming you are using LabVIEW 8.0?).
    Do you get this error when clicking on "Generate Preview" button when configuring source distribution properties?
    Under "Distribution Settings" category, could you try checking the
    "Disconnect type definitions and remove unuses polymorphic VI
    instances" option and see if that helps with the build process?
    Also I suggest Mass Compiling your VIs (Tools -> Advanced -> Mass Compile) before creating a source distribution.
    If these do not help, could you attach your project with all the VIs it contains here?
    Thank you and best regards,
    Shakhina P.
    Applications Engineer
    National Instruments

  • How to prevent users from creating new folders in share folder directory?

    Hello guys
    I'd like to know How to prevent users from creating new folders in share folder directory but still keep their power of creating new folders in their personal 'my folder'?
    I tried changing the 'manage privilage ---- create folder' to deny certain user accounts, but by doing so, it also stops the user from creating new folders in their 'my folder', which is not good..
    I also tried going into these share folders and tried different access types such as 'change/delete', 'read', 'traverse folder' etc, but none of it work ideally. The 'change/delete' access still allows them to create new folders, 'read' access prevents creating new folders but also take away their power of saving reports..
    Any thoughts on how to take away their ability to ONLY create new folders in share folder areas without affecting their other privileges?
    Please advise
    Thank you

    Easy, on the shared folders root folder only give them 'read' or 'traverse folder' but on the the folder inside the shared folders root folder give them 'change/delete'. That means they can change anything inside those folders but not create any folders at the shared folders root level.

  • Error 1430 occurred at Create Folder in Create Directory Recursive.​vi

    Hi all..
    I am facing the error which stated :
    Error 1430 occurred at Create Folder in Create DirectoryRecursive.vi->AB_Destination.lvclass:Crea​te_Destination.vi->AB_Build.lvclass:Create_Destina​tions.vi->AB_Application.lvclass:Create_Destinatio​ns.vi->AB_Build.lvclass:Build.vi->AB_Application.l​vclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build​.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.l​vclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoP​roperties.vi->AB_Item_OnDoProperties.vi.ProxyCalle​r
    Possible reason(s):
    LabVIEW:  The path isempty or relative. You must use an absolute path.
    <Not A Path> 
    I have been trying to do all solutions given by error 6 such as check the  disconnect type definition and remove unused polymorphic VI instances, generate the absolute path and etc. However the same error still occured.
    Please advise guys~ I'm using LabView 2009. 

    I'm having the same problem when trying to build a RT executable.  
    I'm using the FTP Put Buffer.vi along with a data to string example I found on the NI website. I can build the executable when I use a constant instead of the data to string but I can't for the life of me figure out why.
    Order of pictures:
    dataftp.png, which shows the data to string connecting to the data input on the FTP Put Buffer.vi.
    vars.png,which shows thevars being placed into an array and connecting to the Convert to String vi.
    convert.png, which shows the guts of the convert to string vi.
    Attachments:
    dataftp.png ‏2 KB
    vars.png ‏5 KB
    convert.png ‏7 KB

  • How to get folder(directory path only not file path) from local file system

    Hi Firends,
    How to get folder(directory path only not file path) from local file system , whenevr i will click on browse button.
    Please give reply for this one , if anybody knows.
    Thanks,
    Anderson.

    Hi Anderson,
    if you're using flash.filesystem.FileReference - then it is run in black box - except of filename, size and creation data (and few other properties available after some operation succeeded). This is part of security features in Flash runtime (described in header section):
    http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/FileReference .html
    This for example implies that user can download a content to local machine - but that content cannot be loaded back into Flash runtime. For this you would need either Air runtime flash.filesystem.File:
    http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/filesystem/File.h tml
    (so you would created Air runtime based application: desktop or mobile but not web, even as standalone project) or you would need one of 3rd party tools that add file access/file information features to standard Flash runtime applications converted to standalone native applications.
    hth,
    kind regards,
    Peter

  • Where is the directory created?

    I have create a directory with the following command:
    create or replace directory '/tmp/';
    Where this directory created?

    See correct syntax there:
    http://www.mcs.csueastbay.edu/support/oracle/doc/10.2/server.102/b14200/statements_5007.htm
    The statement creates a database object, not a operating system object/folder. The database directory object is not validated, it is just object pointing to some operating system folder, does this folder exist or not does not matter for database, it creates the database object only.
    You must create in operating system the folder yourself. This command doens't create the OS folder.

  • I created a new folder on My Picture on my PC, but when I went into my device to sync the new folder i created i couldnt find it. How could I make it a choice of the selected folder so I can sync that onto my device?

    I created a new folder on "My Pictures" on my PC to sync some new photos, but when I went into my device to sync the new folder I created I couldnt find the new folder under "selected folders" in the sync photo section. How could I make it a choice to find my new folder I created so i could find it under "selected folder" so I could be able to sync?

    Hi there!
    Could you clarify for me: are you still using Photoshop Elements on your new Mac or are you now using the Revel Mac Desktop app?
    Thank you!
    Glenyse

  • Will someone please tell me how to change the name of a folder I created in Pages and saved to the cloud?

    Will someone please tell me how to change the name of a folder I created in "Pages" and saved to the "Cloud"? Thanks.

    Go to the open dialog in Pages and select iCloud.
    Click on the folder that you created on iCloud to open the folder.
    On the lower half of the window (the open folder) click on the name of the folder.
    Once you click and select the folder's name it should be editable.

  • Cache Directory created automatically

    Something strange has been happening recently. A folder on a second (RAID, Mirror) volume internal to my MacPro is automatically created:
    /Volumes/Stuff/System/Library/Caches/com.apple.bootstamps/0410332A-EDA4-35A7-A78 9-0F018AAB205D
    If I delete the folder it reappears a few seconds later. The process owner is root with a PID of 644 and "kextcache" pops in and out of top when the folder is created but I can't get a handle on WHICH kernel extension is doing this and why.
    Google is no help and I can't find mention of this anywhere else in these forums.
    Any suggestions?
    Thanks
    Steve

    Ummmm, if it was normal than it would happen on all Macs on all secondary drives. This is the first time I have ever seen something like this before. Additionally disk utility can't repair the disk as it can't be unmounted.
    Also as time goes on shutdown takes longer and longer, it's now up to about 5 minutes.
    It even happens in single user mode if I issue a reboot command after repairing drives and permissions with Applejack reboot returns an error message that it can't reboot as the disk in question is busy.
    So something is going on here that should not be happening and I can't find the cause or the cure.

  • SCCM Client Push Installation Wizard does not install the client. CCMSetup folder - not created

    Hello,
    I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
    the same - no SCCM client is installed on any computer.
    The computers are running 32-bit Windows XP SP2.
    The Windows firewall is disabled.
    The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
    is not enabled.
    The domain is AD WIndows 2000.
    The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
    The AD schema has been extended.
    MP, and SLP are installed and published. (MP is published in DNS as well.)
    FSP is installed.
    MP, SLP and FSP are running on the same server.
    SQL 2005 server is running locally.
    System management container is created and all rights and permissions delegated.
    With the Push installation account I can access C$ share on the client computer from the SCCM server.
    RPC, Remote registry, WMI services are running on the client machines.
    All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
    All computers are in the same IP subnet which is listed in the boundaries.
    Yet, the client is not being installed.
    No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
    what the is the issue. I do not see anything helpful in the ccm.log on the server.
    I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
    SCCM server / console.
    What else I should check / try? I really want to push agents via the wizard.
    Thank you,
    Peter

    Hi Wally,
    I have changed 2 things:
    1. Enabed automatic push installation (so I am not usign the wizard any more)
    2. Changed the IP subnet to IP ranges in the site boundairies.
    After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
    ==================================
    <![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
    <![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
    <![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
    <![LOG[CCMHTTPSSTATE:    0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
    <![LOG[FSP:    HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
    <![LOG[CCMFIRSTCERT:    0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
    <![LOG[Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
    <![LOG[MSI log file:     ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
    <![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
    <![LOG[                  \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
    <![LOG[                  \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
    <![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
    <![LOG[                  HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
    <![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
    <![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
    <![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
    <![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
    <![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
    <![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
    <![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
    <![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
    ==============================================================
    There are two red errors I am concerned about:
    "Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
    and
    "Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
    What should I do to resolve these errors?
    Thanks,
    Peter

  • Auto increment liveevent streamname folder/directory for each publish while same streamid string?

    Is it possible to auto increment a streamname when publishing to FMS?
    Instead of appending to the same folder/directory of the liveevent and stream files when publishing and unpublishing, is there an option to which if a stream is unpublished and republished to starts a new folder/directory _1, _2, _3, etc?
    Or even better, to name the folder with a timestamp of the publish? instead of _1, _2, _3 -- _2012oct8-2101, _2012oct9-0644, _2012oct10-1833
    Thanks.

    Hi,
    I think we should be able to do this.
    First - Do not specify any query string in your publish string. Just say 'livestream'. This means you are not assigning any event name.
    In the livepkgr main.asc, check out the function application.onPublish. When no event name is defined, the application uses the stream name itself as the event name. The code in livepkgr main.asc corresponding to this;
    if (queryString == undefined || (queryString.localeCompare("") == 0)) {
            /* Did not find query string so use the streamname as the event id */
            trace("Query string not specified. Using StreamName["
                  +streamObj.name+"] as eventname");
    Now, to accomplish your task, all you need to do is append some marker to this stream name.
    Essentially here:
    var liveEventName = streamObj.name
    I will leave it to you to make use of timestamps, shared objects etc. to keep track of the event name and incerement it for every publish attempt.
    As as example, if you do something like this:
    var liveEventName = streamObj.name + "Test"
    Your event name will be livestreamTest
    I hope this helps in some way.
    Thanks,
    Shiven

  • I downloaded 200  photos, an event folder was created, I could see all the photos and was in the process of editing them when I got a message that iPhoto unexpectedly quit.  I cannot find the photos anywhere on my computer now.  Is there anything to do?

    I downloaded 200  photos, an event folder was created, I could see all the photos and was in the process of editing them when I got a message that iPhoto unexpectedly quit.  I cannot find the photos anywhere on my computer now.  Is there anything to do?

    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. (In Library Manager it's the FIle -> Rebuild command)
    This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. 
    Regards
    TD 

  • Directory Create problem

    Hi,
    I have used the below query for creating a directory
    CREATE OR REPLACE DIRECTORY EXPORT_DIR AS 'D:\SCRIPTS';
    The above query is giving no error while execution but its not creating any directory under D:\
    Any help will be needful

    Hi,
    CREATE DIRECTORY doesn't create any directory in the operating system, only creates an Oracle object related to this directory. You must create the directory and grant the privileges later to the user on the Oracle directory created.
    Regards,

  • Since upgrading to Mountain Lion, I cannot restore emails with time machine. In Lion TM created a folder in Mail called recovered emails(or similar) No such folder is created since ML. I am able to see the email I want to restore, but it then disappears

    Since upgrading to Mountain Lion, I cannot restore emails with time machine. In Lion TM created a folder in Mail called recovered emails(or similar) No such folder is created since ML. I am able to see the email I want to restore, but it then disappears

    I am inside Mail, waiting for the TM 'recovered mail' folder to appear - which it doen't.
    I only looked in my home folder after trying several times from within my Main app.
    Marion

  • Folder directory maps to tree control?

    How can I maps folder directory to tree control? Is it even
    possible? For example:
    I want the tree to show all files and folders under
    "C:\Documents and Settings\User\My Documents". Possible?

    The Flashplayer Sandbox does not allow you to get information
    of you file system directly, but there are severel ways to solve
    the problem.
    1.) you can use webservices which you communicate with (the
    webservice can give you the information and then you have to handle
    the webservice result)
    2.) you can use coldfusion
    3.) You can load a file form your system (with Urlrequest, or
    httpservice) which represents your folder you want to display.
    e.g.: you have a xml-file with all the required information,
    then you parse through the xml-file, the disadvantage is, that you
    always have to update you xml-file manually or with a script

Maybe you are looking for