Log Import Problem using Reporting Services

Hi,
I am creating a report using MSS and the Microsoft utility
MSSLogToDatabase utility. The utility seems to work great until there
is an attempt to specify a subdirectory for the /reportfolder
parameter.
I have searched far and wide in diverse newsgroups, google, microsoft's
site and etc. but can't seem to get a definitive answer as to whether
or not there is a way to have the report created on the Reporting
Server Website that is contained within another folder.
Documentation is very concise and I can't find any additional
information for using the utility. The description for the
/reportfolder:value switch is "Specifies a name for the target
Reporting Services folder. Optional. If unspecified, Speech Application
Reports is used."
I have tried everything in terms of different methods of designating a
subfolder such as:
/reportfolder:myReportFolder/myReport
/reportfolder:myReportFolder\myReport
/reportfolder:myReportFolder%2fmyReport
Any attempt to create a subdirectory structure on the Reporting Server
has either failed altogether with this excerpt error:
Failed to create folder for reports on the specified SQL Reporting
Services host:
The name of the item 'myReportFolder/my
Report is not valid. The name must be less than 260 characters long,
must not start with slash; other restrictions apply. Check the
documentation for complete set of restrictions.
Or it creates a single folder on the homepage with a name like,
myReportFolder%2fmyReport.
Unfortunately, I have suspicion that the error is very vague and a bit
too generic to indicate the actual cause of failure since complying
with the character restraints still doesn't produce the subdirectory
structure.
I have even explored the data structure and layout for the webcontent
in the catalogs table of the Reports database to hopefully find a clue
but to no satisfactory resolve.
In a nutshell, there is only one of 2 answers for this problem.
1. The utility is limited in this capacity and since there isn't any
method of resolving or working around the problem to get the desired
results.
2. The utility is capable of performing the requested action, but the
documentation is very poor when it comes to more elaborative
descriptions of its features.
If it is the latter of the 2 and someone can provide a viable
workaround or answer, that would be great!!!!
Thanks,
MarkWish that I could help.. I've got some reports that have paths that are
~100 characters; etc and they are coughing on this same error message;
but it's not specific to MSSLogToDatabase utility
I had heard it's a bug with a bad error description; I wish I could
find the resolution.
Does anyone know which characters we're allowed to use in a report
title'
-Aaron
mivey4 wrote:
> Hi,
> I am creating a report using MSS and the Microsoft utility
> MSSLogToDatabase utility. The utility seems to work great until there
> is an attempt to specify a subdirectory for the /reportfolder
> parameter.
> I have searched far and wide in diverse newsgroups, google, microsoft's
> site and etc. but can't seem to get a definitive answer as to whether
> or not there is a way to have the report created on the Reporting
> Server Website that is contained within another folder.
> Documentation is very concise and I can't find any additional
> information for using the utility. The description for the
> /reportfolder:value switch is "Specifies a name for the target
> Reporting Services folder. Optional. If unspecified, Speech Application
> Reports is used."
> I have tried everything in terms of different methods of designating a
> subfolder such as:
> /reportfolder:myReportFolder/myReport
> /reportfolder:myReportFolder\myReport
> /reportfolder:myReportFolder%2fmyReport
> Any attempt to create a subdirectory structure on the Reporting Server
> has either failed altogether with this excerpt error:
> Failed to create folder for reports on the specified SQL Reporting
> Services host:
> The name of the item 'myReportFolder/my
> Report is not valid. The name must be less than 260 characters long,
> must not start with slash; other restrictions apply. Check the
> documentation for complete set of restrictions.
> Or it creates a single folder on the homepage with a name like,
> myReportFolder%2fmyReport.
> Unfortunately, I have suspicion that the error is very vague and a bit
> too generic to indicate the actual cause of failure since complying
> with the character restraints still doesn't produce the subdirectory
> structure.
> I have even explored the data structure and layout for the webcontent
> in the catalogs table of the Reports database to hopefully find a clue
> but to no satisfactory resolve.
> In a nutshell, there is only one of 2 answers for this problem.
> 1. The utility is limited in this capacity and since there isn't any
> method of resolving or working around the problem to get the desired
> results.
> 2. The utility is capable of performing the requested action, but the
> documentation is very poor when it comes to more elaborative
> descriptions of its features.
> If it is the latter of the 2 and someone can provide a viable
> workaround or answer, that would be great!!!!
> Thanks,
> Mark|||Hi Aaron,
I may be able to provide some assistance to you concerning your
inquiry.
I have found that the following set of rules apply to virtually any
path designated within MSS because it is based on a web-based platform:
A. The full name of the item (including the path) cannot exceed 260
characters.
B. Names cannot be null, consist of any empty string
C. Names cannot include any of these reserved characters: (for URL
paths)
: ? ; @. ' = + $ , \ * > < | . " : =D. You cannot end an item name with a backslash character.
Although my issue was a bit different the same sets of rules still
applied because I was attempting to specify a path to the report via
the use of \.
When I attempted to use / I believe the error was thrown simply because
the tool was limited to creating a directory structure in the root only
in addition to the fact that the / was probably reserved as a switch
parameter at the command line from which the utility was run as well,
because the / wasn't an invalid URL character.
As far as naming your reports goes, there aren't any restrictions that
I am aware of that would potentially prohibit you from naming your
reports whatever you desire. I proved this by enclosing the report name
in double quotes which explicitly designate every character within the
quotes as being a literal string. e.g. "Reports/myReports" and
"Reports\myReports".
The problem was by doing so, the intended path was interpreted as a
literal string and not as the path. I was then left with a Report
called Reports/myReports.
I couldn't resolve the problem since it was apparently not a problem
but a mere limitation of the utility. I did confirm that short of this
issue, the operation didn't totally crash but continued gracefully with
the remaining tasks.
I hope I have helped clear up some of your questions. If not, e-mail me
and I'll assist in anyway I can.
Thanks!
Mark
aaron.kempf@.gmail.com wrote:
> Wish that I could help.. I've got some reports that have paths that are
> ~100 characters; etc and they are coughing on this same error message;
> but it's not specific to MSSLogToDatabase utility
> I had heard it's a bug with a bad error description; I wish I could
> find the resolution.
> Does anyone know which characters we're allowed to use in a report
> title'
> -Aaron
>
> mivey4 wrote:
> > Hi,
> >
> > I am creating a report using MSS and the Microsoft utility
> > MSSLogToDatabase utility. The utility seems to work great until there
> > is an attempt to specify a subdirectory for the /reportfolder
> > parameter.
> >
> > I have searched far and wide in diverse newsgroups, google, microsoft's
> > site and etc. but can't seem to get a definitive answer as to whether
> > or not there is a way to have the report created on the Reporting
> > Server Website that is contained within another folder.
> >
> > Documentation is very concise and I can't find any additional
> > information for using the utility. The description for the
> > /reportfolder:value switch is "Specifies a name for the target
> > Reporting Services folder. Optional. If unspecified, Speech Application
> > Reports is used."
> >
> > I have tried everything in terms of different methods of designating a
> > subfolder such as:
> > /reportfolder:myReportFolder/myReport
> > /reportfolder:myReportFolder\myReport
> > /reportfolder:myReportFolder%2fmyReport
> >
> > Any attempt to create a subdirectory structure on the Reporting Server
> > has either failed altogether with this excerpt error:
> > Failed to create folder for reports on the specified SQL Reporting
> > Services host:
> >
> > The name of the item 'myReportFolder/my
> > Report is not valid. The name must be less than 260 characters long,
> > must not start with slash; other restrictions apply. Check the
> > documentation for complete set of restrictions.
> >
> > Or it creates a single folder on the homepage with a name like,
> > myReportFolder%2fmyReport.
> >
> > Unfortunately, I have suspicion that the error is very vague and a bit
> > too generic to indicate the actual cause of failure since complying
> > with the character restraints still doesn't produce the subdirectory
> > structure.
> >
> > I have even explored the data structure and layout for the webcontent
> > in the catalogs table of the Reports database to hopefully find a clue
> > but to no satisfactory resolve.
> >
> > In a nutshell, there is only one of 2 answers for this problem.
> >
> > 1. The utility is limited in this capacity and since there isn't any
> > method of resolving or working around the problem to get the desired
> > results.
> > 2. The utility is capable of performing the requested action, but the
> > documentation is very poor when it comes to more elaborative
> > descriptions of its features.
> >
> > If it is the latter of the 2 and someone can provide a viable
> > workaround or answer, that would be great!!!!
> >
> > Thanks,
> > Mark|||lol it was actually a SPACE
filename_.rdl with the underscore representing a SPACE
dont know how I missed it; seems like it should have automatically
fixed itself; but i found it; fixed a half dozen reports with minimal
effort
-Aaron
mivey4 wrote:
> Hi Aaron,
> I may be able to provide some assistance to you concerning your
> inquiry.
> I have found that the following set of rules apply to virtually any
> path designated within MSS because it is based on a web-based platform:
> A. The full name of the item (including the path) cannot exceed 260
> characters.
> B. Names cannot be null, consist of any empty string
> C. Names cannot include any of these reserved characters: (for URL
> paths)
> : ? ; @. ' = + $ , \ * > < | . " : => D. You cannot end an item name with a backslash character.
> Although my issue was a bit different the same sets of rules still
> applied because I was attempting to specify a path to the report via
> the use of \.
> When I attempted to use / I believe the error was thrown simply because
> the tool was limited to creating a directory structure in the root only
> in addition to the fact that the / was probably reserved as a switch
> parameter at the command line from which the utility was run as well,
> because the / wasn't an invalid URL character.
> As far as naming your reports goes, there aren't any restrictions that
> I am aware of that would potentially prohibit you from naming your
> reports whatever you desire. I proved this by enclosing the report name
> in double quotes which explicitly designate every character within the
> quotes as being a literal string. e.g. "Reports/myReports" and
> "Reports\myReports".
> The problem was by doing so, the intended path was interpreted as a
> literal string and not as the path. I was then left with a Report
> called Reports/myReports.
> I couldn't resolve the problem since it was apparently not a problem
> but a mere limitation of the utility. I did confirm that short of this
> issue, the operation didn't totally crash but continued gracefully with
> the remaining tasks.
> I hope I have helped clear up some of your questions. If not, e-mail me
> and I'll assist in anyway I can.
> Thanks!
> Mark
>
> aaron.kempf@.gmail.com wrote:
> > Wish that I could help.. I've got some reports that have paths that are
> > ~100 characters; etc and they are coughing on this same error message;
> > but it's not specific to MSSLogToDatabase utility
> >
> > I had heard it's a bug with a bad error description; I wish I could
> > find the resolution.
> >
> > Does anyone know which characters we're allowed to use in a report
> > title'
> >
> > -Aaron
> >
> >
> >
> > mivey4 wrote:
> > > Hi,
> > >
> > > I am creating a report using MSS and the Microsoft utility
> > > MSSLogToDatabase utility. The utility seems to work great until there
> > > is an attempt to specify a subdirectory for the /reportfolder
> > > parameter.
> > >
> > > I have searched far and wide in diverse newsgroups, google, microsoft's
> > > site and etc. but can't seem to get a definitive answer as to whether
> > > or not there is a way to have the report created on the Reporting
> > > Server Website that is contained within another folder.
> > >
> > > Documentation is very concise and I can't find any additional
> > > information for using the utility. The description for the
> > > /reportfolder:value switch is "Specifies a name for the target
> > > Reporting Services folder. Optional. If unspecified, Speech Application
> > > Reports is used."
> > >
> > > I have tried everything in terms of different methods of designating a
> > > subfolder such as:
> > > /reportfolder:myReportFolder/myReport
> > > /reportfolder:myReportFolder\myReport
> > > /reportfolder:myReportFolder%2fmyReport
> > >
> > > Any attempt to create a subdirectory structure on the Reporting Server
> > > has either failed altogether with this excerpt error:
> > > Failed to create folder for reports on the specified SQL Reporting
> > > Services host:
> > >
> > > The name of the item 'myReportFolder/my
> > > Report is not valid. The name must be less than 260 characters long,
> > > must not start with slash; other restrictions apply. Check the
> > > documentation for complete set of restrictions.
> > >
> > > Or it creates a single folder on the homepage with a name like,
> > > myReportFolder%2fmyReport.
> > >
> > > Unfortunately, I have suspicion that the error is very vague and a bit
> > > too generic to indicate the actual cause of failure since complying
> > > with the character restraints still doesn't produce the subdirectory
> > > structure.
> > >
> > > I have even explored the data structure and layout for the webcontent
> > > in the catalogs table of the Reports database to hopefully find a clue
> > > but to no satisfactory resolve.
> > >
> > > In a nutshell, there is only one of 2 answers for this problem.
> > >
> > > 1. The utility is limited in this capacity and since there isn't any
> > > method of resolving or working around the problem to get the desired
> > > results.
> > > 2. The utility is capable of performing the requested action, but the
> > > documentation is very poor when it comes to more elaborative
> > > descriptions of its features.
> > >
> > > If it is the latter of the 2 and someone can provide a viable
> > > workaround or answer, that would be great!!!!
> > >
> > > Thanks,
> > > Mark