Error after unarchive process - Error: The MDM respository is invalid

Hi Experts:
We are on the process to unarchive a repository, but we are getting this error when trying to logon to load it.
Repository connect failed
Error: The MDM repository is invalid
p.s. We are trying to copy our Production environment to our Test Environment.
Thanks,
Claudia Hardeman

Hi Claudia,
I have been across this scene many times the easiest and fastest way to get rid of this problem is -
1) Delete the repository from Database
Step 1 u2013 Connect to the Database using the Database Management tool
Step 2 u2013 Delete the databases - RepositoryName_z000 and RepositoryName_m000
Step 3 u2013 Delete repository specific entry from the table A2i_Catalogs in A2i_xCat_DBs database
2) Unarchive the repository from old archive
3) Load the repository
This will solve the issue.
Regards.

Similar Messages

"the MDM repository is invalid"

Hej All
Vi have updatered our MDM server with standard update from Microsoft. Later on we can't start MDM services, therefore after "a long fight" it was decided to restore repositories in that way:
we restored a backup of the MDM database on the newly installed server. Afterwards we copied the MDM directories from the old server. we changed the servername in all configuration files and started the MDM systems.
All seems to be fine but each time we log on to repository we got an error:
"the MDM repository is invalid"
can you help?
Thank you in advance.
BR
Rafal

Hi Rafal
just few questions to you
1) Have you checked the connection between your MS Sql and SAP MDM Server ?
2) If you have then are you able to create the repository manuallly?
if you have made the connection and still you are not able to create the repository manually then please reset the connection again, also plz check if the name of this particular repository you are trying the log in is ceated in your MDIS, MDS and MDSS.
if every thing seems to be right then please again import the schema of your old repository and then log with admin user and check if you are able to connect to the repository.
if still you are unable to log in please let us know.
Thanks and Regards
Praful

Upload from iAd Producer fails with error "The Ad contains an invalid banner type".

I worked half a day on an ad in iAd Producer, only to see it fails right after the upload with this error:
"The Ad contains an invalid banner type"
"iAd Workbench currently accepts standard banners. Remove all other banner types and try upload your banner again."
The error and the documentation give no hints on what these "standard banners" are exactly. My project is based on the Tap - Web iAd Blueprint, which requires a bunch of images to be created. I created all of these, regular images as jpeg, transparent images as png. At first the png's were normal (24-bit), but then I read in the help that 8-bit is required. Downgrading the png's to 8-bit didn't help to fix the error though. I also tried recreating the whole project, but it didn't help: same error.
Before the upload, I get this vague warning:
"Are you sure you want to upload your project with assets missing? There are 0 assets you haven't provided yet."
Sounds like a bug. This warning was there in my 1st and in my 2nd project, the 2nd one being the exact copy.
Finally I want to say that simulating in the simulator or Safari, or uploading to the sandbox works fine.
I'm using version 4.2 of iAd Producer on OS X 10.9.2.
Can anyone help me?
Has anyone been successful with the Tap - Web iAd Blueprint?

The Tap to Web blueprint for iPad contains banner types currently not supported in iAd Workbench. Delete the MRec and Full Page banners and you should be able to upload.
-Mark

IWork export to Office error "The file format is invalid" in pages, keynote and numbers.

I am running iWork 09 (latest versions in all cases)*. When I try to export files from all three of the applications Pages, Keynote and Numbers into the relevant Office formats, I get the error "The file format is invalid." It works fine with PDF or RTF export.
I am able to open the same files in the iPad versions of thess iWork apps, and then export them. While this workaround will do for now, I'd like to be able to just export correctly.
Anyone have any suggestions on what might be wrong?
Thanks,
Iarla
* on a MacBook Pro '07, running Lion 10.7.1.

Yes, this worked a treat, thanks very much! *
Iarla
* Note that I needed to manually remove iWorks as the For_iWork:iWork '09:iWork9Update5.dmg.zip file wouldn't work on the latest version of iWorks. This involved deleting the iWork folders in the Applications and Library directories.

I'm trying to open a word file on my iMac and it keeps saying Import error: the file format is invalid. Why?

I exported a file on my imac as a word document but now I can't open it. It says Import error: The file format is invalid.

If no on this forum can help you then I would recommend reposting on the Office for Mac Product Forums.

After unarchive a repository, the auto import is not working

Hi All,
I've met a problem when I archived a repository and unarchive it using another repository name:
I can login to it by Console, and Data manager, etc. But when I put a input file to the Ready folder of its port, the file is not processed by the Import Server. On the other hand, all the other repositories on that server remain fine and the auto-import is normal.
Could any one tell me if there is any other Config shold be done to make the import work?
PS: still the 5.5 version, not 7.1.
Thanks,
Angela
Edited by: Angela Zhang on Aug 6, 2009 9:09 AM
Edited by: Angela Zhang on Aug 6, 2009 9:09 AM

Hi Angela,
If you are using any password for Admin user then same needs to be mentioned in MDIS.ini file. Check the below steps
1. Open MDIS.ini file located in <MDM Insallation directory>/Import Server
2. Navigate to your repository section
3. Remove the character 'E' from the entry PasswordE
4. Write the password of Admin user i.e. Password = abc
5. Restart the Import Server once and check the same password entry, it should get converted to PasswordE and the value should be some characters.
6. Now check the Auto Import
Regards,
Jitesh Talreja

Gives error The requested URL "/", is invalid but I gave a valid format

I gave firefox 3.6.6 what I think is a properly formatted URL, namely http://www.3dfx.com. Firefox changes this to http://www.3dfx.com/ I think the added / indicates it got a response from the URL I gave but then it says The requested URL "/", is invalid.
Reference #9.eb4a595.1295368725.9366789
so it seems like it did not understand the format. By comparison, I enter http://www.purdue.edu and it is changed to http://www.purdue.edu/ and the page is displayed.

Here's a (maybe THE) solution, assuming you have the HTTPS Everywhere add-on installed. If not, then this will probably be of no help at all (sorry).
I was having this exact issue, only when attempting to reach the Washington Post website, which had always worked for me without problems before. I received this error message:
The requested URL "/", is invalid.
To make matters even more confusing, I could reach the desired web site (using the same URL--http://www.washingtonpost.com) on the same PC using Internet Explorer, and on another PC using Firefox.
After an annoying search, Googling this error message, and trying a variety of suggested remedies, I was finally able to resolve the problem by changing the settings for the Firefox add-on HTTPS Everywhere.
In Firefox, click on the Tools menu, then select Add-ons, then click on HTTPS Everywhere and click on the Options button. The HTTPS Everywhere Preferences screen will appear asking, "Which HTTPS redirection rules should apply?"
Uncheck the website you're having the problem with and click OK. That should solve the problem. At least, for me it ended the problem immediately, without restarting Firefox, my PC, my router, or any of the other "remedies" I had tried during my earlier troubleshooting efforts.

Order Import failing with error "The specified subinventory is invalid to use, the profile option INV: Allow Expense to Asset Transfer is set to No. Change the profile option to Yes or choose a valid subinventory."

Hi All,
I am getting this error while importing an internal sales order.
“The specified subinventory is invalid to use, the profile option INV: Allow Expense to Asset Transfer is set to No. Change the profile option to Yes or choose a valid subinventory.”
I have tried to set mentioned profile as ‘Yes’. But still getting same error.
Also, provided subinventory is present and active in given inventory organization.
Please share if anybody encountered this before and have a solution.

Hi 2878342
Please refer the following metalink note, it should resolve your problem.
Order Import Interface.Error Message Specified Subinventory Is Invalid To Use (Doc ID 406411.1)

Numbers 09 not working - I can open the program but only a few files are available, missing blank, checklist and many others. e.g when I click on a file I get this error: The document "nmbtemplate is invalid. The index.xml file is missing. help.

Please let me know what I can do to get my Numbers (iWork 09) working properly again.
Here is what is going on:
Numbers in iWork 09 not working can't access Blank, Checklist and many other files within Numbers. I can open the program but only a few files are available. When I click on the file (which also has no icon just the name of the file) this warning appears:
The document "Blank.nmbtemplate" is invalid. The index.xml file is missing.
I recently had to get a new hard drive installed and had the system upgraded and more memory put in by a Mac certified specialist recommended to me from the Apple store in Northbrook because this was the 3rd time my drive went bad but this time it was to old (I got the IMAC- in 2007) and the Apple store could no longer work on it this time so they recommended a few places that had certified Mac specialists. Since then Numbers is not working right.
I'm sure it's something simple to fix, but I've tried re installing it and that didn't work. Appreciate any help.
Thanks
AppMare

There is one way its getting fixed. Once I update my Adobe Illustrator CC to Adobe Illustrator CC 2014 it is further allowing me to go into the system folder and allocate the font to the file so that it can replace it. My only concern now is that our MAC partners who will receive these files back from us have Adobe CS6. We will down save it to CS6 but I hope they won't experience any font issues because of us using CC 2014? Any light you can shed on this?

Repository is invalid after crash of the MDM Server in MDM 7.1

Hello,
after a crash of our MDS the slave repository is invalid. When I tried to connect to the repository I am getting an error like
Repository connect failed
Error: The MDM repository is Invalid
I tired to delete but I am not able to delete also. While deleteing it is giving an error like
The MDM repository is in read-only mode
The master repository on the same db server and MDS server works fine. I'm also unable to unmount the repository and note 1325833 was not helpful.
Any Help or Solution?
Thanks

Hello Patrick G.
Sometimes we had some situation.
Create your master repository archive .
Connect to database directly and drop you slave repository tablespace.
Than create slave repository again.
in Database you repositories have names like [repository_name] M000 or [repositoryname] _Z000
Regards
Kanstantsin Chernichenka

Repositories are invalid after restarting the MDM Server in MDM 7.1

Hi SDNers,
After I restarted the MDS server I am not able to logon to the repository. When I tried to connect to repository I am getting an error like "Repository Connect Failed and The MDM Repository is Invalid"
I tired to delete but I am not able to delete also. While deleteing it is giving an error like "MDM Repository is in Read Only Mode".
So I am not able to Delete the repository also to create a new Repository.
Any Help or Solution
Thanks
Kiran
Edited by: Kiran on Apr 6, 2011 6:40 AM

Kiran -
some of the below ways you can check
1. Check your mds.ini settings. and do unmount nad then mount the MDM server again. Try to Monitor the Authentication for Particular repositry which you want to connect to your MDM 7.1 server
2. after checking the note 1325833. try restart database server first then MDM server.
3. also try to check with Appropriate repository option once.
HTH
thx
Deep

The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2

Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew

Hi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2015-03-24 09:55:25
End time:                      2015-03-24 10:01:04
Requested action:              CompleteFailoverCluster
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 RS:              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 BC:              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 ComponentUpdate: 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.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine name: SUN-PIE-CS-02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Data Quality Client                      1033                 Standard
Edition     12.0.2000.8     No         Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine Properties:
Machine name:                  SUN-PIE-CS-01
Machine processor count:       16
OS version:                    Windows Server 2012
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2014
ProductName:                   SQL Server 2014
Type:                          RTM
Version:                       12
SPLevel:                       0
Installation location:         \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition:          Standard
User Input Settings:
ACTION:                        CompleteFailoverCluster
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE:     false
ENU:                           true
FAILOVERCLUSTERDISKS:          <empty>
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    <empty>
FAILOVERCLUSTERNETWORKNAME:    sun-pie-mt-01
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTALLSQLDATADIR:             <empty>
INSTANCENAME:                  MSSQLSERVER
QUIET:                         false
QUIETSIMPLE:                   false
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\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:                       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:                       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 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:                       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:                       Setup Support Files
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:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\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.CancelException
    Message:
        User has cancelled.
    HResult : 0x84b70642
        FacilityCode : 1207 (4b7)
        ErrorCode : 1602 (0642)
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

'The state information is invalid for this page and might be corrupted' error

An admin user added a 'widget' for internet content to be displayed on our intranet (sharepoint). Now, anytime I try to modify the page (it is still checked out) I get this error:
The state information is invalid for this page and might be corrupted.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The state information is invalid for this page and might be corrupted.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
  <%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
[FormatException: Invalid character in a Base-64 string.]
System.Convert.FromBase64String(String s) +0
System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +67
System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +4
System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37
System.Web.UI.HiddenFieldPageStatePersister.Load() +136
[ViewStateException: Invalid viewstate.
Client IP: 10.10.16.77
Port: 3996
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; GTB6.4; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8; InfoPath.2) chromeframe/5.0.317.0
ViewState: /wEPDwUJLTY1NzY2ODU3D2QWAmYPZBYCZg9kFgQCAQ9kFgICBQ9kFgJmD2QWAgIBDxYCHhNQcmV2aW91c0NvbnRyb2xNb2RlCymIAU1pY3Jvc29mdC5TaGFyZVBvaW50LldlYkNvbnRyb2xzLlNQQ29udHJvbE1vZGUsIE1pY3Jvc29mdC5TaGFyZVBvaW50LCBWZXJzaW9uPTEyLjAuMC4wLCBDdWx0dXJlPW5ldXRyYWwsIFB1YmxpY0tleVRva2VuPTcxZTliY2UxMTFlOTQyOWMBZAIDD2QWDgIBD2QWAgUmZ18zYzI1NzczNl82NDAzXzQwNTlfYmE4Y19hODJjODE0YzMzOTAPDxYEHgxmaWx0ZXJzdHJpbmdlHg9vbGRmaWx0ZXJzdHJpbmdlZGQCAw9kFgICDw9kFgJmD2QWAgIDDxYCHgRUZXh0BQF8ZAIJD2QWBAIDD2QWAgIBD2QWAmYPZBYCAgEPD2QWAh4FY2xhc3MFGG1zLXNidGFibGUgbXMtc2J0YWJsZS1leGQCBQ9kFgJmD2QWBAICD2QWCAIBDxYCHgdWaXNpYmxlaGQCAw8WAh8FaGQCBQ8WAh8FaGQCBw9kFgJmDw8WBh4cUHJldmlvdXNBdXRob3JpbmdJdGVtVmVyc2lvbgUCMzAeGlByZXZpb3VzQXV0aG9yaW5nSXRlbU93bmVyBQExHhxQcmV2aW91c0F1dGhvcmluZ0NvbnRyb2xNb2RlCysEAWRkA...]
[HttpException (0x80004005): The state information is invalid for this page and might be corrupted.]
System.Web.UI.ViewStateException.ThrowError(Exception inner, String persistedState, String errorPageMessage, Boolean macValidationError) +267
System.Web.UI.HiddenFieldPageStatePersister.Load() +218
System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +83
System.Web.UI.Page.LoadAllState() +35
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7350
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.WELCOMELINKS_ASPX__1775745042.ProcessRequest(HttpContext context) +4
Microsoft.SharePoint.Publishing.TemplateRedirectionPage.ProcessRequest(HttpContext context) +153
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Should I Publish it then re-check it out to edit or even restore to a prior version?

Try one of the tips in these blog posts:
http://weblogs.asp.net/lduveau/archive/2007/04/17/viewstate-chunking-in-asp-net-2-0-maxpagestatefieldlength.aspx
http://delroger.wordpress.com/2008/08/19/invalid-character-in-a-base-64-string-aspnet/
I suspect that the webpart the user added is putting a large amount of data into the page's Viewstate.
Bryan Phillips
MCT, MCSD, MCDBA, MCSE
Microsoft MVP - SharePoint Services
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net

How can I navigate to a new page when after-submit process running proc

I have a long running procedure and would like to provide the users with an animated gif to indicate progress that updates a description line to indicate the current step in the process.
Currently I have a couple pages in this application in which a stored procedure in a package is called which performs a long-running process which updates progress in a table. These processes have a single parameter argument. In these cases I call the procedure via the Job Scheduler as part of my After-Submit process and the page navigation jumps to another page which shows a graphical representation of % complete based on the progress updates in the table and refreshes itself every 5 seconds until the job is complete. This works fine.
I am now running into an issue where I have a more complex set of processes, with a number of parameters. To resolve this I used the same process as above, however, I first check to see if the process exists in the Job Scheduler, if not I create it. I then set all of the parameters and tell the job scheduler to execute the procedure. This should work similar to the process I am running on the other pages, however, in this page where I have multiple parameters and send an execute command rather than an execute immediate on job creation, the system runs the entire job prior to running the page branch, as a result the end user is stuck on a hanging page with no user feedback for two minutes after pressing submit.
I am looking for how to call the procedure and have the branch execute so a progress screen can be viewed. I am not committed to the use of the job scheduler if there is a better way.
Any help is greatly appreciated.

The process involves
(1) a detail table filled with phone usage data, approximately 175,000 records per month.
(2) a table that stores what various combinations of codes in the detail table translate to for types of calls or data transmissions
(3) a summary table for the months calls and billing
(4) the E-Business Suite.
(5) A GTT for temporary crossreference storage
(6) A GTT for reporting data
I have a parameter page where the user selects what data they are looking for and then submits it to generate the report.
The generation of data is a four step process.
(A) Retrieve the Code Combination ID's for the phone usage specified in the parameters from the summary billing table(1) into a GTT(5)
(B) Query the department and Account Code Block Details from E-Business Suite(3) (using dblink) for the CCID's in step one and add to the GTT(5)
(C) Run a query which uses the detail table(1), a function against the crossref table(2), and the crossreference GTT(5) to create the output in the report GTT(6)
(D) An ApEx page process that counts the output and returns to a page without Export to Excel for over 65000 records or with Export for under.
The parameter page is an ApEx page with some text fields, a couple date fields, and some checkboxes. An after submit process calls a packaged procedure which calls separate procedures for (A), (B), and (C), the page then branches to a page that shows an animated gif and current step of the process {this is what is not working right now}. Once the task completes this page branches as per (D) to a page that shows all the contents of the GTT report(6).
The process works successfully with the exception that instead of going to a page to show the process the system simply hangs on the parameter page after the submit is pressed until the processing is done and then goes to the processing page just long enough to branch to the report page.
I am beginning to think that I should alter the design to not use the GTT, but include the username as a field in the output table with a binary index on it for speed so that I can use the job scheduler to run a separate session and hence enable the processing page. The processing page is important as the query can take anywhere from 2 minutes to 2 hours to generate the report depending upon the parameters.

HTTPS SharePoint site with HTTPS Provider hosted app - The remote certificate is invalid according to the validation procedure

We have SharePoint 2013 site configured with SSL and we have developed a provider hosted app which interacts with SharePoint list.
If we try accessing the Provider hosted app from the SharePoint site with HTTP [http://mysharepointsite.com/] there are no any errors thrown.
But whenever the same Provider hosted app is tried accessing from the same SharePoint site using https address
[https://mysharepointsite.com/] we are getting below error:
The remote certificate is invalid according to the validation procedure.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[AuthenticationException: The remote certificate is invalid according to the validation procedure.]
System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) +2983172
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +473
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +86
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +262
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +473
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +86
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +262
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +473
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) +86
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) +262
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) +473
System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) +8530566
System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) +230
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +645
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) +9
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) +87
System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) +1467
System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) +84
System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) +22
System.Net.ConnectStream.WriteHeaders(Boolean async) +761
[WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.]
System.Net.HttpWebRequest.GetResponse() +8534156
Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute() +58
Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb) +975
ProviderHostedHTTPSWeb.Default.Page_Load(Object sender, EventArgs e) +348
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178
We have already added the certificate used for the SharePoint site and the provider hosted app in the SharePoint central admin trusts.
Any idea's how can I resolve this issue?

Hi,
According to your post, my understanding is that you failed to access provider host app using https.
The reason for this is that SharePoint implements its own certificate validation policy to override .NET certificate validation.
Fix is to setup a trust between SharePoint and the server requiring certificate validation.
For more information, you can refer to:
http://blogs.technet.com/b/sharepointdevelopersupport/archive/2013/06/13/could-not-establish-trust-relationship-for-ssl-tls-secure-channel.aspx
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Error after unarchive process - Error: The MDM respository is invalid

Similar Messages

Maybe you are looking for