Report painter - Default set 010100010001-1 does not exist

Dear Experts,
I have created a report in report painter and I transported (report, report group, variables) thru transport request.  while importing into Quality system  i was getting errror"Library 1VK: Default set 010100010001-1 does not exist".   Then i kept 1 VK library in transport then i moved to Quality system  now all standard report are not working properly.
Please advise.
Thanks
Balu

Hi Thanks for your reply
Earlier i was getting the following error when i was importing  transpor request (report, report group, variables)
1)"Library 1VK: Default set 010100010001-1 does not exist. "
2)Errors occurred during post-handling G_RW_AFTER_IMPORT for GRW_JOB T
3)The errors affect the following componenets:
4)FI-SL-IS (Information System)
Then I transported 1VK library also (without selection list option) now my standard reports are not working properly
Please advise.
Thanks
Balu

Similar Messages

  • SCCM 2012 R2 - Reporting Services Point installation - "The Datasource does not exist"

    Hi all,
    Quick bit of background, we have SCCM 2012 R2 installed on a Windows 2012 R2 server. We have the SQL back end off box, configured on a SQL 2012 R2 server running on a Windows Server 2012 R2 cluster. Then there is yet another server which runs the reporting
    services. I've just tried installing the Reporting Services Point on the srs server but it doesn't appear to have worked that well. Here's the info i've got back: 
    A] Site Status > Reporting services point:
    SMS_SITE_SYSTEM_STATUS_SUMMERIZER
    Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\NA-SQLR01.in.tna.local" has changed to Failed.
    B] The last message from the SMS_SRS_REPORTING_POINT Component Status is "Site Component Manager successfully installed this component on this site system"
    C] Here's the first chunk of info which appears in the srsrp.log file:
    SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 4204 (0x106C).
    This is a SRS Reporting Point Role as SRSRP registry key exists.
    Waiting for changes for 0 minutes
    Timed Out...
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver SMS_
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlserver.local\SQL1] [SCCM_XXX] [ConfigMgr_XXX] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [xxx\SCCM2012Server]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    STATMSG: ID=7405 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=sqlreportserver.LOCAL SITE=P01 PID=2120 TID=4204 GMTDATE=Wed Apr 08 08:56:05.349 2015 ISTR0="ConfigMgr_XXX" ISTR1="sqlreportserver.LOCAL"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    After this point i simply get the following info messages looping endlessly:
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlreportserverlocal\SQL1] [SCCM_XXX] [ConfigMgr_P01] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [XX\SCCM2012Server]
    [1] [0]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_P01' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    Has anyone come across this issue before? Must admit, I'm not too hot on the sql side of things so any advice or suggestions would be greatly appreciated. Thanks in advance!

    Hi guys, cheers for the swift response.
    Garth, i can access SSRS in IE from the SCCM box and it looks a-ok.
    Paul, nope can't say I've done any configuration of reporting services - the whole thing has been set up by the database team. Having had a trundle through Reporting Services Configuration Manager, it seems the Database team have set up SSRS in line with
    the walkthrough you posted.
    Since i'm not seeing the ConfigMgr_XXX folder appear in SSRS I'm wondering if there's something preventing SCCM from being able to create it. The message
    "Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions
    granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation" sounds like the account SCCM is leveraging to perform the install might not have the right permissions in SSRS. Do i need to delegate specific rights to the NT
    AUTHORITY\SYSTEM account in SRS perhaps?

  • Default Target Main Build does not exist in this project

    I am learning ant with eclipse and wanted to use ant build.xml to compile and run my class. I was getting the following error when i just tried to use ant.
    Default Target Main Build does not exist in this project
    package src;
    public class Ch05_02 {
        public static void main(String[] args) {
            System.out.println("This code was built using Ant.");
    <?xml version="1.0" encoding = "UTF-8"?>
    <project name="Ch05_02" default="Main Build" basedir=".">
    </project>Ref: http://www.javabeginner.com/Ch05_02.zip
    Edited by: hemanthjava on Oct 28, 2007 5:43 AM

    You gave a default target in the build.xml, and then didn't define the target.
    This is an Ant question. You're better off asking Ant questions on an Ant forum.

  • Set type COMM_PR_UNIT does not exist

    Hi All
    How do i make set types available for assignment to categories if they are not available but are there in comm_settype. Getting errors as follows: Set type COMM_PR_UNIT does not exist.
    Please assist
    Regards,
    Patrick
    Edited by: Patrick Chidarara on Jul 22, 2008 10:14 AM

    Hi Patrick,
    Please see OSS note Note 966072 - Download of material fails - set type COMM_PR_UNIT
    Regards,Nishant

  • MBAM - SCCM 2012 Reports - Error: the 'MBAM Policy' view does not exist

    Hi
    I have installed MBAM with SCCM 2012 integration. A single server install with SQL server 2012. Mostly it has gone smoothly and laptops are being encrypted and pins stored and recoverable. The problem I have is reports are not showing. I get the following
    error message.
    "Error: the 'MBAM Policy' view does not exist"
    Any ideas why this is? I get the same error message with all 4 reports.

    Hi Slycy,
    There is another thread that seems to be a similar issue
    here that may help you. The last post in particular has a number of steps that you can use to speed up creation of the views:
    Just for future reference, there are quite a few things that have to happen before the view is created. This is merely how CM works.
    Make MBAM MOF changes
    Select TPM spec version in hardware inventory
    Install MBAM CM Integration feature
    Perform a machine policy refresh cycle on a client to get the MOF changes that need to be inventoried
    Perform hardware inventory
    Update MBAM Supported Computers collection membership.  The machine should appear if it meets the criteria
    Run another machine policy refresh on the client so that the Configuration Baseline will come down
    Make sure that the MBAM agent has woken up once
    Evaluate the Configuration Baseline
    The MBAM views should be created now.
    You don't have to do this for every machine, but this is the process to speed it up.  If you let CM do it, it could take over a week before the view is created the first time, depending on when Hardware inventory runs, etc.
    Hope this helps,
    David

  • Release strategy: Tx CL20N Error: Entry 01 does not exist in table T16FS

    Dear MM Gurus,
    I was designing new release strategy for PR and PO, so I deleted all the previous entries(SPRO) available in SAP. I created my new entries but in the transaction CL20N I got the above mentioned error: "Entry 01 does not exist in table T16FS-Check your entry" . I checked the table T16FS, where the entries were available. It also showed the previous entries I deleted from SPRO.
    Refering the SAP note 365604 (version 29, valid from 08.10.2008), I created the deleted entries again so that I could delete them in the required sequence
    1. release strategies
    2. release indicators
    3. release codes
    4. release groups
    5. class
    After deleting the entries in the above mentioned sequence also I am getting the same error in CL20N.
    I ran report RCCLZUOB, it shows the entries does not exist.
    Please help.
    Edited by: Akshay Kurhe on Mar 2, 2009 6:02 AM

    hi
    check this setting
    Distribution Using Object Classes -->Maintain Class Types & Maintain Classes

  • SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

    I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
    As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
    FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
    However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
    In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
    1/ The major number for IDE based drives is 3.
    2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
    3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
    4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
    In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
    - The major number is 8.
    - The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
    Armed with this knowledge, I su'd to root and entered:
    # mknod /dev/sdc4 b 8 36
    and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
    SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
    Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
    # ls -ald /dev/sd*
    Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
    brw-rw----  1  root  disk  8,   32   date   time   /dev/sdc
    Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
    Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

    Solved!
    See the lengthy response in this post:
    http://bbs.archlinux.org/viewtopic.php?id=36468
    I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

  • Report Painter Characteristic Ledger does not exist

    Hi Experts,
    I am trying to create a report GRR1 and for Plan Budget Report in Rows i have given SALES, REVENUE,COST and TOTAL and when i have defined the Columns with period 1,2,3,4,5,6..12 I got the following message when executing the Report.
    Characteristic Ledger does not exist and  Characteristic Record Type does not exist
    Characteristic Ledger does not exist
    Message no. GR655
    Diagnosis
    The characteristic must (message type E) or should (message type W) be addressed in the report definition. This means that a set must/should exist for the characteristic in the definition of the report rows, report columns, or report selection.
    For performance reasons, it is important that you limit the value ranges of those key fields located at the start of the database key as much as possible.
    Procedure
    Define a set for this characteristic in the report.
    Note
    In Controlling (Table CCSS), different characteristics (cost center, order, project, etc.) are portrayed internally with a common technical characteristic, "Object". In reports, either a specific characteristic such as cost center must be used, or the characteristic "Object" must be used directly. If this is not the case, an error message appears saying that the "Object" characteristic is missing.
    Also i would like to know how do i define the selection criteria for executing the report
    Please advice a solution for the same
    Regards
    Rahul

    The reason could be having (1)  invalid characteristics value or (2) have not properly defined the General Data Section, most likely (1) in this case.
    Either way, go to t-code GRR2 to change the report.
    In the report row or column, is there an Element (the labels in red color) that does not make sense?
    It could still have the correct label names, but double-click and go into "Record Types (from your error message)".  Be sure to have the correctly define values attached to each Characteristics.
    If all above seems okay, try (From top bar, select) Edit --> General Data Section.  Think of this section as the "header data" of the report.
    Good luck
    AY

  • Report painter report does not exist after applying support pack

    Hi,
    I have created report with the help of report painter for FI.
    Also created transaction code for the same.
    After applying the support pack, while testing I got the error that
    program in the transaction code does not exists.
    How to search that program and where or I need to create the same program again?
    Thanx in advance.
    -Umesh

    The reason could be having (1)  invalid characteristics value or (2) have not properly defined the General Data Section, most likely (1) in this case.
    Either way, go to t-code GRR2 to change the report.
    In the report row or column, is there an Element (the labels in red color) that does not make sense?
    It could still have the correct label names, but double-click and go into "Record Types (from your error message)".  Be sure to have the correctly define values attached to each Characteristics.
    If all above seems okay, try (From top bar, select) Edit --> General Data Section.  Think of this section as the "header data" of the report.
    Good luck
    AY

  • MS ssis service: registry setting specifying configuration file does not exist. attempting to load default configuration file. SQLIService100 - event id 274

    window 2008 R2 server ---- after installing SQL 2008 R2 then applying sp2 / sp3 I noted a warning -
    Note this server had SQL 2008 R2 uninstalled previously.
    MS ssis service: registry setting specifying configuration file does not exist. attempting to load default configuration file.
    SQLIService100 - source
    event id- 274
    user - N/A
    Task category - service control.
    Do we need to fix something and how do we fix this warning event?
    dsk

    You could search online for this warning. I was able to find http://superuser.com/questions/346264/event-log-warning-registry-setting-specifying-configuration-file-does-not-exist
    where the fix is "in your registry, go to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile
    or
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ServiceConfigFile
    if value is empty then add in:
    C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.ini.xml"
    Arthur
    MyBlog
    Twitter

  • Report painter execution error - KH014  "Report does not exist".

    Hi All,
    I customized one report in FSI3 and used SE43 to create a t code for this report. In the development system, report will be executable from this t code.
    Transport requests are successfully transported from development to production without any error. But on production when I tried to execute the report, I am getting the error KH014 - "Report does not exist".
    While checking in production I found that the report was missing from report tree in FSI3 and as a result the customized report cannot be executed. As per basis guys there was not a issue in request transportation.
    Has anyone encountered similar problem? How was it resolved?
    Thanks.
    Prashant

    Hi Mikko,
    Thanks for your reply but your solution is not working.
    Hi Stacy,
    I can execute the report from t codes like FSI3 & FSI0 in development.
    I used SE43 for t code creation. At the time of t code creation there is a option called "Drilldown" under Report type heading, In drilldown option I selected my report from report type 002 (Financial Statement Key Figure) and created the t code. After this I transported both the request to production server.
    Please let me know if this is wrong method or there is any other option to transport this report in Production.
    Thanks & Regards,
    Prashant

  • SSMA for Oracle 6.0 Cannot connect to Oracle DB reporting "table or view does not exist"

    SSMA For Oracle v6.0.0
    MS SQL Server Enterprise 64bits v11.0.3000.0
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Symptom:
    when connecting Oracle, it reports error "Common Requirement: User does not have required permissions". Then it reports error: "Error occurred while collecting data."
    The following is log:
    [Generic: Mandatory] [1500/1] [2015-03-03 04:19:29]: SQL Server Migration Assistant for Oracle v6.0.0
    [Generic: Mandatory] [1500/1] [2015-03-03 04:19:29]: Starting assembly: SSMAforOracle, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Created: 7/22/2014 4:42:22 PM
    Last Modified: 7/22/2014 4:42:22 PM
    OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1
    OS architecture: x64
    Processor architecture: AMD64
    Current culture: en-US
    UI culture: en-US
    [Collector: Mandatory] [1500/4] [2015-03-03 04:20:04]: Oracle connection provider: OracleClient.
    [Collector: Mandatory] [1500/4] [2015-03-03 04:20:04]: Oracle connection mode: Standard.
    [Collector: Mandatory] [1500/4] [2015-03-03 04:20:06]: Oracle server version: '11.2.0.3.0'.
    [Gui: Error] [1500/4] [2015-03-03 04:20:12]: LowLevelAdapter.ReadSource : Read Source error: Microsoft.SSMA.Framework.Generic.Collectors.CollectorException: Error occurred while collecting data. ---> System.Data.OracleClient.OracleException: ORA-00942: table
    or view does not exist
       at System.Data.OracleClient.OracleConnection.CheckError(OciErrorHandle errorHandle, Int32 rc)
       at System.Data.OracleClient.OracleCommand.Execute(OciStatementHandle statementHandle, CommandBehavior behavior, Boolean needRowid, OciRowidDescriptor& rowidDescriptor, ArrayList& resultParameterOrdinals)
       at System.Data.OracleClient.OracleCommand.ExecuteScalarInternal(Boolean needCLStype, Boolean needRowid, OciRowidDescriptor& rowidDescriptor)
       at System.Data.OracleClient.OracleCommand.ExecuteScalar()
       at Microsoft.SSMA.Framework.Generic.DbUtilities.SsmaDbCommand.ExecuteScalar()
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.ExecuteScalarToInt(IDbConnection connection, String text)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.GetCountForExcludedSchemas(IDbConnection connection, IEnumerable`1 excludedSchemas, Int64 version)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CountObjects(IDbConnection connection, Int64 serverVersion, OracleCollectionFilter filter, Set`1 excludedSchemas)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CollectDataIntoMetabase(XMetabase xMetabase, IDbConnection connection, Int64 serverVersion, OracleCollectionFilter filter, IUIProgressBarProvider progressBarProvider, IUIStopOperationProvider
    stopOperationProvider, ICollectionContext context)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CreateMetabaseAndCollectData(IDbConnection connection, String xmlConnectionParameters, XNode xFilter, IUIProgressBarProvider progressBarProvider, IUIStopOperationProvider stopOperationProvider,
    ICollectionContext context)
       --- End of inner exception stack trace ---
       at Microsoft.SSMA.Framework.Generic.Workspaces.Default.MetabaseWorkspaceItem.Connect(String connectionParameters, SecureString password)
       at Microsoft.SSMA.GUI.Product.OracleToMsSql.LowLevel.AppConnectToSourceOracle.ConnectToSourceStart(Object guiContext)
    [Gui: Error] [1500/4] [2015-03-03 04:20:12]: Exception: Error occurred while collecting data.
     site: Void Connect(System.String, System.Security.SecureString)
     source: Microsoft.SSMA.Framework.Generic.SSMAEnvironment
       at Microsoft.SSMA.Framework.Generic.Workspaces.Default.MetabaseWorkspaceItem.Connect(String connectionParameters, SecureString password)
       at Microsoft.SSMA.GUI.Product.OracleToMsSql.LowLevel.AppConnectToSourceOracle.ConnectToSourceStart(Object guiContext)
    [Gui: Error] [1500/4] [2015-03-03 04:20:12]: Inner Exception #1: ORA-00942: table or view does not exist
     site: Void CheckError(System.Data.OracleClient.OciErrorHandle, Int32)
     source: System.Data.OracleClient
     error code: -2146232008
       at System.Data.OracleClient.OracleConnection.CheckError(OciErrorHandle errorHandle, Int32 rc)
       at System.Data.OracleClient.OracleCommand.Execute(OciStatementHandle statementHandle, CommandBehavior behavior, Boolean needRowid, OciRowidDescriptor& rowidDescriptor, ArrayList& resultParameterOrdinals)
       at System.Data.OracleClient.OracleCommand.ExecuteScalarInternal(Boolean needCLStype, Boolean needRowid, OciRowidDescriptor& rowidDescriptor)
       at System.Data.OracleClient.OracleCommand.ExecuteScalar()
       at Microsoft.SSMA.Framework.Generic.DbUtilities.SsmaDbCommand.ExecuteScalar()
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.ExecuteScalarToInt(IDbConnection connection, String text)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.GetCountForExcludedSchemas(IDbConnection connection, IEnumerable`1 excludedSchemas, Int64 version)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CountObjects(IDbConnection connection, Int64 serverVersion, OracleCollectionFilter filter, Set`1 excludedSchemas)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CollectDataIntoMetabase(XMetabase xMetabase, IDbConnection connection, Int64 serverVersion, OracleCollectionFilter filter, IUIProgressBarProvider progressBarProvider, IUIStopOperationProvider
    stopOperationProvider, ICollectionContext context)
       at Microsoft.SSMA.Framework.Oracle.Collector.OracleObjectCollector.CreateMetabaseAndCollectData(IDbConnection connection, String xmlConnectionParameters, XNode xFilter, IUIProgressBarProvider progressBarProvider, IUIStopOperationProvider stopOperationProvider,
    ICollectionContext context)

    Hi Airings,
    'ORA-00942: table or view does not exist'
    According to the error message, it seems that the migrating table or view does not exist in the database, or SSMA does not have access to it. To troubleshoot the issue, please check the following things.
     1. Verify that if the spelling of the table or view name is correct.
     2. If the table or view exists but is in a different schema from the current schema where the SQL is executing (in other word, the table doesn’t own by you, but owned by other user), the ORA-00942 error will return too. Resolve this by
    explicitly reference the table or view by specifying the schema name (schema_name.table_name).
    3. SSMA queries some additional catalog tables that you may not have permission to, please make sure that you grant the account permission to
     read sys.mlog$. For more details, please review this similar thread:
    Bug in SSMA For Oracle 6.0 for non-dba Oracle user.
    Reference:
    ORA-00942 Table or View Does Not Exist Oracle Error
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SCCM 2012 R2 reporting error: "The DefaultValue expression for the report parameter 'UserTokenSIDs' contains an error: A specified logon session does not exist. It may already have been terminated. (rsRuntimeErrorInExpression)"

    Hi,
    I have two SCCM environments under same active directory domain and one service account have been used for SCCM configurations on both the environments (QA and PRODUCTION). I am facing similar error as mentioned above while trying to fetch reports on
    PRODUCTION site, but the QA site is working fine, though same service account have been used for configuring both. While looking at the reportserverservice_<date> log on my Production DB server i see the following error
    "processing!ReportServer_0-3!2124!01/02/2015-09:09:30:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: , Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during
    report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot read the next data row for the dataset DataSet1. ---> System.Data.SqlClient.SqlException: Conversion failed when converting the nvarchar value 'Override
    Default' to data type int."
    My DB and SCCM primary site are different and the reorting services point is installed on remote DB server. Please help me resolving the issue.
    Troubleshooting performed:
    1.Disabled the registry key 'EnableRbacReporting' from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SRSRP to 0 and then restarted SSRS service and the reporting worked for some minutes after that the registry key reverted back to 1 automatically and
    reporting started throwing errors again.
    2. Checked with the permissions on DB whether or not 'sysadmin' role is assigned to the SCCM service account.
    3. re-registered the SQL management Provider WMI class.
    mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof”

    Hi All,
    Finally found exact solution to the reporting error.
    Error: while launching SCCM reports (both from Console and web based) an unexpected error occured with error message as "The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: A specified logon session does not exist.
    It may already have been terminated. (rsRuntimeErrorInExpression)"
    Solution: This is password replication issue for the domain account used to configure reporting services point in SCCM. If your SQL SSRS reporting services instance and databse runs with local default account whereas the reporting services point on SCCM
    primary site is configured with domain account, (As in My case) you need to perform the following in order to get rid of the error.
    Launch 'Reporting Services Configuration Manager' from the SQL SSRS box(either Local or Remote), Connect to Report Server Instance->Go to 'Execution Account' tab->Specify the 'Execution Account' as domain account and password which is used to configure
    Reporting Services Point in SCCM Primary Site, and then click apply.
    Now Lauch the report either way (Web based or from Console), the error will disappear and all your default reports will execute perfectly as before.

  • Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

    Hi ALl,
    I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
    Contents of summary log:
    Overall summary:
       Final result:                  Failed: see details below
       Exit code (Decimal):           -2068578304
       Exit facility code:            1204
       Exit error code:               0
       Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
    exist.
       Start time:                    2015-01-09 10:19:12
       End time:                      2015-01-09 10:20:07
       Requested action:              Install
    Setup completed with required actions for features.
     Troubleshooting information for those features:
       Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
       Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
     Machine Properties:
       Machine name:                  IDCSQLTST11
       Machine processor count:       2
       OS version:                    Future Windows Version
       OS service pack:              
       OS region:                     United States
       OS language:                   English (United States)
       OS architecture:               x64
       Process architecture:          64 Bit
       OS clustered:                  No
    Product features discovered:
       Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Package properties:
       Description:                   Microsoft SQL Server 2012
       ProductName:                   SQL Server 2012
       Type:                          RTM
       Version:                       11
       SPLevel:                       0
       Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
       Installation edition:          Standard
    Product Update Status:
       None discovered.
    User Input Settings:
       ACTION:                        Install
       ADDCURRENTUSERASSQLADMIN:      false
       AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
       AGTSVCPASSWORD:                <empty>
       AGTSVCSTARTUPTYPE:             Automatic
       ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
       ASCOLLATION:                   Latin1_General_CI_AS
       ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
       ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
       ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
       ASPROVIDERMSOLAP:              1
       ASSERVERMODE:                  MULTIDIMENSIONAL
       ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
       ASSVCPASSWORD:                 <empty>
       ASSVCSTARTUPTYPE:              Manual
       ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
       ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
       BROWSERSVCSTARTUPTYPE:         Disabled
       CLTCTLRNAME:                  
       CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
       CLTSTARTUPTYPE:                Manual
       CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
       CLTSVCPASSWORD:                <empty>
       CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
       COMMFABRICENCRYPTION:          0
       COMMFABRICNETWORKLEVEL:        0
       COMMFABRICPORT:                0
       CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
       CTLRSTARTUPTYPE:               Manual
       CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
       CTLRSVCPASSWORD:               <empty>
       CTLRUSERS:                     DOMAINAA\user12345
       ENABLERANU:                    false
       ENU:                           true
       ERRORREPORTING:                false
       FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
    DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
       FILESTREAMLEVEL:               0
       FILESTREAMSHARENAME:           <empty>
       FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
       FTSVCPASSWORD:                 <empty>
       HELP:                          false
       INDICATEPROGRESS:              false
       INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
       INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
       INSTALLSQLDATADIR:             <empty>
       INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
       INSTANCEID:                    MSSQLSERVER
       INSTANCENAME:                  MSSQLSERVER
       ISSVCACCOUNT:                  NT Service\MsDtsServer110
       ISSVCPASSWORD:                 <empty>
       ISSVCSTARTUPTYPE:              Automatic
       MATRIXCMBRICKCOMMPORT:         0
       MATRIXCMSERVERNAME:            <empty>
       MATRIXNAME:                    <empty>
       NPENABLED:                     0
       PID:                           *****
       QUIET:                         true
       QUIETSIMPLE:                   false
       ROLE:                         
       RSINSTALLMODE:                 DefaultNativeMode
       RSSHPINSTALLMODE:              SharePointFilesOnlyMode
       RSSVCACCOUNT:                  NT Service\ReportServer
       RSSVCPASSWORD:                 <empty>
       RSSVCSTARTUPTYPE:              Manual
       SAPWD:                         <empty>
       SECURITYMODE:                  SQL
       SQLBACKUPDIR:                  <empty>
       SQLCOLLATION:                  Latin1_General_CI_AS
       SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
       SQLSVCPASSWORD:                <empty>
       SQLSVCSTARTUPTYPE:             Automatic
       SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
       SQLTEMPDBDIR:                  F:\TempDB
       SQLTEMPDBLOGDIR:               <empty>
       SQLUSERDBDIR:                  E:\SQLData
       SQLUSERDBLOGDIR:               D:\SQLLog
       SQMREPORTING:                  false
       TCPENABLED:                    1
       UIMODE:                        Normal
       UpdateEnabled:                 true
       UpdateSource:                  MU
       X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
    Detailed results:
       Feature:                       Database Engine Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Replication
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Analysis Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - Native
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services - SharePoint
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Reporting Services Add-in for SharePoint Products
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Data Quality Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Integration Services
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Complete
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Controller
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Distributed Replay Client
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Server Data Tools
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Management Tools - Basic
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Client Connectivity SDK
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Writer
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       Documentation Components
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
      Feature:                       SQL Browser
       Status:                        Failed: see logs for details
       Reason for failure:            Setup was canceled for the feature.
       Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
    Exception summary:
     The following is an exception stack listing the exceptions in outermost to innermost order
     Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
         Message:
             The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x84b40000
             FacilityCode : 1204 (4b4)
             ErrorCode : 0 (0000)
         Data:
           SQL.Setup.FailureCategory = InputSettingValidationFailure
           DisableWatson = true
         Stack:
             at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
             at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
             at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
             at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
         Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
             Message:
                     The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
             HResult : 0x87d00006
                     FacilityCode : 2000 (7d0)
                     ErrorCode : 6 (0006)
             Data:
               DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
               SettingName = CLTRESULTDIR
               WatsonData = 
    Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

    Hello,
    Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
    means each parameter:
    http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
    You will also find the list of features supported by each edition on the following article:
    http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
    For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com
    Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
    would Microsoft tease you like that? Frustrating since I spent hours on this ..

  • Reporting using SSRS not working - logon session does not exist

    Hello All,
    After installing the 'reporting site system role' and configuring (using MS technet reference guides), I see the report folder under my Monitoring-> reporting->reports folder;
    When I click on a report and 'run', I get the following error:
    "the default value expression for the report parameter 'usertokenSIDs' contains an error. A specified logon session does not exist. It may already have been terminated"
    details:
    System.Web.Services.Protocols.SoapException: The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: A specified logon session does not exist. It may already have been terminated.
       at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ParameterInfoCollection& Parameters)
       at Microsoft.ReportingServices.WebServer.ReportingService2005.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ReportParameter[]& Parameters)
    Microsoft.ConfigurationManagement.ManagementProvider.SmsException
    The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: A specified logon session does not exist. It may already have been terminated.
    Stack Trace:
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.GetParameters()
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.LoadParameters(IReport report, Collection`1 navigationParameters, IResultObject resultObject)
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerPresenter.Worker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    System.Web.Services.Protocols.SoapException
    System.Web.Services.Protocols.SoapException: The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: A specified logon session does not exist. It may already have been terminated.
       at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ParameterInfoCollection& Parameters)
       at Microsoft.ReportingServices.WebServer.ReportingService2005.GetReportParameters(String Report, String HistoryID, Boolean ForRendering, ParameterValue[] Values, DataSourceCredentials[] Credentials, ReportParameter[]& Parameters)
    Stack Trace:
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.GetParameters()
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ParameterPresenter.LoadParameters(IReport report, Collection`1 navigationParameters, IResultObject resultObject)
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerPresenter.Worker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    The account I'm using is a domain account with 'full' permissions to compliance security role. I also verified the individual object level permission and it holds good. I'm not sure what I'm missing here.
    Any help on this is greatly appreciated. thanks

    I talked to a member of the product team and they agree this is not a solution. He has not heard of this issue before and STONGLY recommends that you contact CSS for support. This is the only way this is going to be fixed permanently.
    It is my guess that if you ever apply a service pack 2 or other updates to CM12, this problem will re-occur, again this is my guess this will happen again.
    Remember that if it is a bug then there is no charge for the support call.
    http://www.enhansoft.com/

Maybe you are looking for