Thanks for the reply. Perhaps a little more information regarding the
situation would help. I am currently working on a setup/deployment project
that will install our SRS reports on the target machine. I am using the web
service interface to set up the directory structure and deploy reports via
the CreateFolder method. Including the '/' in the CreateFolder call works on
every machine in the organization except my local developer installation.
Furthermore, the MSDN docs do not list the '/' as a reserved character.
However, my SRS installation returns an error listing the '/' as a reserved
character. I would assume this is a bug having to do with my configuration
and was wondering id anyone else had experienced this.
[quoted text, click to view] "Mike Epprecht (SQL MVP)" wrote:
> Hi
>
> Generally, you need to create folders one level at a time.
> folder
> cd folder
> then
> subfolder
> cd subfolder
> then
> anotherfolder
> cd anotherfolder
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program:
http://www.microsoft.com/mvp >
> Blog:
http://www.msmvps.com/epprecht/ >
> "DerrickBrown100" <DerrickBrown100@discussions.microsoft.com> wrote in
> message news:D7B14559-8330-453C-A86D-6E137D2AE287@microsoft.com...
> > When I try and create a folder using the following syntax:
> >
> > folder/subfolder/anotherfolder
> >
> > I get the following error
> > The item name is not valid. Item names cannot contain the following
> > reserved
> > characters ;?:@&=+$,\*<>|"/, and cannot consist exclusively of dots or
> > spaces.
> >
> > When checking the MSDN documentation for the ReportServices CreatFolder I
> > noticed it contains the following comment:
> >
> > Folder names cannot be null, consist of empty strings, or contain the
> > following reserved characters:
> > : ? ; @ & = + $ , \ * > < | . "
> >
> > The difference is the message my ReportServer is giving me includes the
> > '/'
> > character, while the documentaion does not.
> >
> > This is causing a great deal of pain with my deployment scripts and I
> > can't
> > find any information on this issue.
> >
> >
>
>
