Import Solution Package (WSP) 2013 using VS 2012

Anyone working/worked on SharePoint 2013 solution using VS 2012?
I am trying to Import Solution Package (WSP) using VS 2012, but VS 2012 doesn't allow to import the solution. It throws an error with message saying that SharePoint Foundation/Server 2013 need to be installed on local system.
I have also installed MS Office Developer tool for VS 2012, but VS still throws an error while Importing Solution Package.
Please suggest steps to import WSP in VS 2012..

Hi vaibhavi,
Here is the list of steps given
http://msdn.microsoft.com/en-us/library/ee231603(v=vs.110).aspx
Please remember to click 'Mark as Answer' on the answer if it helps you

Similar Messages

Install TFS 2012 Solution packages (WSP) on MOSS 2007 that already have TFS 2010 Solution package installed and deployed

Hi
I hope to place this question in the proper forum but if not, can someone move it to the right forum. Thanks
I have a MOSS 2007 farm and I have 2 TFS 2010 SharePoint extension solution package (WSP) installed and working properly for a while now.
Microsoft.TeamFoundation.SharePoint.Dashboards.wsp and Microsoft.TeamFoundation.SharePoint.wsp
The Application team is going to upgrade their TFS 2010 server to TFS 2012 and want me to installed the new TFS 2012 SharePoint WSP solution to our MOSS farm.
My Question is that do I have to uninstall TFS 2010 solution package first or can I installed the new TFS 2012 solution packages in addition and both TFS 2010 and TFS 2012 solution package will co-exist and will work properly?
the reason i want to do this is making sure all existing TFS 2010 will still work. My concern is if I have to uninstall TFS 2010 solution just to get TFS 2012 solution then run into problem with existing TFS 2010 projects.
Thanks in advance for any advice or insight on this.
Swanl
Swanl

Hi Swanl,
you may check on the prequisite in sharepoint products,
"SharePoint Products: If you have a portal server, you might have to upgrade it to continue using SharePoint integration. We no longer support Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007. See
SharePoint Products requirements for Team Foundation Server."
Supported versions, editions
SharePoint Foundation 2013¹
SharePoint Server 2013,¹ (Enterprise or Standard edition)
SharePoint Foundation 2010²
SharePoint Server 2010,² (Enterprise or Standard edition)
http://msdn.microsoft.com/en-us/library/hh667648.aspx
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

CRM 2013 online - deploy a 2015 solution package to crm 2013

Hi,
We have staging online CRM upgraded to 2015 already, however, the prod CRM still stays in version 2013 during this transition time. We developed some functions in staging CRM, such as new attributes, web resources, workflows, etc, and packaged
them into a solution. When we imported the solution to production(2013), we had the error saying '...invalid XML in package...'. Is there any way to fix it? Thanks.

Hello,
So if I have got it right, you want to export your solution from CRM 2015 to CRM 2013 which is your production. Unfortunately you cant do this as any solution exported from a newer version of Microsoft Dynamics CRM (which is crm 2015 in your case)
cannot be imported into an older version of Microsoft Dynamics CRM (which is CRM 2013 in your case).
You can also refer the following link for more information:-
https://msdn.microsoft.com/en-us/library/gg328109.aspx?f=255&MSPPError=-2147217396
Regards, Abhishek Bakshi If you find this post helpful then please Vote as Helpful and Mark As Answer. Check my blog on https://mydynamicscrmblog.wordpress.com/

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

Error in xpras when importing support packages in solution manager

Hello,
We are importing support packages in our solution manager and we begun
the process more than two weeks ago and the process is still running.
I have stopped the system and restarted the import again, but it seems
to be the same. The SP queue is:
SAPK-1507EINSTPL
SAPK-1507FINSTPL
SAPK-1507GINSTPL
SAPK-1507HINSTPL
SAPK-1507IINSTPL
SAPK-1507JINSTPL
SAPKB70015
SAPKA70015
SAPKITL426
SAPKIPYJ7F
SAPKW70017
SAPKU50012
SAPKB70016
SAPKA70016
SAPKITL427
SAPKIBIIP9
SAPK-40012INCPRXRPM
SAPK-40013INCPRXRPM
SAPK-40014INCPRXRPM
SAPKNA7012
SAPKNA7013
and there is an error (rc=12) at the method execution step in package SAPKU50012 or in SAPKB70016.
Now, there is an rc 12, but the queue is running, the import queue hasn't cancelled, but it seems to do nothing. The RDDEXECL job log is:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server crosol203 were synchronized
Error Building the ENH TreeObject Type:XHObject Name:EH_FJ_FUBA_PARA_VERS
the job was running for 149.332 seconds and at that moment I stopped the sap system. After restating the system I imported the queue again and now, the process has been running for more than 13500 seconds.
We have checked note number 1142410 and all the modifications were already implemented in the system.
Thanks and best regards,
Ana.

Hello Sunny,
The problem is still happening. I have read and apply all the threads you suggested, nut they didn't resolve the problem:
I have updated the kernel
I have checked table DRSEG and it has no problems.
I don't have any syntax errors so I haven't run the SGEN as I think it doesn't apply.
After changing the kernel I have started the sap system and the job rddexecl has started itself before running again the SPAM and reimporting the queue.
I already have 6 support packages without running the method execution step and I don't know how much time it will consume.
Regards,
Ana

AirDrop doesn'n work between Macbook Pro Mid 2012 and Mac Book Air mid 2013 using both Yosemite

Can't search other devices using AirDrop between between Macbook Pro Mid 2012 and Mac Book Air mid 2013 using both Yosemite...
And trying with MBP late 2011 can't connect either

Hey aniMix,
Thanks for the question. I understand that you are experiencing issues with AirDrop. The following resource provides some troubleshooting information which may be helpful:
Mac Basics: AirDrop lets you send files from your Mac to nearby Macs and iOS devices
http://support.apple.com/kb/HT6510
Thanks,
Matt M.

Import certificate in to Firefox certificate store using SCCM 2012 R2

Hello,
I'm trying to figure out how to import a certificate in to the Firefox certificate store using SCCM 2012 R2 to push out to 8,000 computers. The only answer I have found was to import the certificate manually on my computer and copy the "cert8.db" file out of my "appdata\Roaming\Mozilla\Firefox\Profiles\******.default\" folder and use this file to copy to all profiles on each computer. I have not tried this since I believe this is not a standard practice. Is there a Firefox certificate scripting tool that I can use to accomplish this or a recommended way?
Thanks,
Matt

Hi,
It is listed here:http://technet.microsoft.com/en-us/library/gg712298.aspx
There are a number of limitations to supporting workgroup computers:
Workgroup clients cannot locate management points from Active Directory Domain Services, and instead must use DNS, WINS, or another management point.
Global roaming is not supported, because clients cannot query Active Directory Domain Services for site information.
Active Directory discovery methods cannot discover computers in workgroups.
You cannot deploy software to users of workgroup computers.
You cannot use the client push installation method to install the client on workgroup computers.
Workgroup clients cannot use Kerberos for authentication and so might require manual approval.
A workgroup client cannot be configured as a distribution point. System Center 2012 Configuration Manager requires that distribution point computers be members of a domain.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Importing packages in JSP using iPlanet problem

hi experts,
i am new begi to iPlanet server6.0
i have installed iPlanet6.0 in windowsNT(d:\iPlanet\servers)
document root is d:\iPlanet\servers\Docs
i have one jsp called test.jsp in document root dir.
i imported one package called adminBeans in jsp file.
i put adminBeans class folder in
d:\iPlanet\servers\Docs\WEB-INF\classes
whrn i am ruuning this jsp error shows as below
============================
[04/Jul/2002:11:15:01] info ( 347): JSP: JSP1x compiler threw exception
org.apache.jasper.JasperException: Unable to compile class for JSPd:\iPlanet\Servers\https-ntserver.vsnl\config\..\ClassCache\_jsps\_test_jsp.java:15: Package adminBeans not found in import.
import adminBeans.*;
^
1 error
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:284)
     at com.iplanet.server.http.servlet.NSServletEntity.load NSServletEntity.java:252)
     at com.iplanet.server.http.servlet.NSServletEntity.update(NSServletEntity.java:173)
     at com.iplanet.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:416)
=====================================================
do i want to set any configuration for jsp running?.
without any import,like helloworld.jsp file is working fine.
any idea
plz help me ya.
thanks in adv.
endrum anpudan
maruthu

hi,
first of all u understand the way package works
suppose u have package named mybeans and there r classes under this folder for e.g myBeans/AdminBean and many more so ur definetly going to import the classes in this way import myBeans.*; for all classes or import myBeans.AdminBean; for single class but before doin that make sure that u have set that package path in ur environment. how will u do that ? register the path just above one folder to myBeans for e.g
D:\myClasses in the evironment and ur myBeans folder wil reside under D:\myClasses\myBeans

Adobe Creative Cloud Enterprise Deployment Issues using SCCM 2012 R2

Hi,
I have been trying to deploy Adobe Creative Cloud Enterprise to Windows 8.1 machines that are identical, using SCCM 2012 R2.
The Adobe package seems fine, because it seems to deploy successfully to some machines. And SCCM 2012 R2 has been configured correctly, as I can deploy other software using it, and again, it deploys Adobe CC successfully to some of the machines.
I have tried comparing the package that is downloaded on the test machine/client machine, with the original package on the distribution point, using Beyond Compare, and there are no differences.
I have contacted Adobe Enterprise Support, and they asked me to send to them log files from Event Viewer, the msi installer, and other Adobe logs, from the machine that failed the deployment. However, after Adobe studying them, they told me that they could not identify any problems... Strange, because I could have sworn that I saw error 1603 pop up over 20 times on different machines indicating that the 'Set-up.dat' file had a problem with it.
After all the testing on over 20 identical machines (same hardware/same software), using different configurations on SCCM 2012 R2 and the client machines, I still can't seem to have a reliable solution to deploying Adobe CC.
The fact that it deploys successfully on one machine and fails on another, or sometimes deploy to two machines and fail on another (simultaneously), is something that I don't understand.
Another thing is that, if I retry the deployment 10-15 times after it failed the first time, it might go through...
Adobe Enterprise Support asked me if they could remote into a machine that failed the deployment to have a look at it and I agreed to that option, but it seems like my issue has been ignored because they never got back to me.
Has anyone had this kind of problem or anything similar before?
I need to be able to deploy this remotely to 100+ machines. So installing manually is not an option.
Any help is appreciated.
This was posted in the wrong section a few days ago. I'm hoping I can get some help here.
Case Number: 1862659812
UPDATE: I spoke to Adobe Customer Support and after 1.5 hours on the phone with a remote session going on, problem was still not solved or identified. Additional log files have been sent and now I'm waiting for a call back.

Hi Robert,
We seem to be having a very similar issue. Our installs would randomly fail with error code 1603 and an error message about a fault in Set-up.dat. Failure rate was near 95% on our 900 machines. Adobe Support and Karl having been looking into our issues but so far no solution has been found.
Having done a lot of investigating we've managed to deploy our package using a schedule task running as a domain admin. This is a nasty solution and we don't intend on using this permanently, but we needed to get the package out.
Are you seeing any of the following:
Entries in PDApp.log:
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The Bootstrapper Process is (5).Stopping the installation process.
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to find the pdb database.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to get the local payload database handle.
Event Log:
Faulting application name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Faulting module name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Exception code: 0xc0000005
Fault offset: 0x000d7c52
Faulting process id: 0xb40
Faulting application start time: 0x01d072a073861622
Faulting application path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Faulting module path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Report Id: c86d9216-de93-11e4-8284-782bcb99e284
Faulting package full name:
Faulting package-relative application ID:
Installer Log
Indicates it can't find the Media_db. We noticed that the folder C:\Program Files (x86)\Common Files\Adobe\caps doesn't get created on the machines were the install fails, so error message is correct in that there isn't a Media_db.db. Sysinterals Process Monitor seems to show that the setup tried to create the folder/files but they don't actually get created. Copying a Media_db into the folder from another machine seems to allow the installation to almost finish, but unsurprisingly you end up with problems later on.

SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903

Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.

Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain.

Correct way to install SHARE POINT 2013 ON WINDOWS 2012 R2

HI
INSTALLING SHAREPOINT 2013 ON WINDOWS 2012 R2 IS NOT SUPPORTED , when i search for this i found a kb article
https://support.microsoft.com/en-us/kb/2891274
SharePoint 2013 SP1 support in Windows Server 2012 R2,
So in windows server 2012 R2 machine i should install
1) install sharepoint pre requisites
2) run sharepoint setup and install binraries
3)and after download sharepoint 2013 SP1 and install
is the right steps will i do for INSTALLING SHAREPOINT 2013 ON WINDOWS 2012 R2?
adil

Get the SharePoint 2013 w/ SP1 ISO from the MSDN or VLSC (or Download Center if using SharePoint Foundation 2013) -- this is required for Windows Server 2012 R2, other media will not work. Follow the standard SharePoint install process, e.g. run the pre-req
installer, and then install SharePoint.
Once completed, install the appropriate version of SP1 for your product. See http://thesharepointfarm.com/2015/04/list-of-good-sharepoint-2013-service-pack-1-packages/
for a list of packages.
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Uninstall Microsoft Office 2013 using Invoke-TroubleshootingPack

Hi,
I'm deploying an uninstallation package to uninstall Office 2013 using the ingenious Microsoft Fix it (located here: http://support.microsoft.com/kb/2739501/en-us)
called O15CTRRemove.
When running it manually, it removes everything that is related to Microsoft Office 2013 and I am able to install a new Office 2013 without any problems (changing from Office 365 to VL).
The problem is as follows:
I need to do this silently on a lot of computers using a deployment tool. I figured out how to use powershell and I'm doing it in the following way:
Import-Module TroubleshootingPack
$DIAGOFFRemoveOff2013 = Get-TroubleshootingPack -Path "C:\Deployment\Office2013Uninstall\O15CTRRemove"
Invoke-TroubleshootingPack -Pack $DIAGOFFRemoveOff2013 -AnswerFile "C:\Deployment\Office2013Uninstall\DIAG_Off_RemoveOff2013.xml" -unattended
I created the Answerfile DIAG_Off_RemoveOff2013.xml in the following way (according tohttp://blogs.technet.com/b/heyscriptingguy/archive/2011/02/09/use-powershell-troubleshooting-packs-to-diagnose-remote-problems.aspx):
Get-TroubleshootingPack "C:\Deployment\Office2013Uninstall\O15CTRRemove" -answerfile "C:\Deployment\Office2013Uninstall\DIAG_Off_RemoveOff2013.xml"
It looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<Answers Version="1.0" />
When I run the script it works but for some reason, it doesn't work when I run it as system (my deployment tool runs the script as system, and I've tried it manually like this):
psexec -i -s cmd
cmd /C powershell -executionpolicy unrestricted -file "C:\Deployment\Office2013Uninstall\Uninstall_Office2013.ps1"
It just hangs and I can see in eventviewer that it has run a few troubleshooting packs, that the uninstall of Office is complete but it doesn't continue until I force kill sdiagnhost.exe.
If I run the script after killing sdiagnhost.exe, it finishes without a problem.
I have temporarily solved it like this (I run the same job twice, to be sure everything is removed and the second one finishes quickly while the first hangs until the timeout):
Start-Job -ArgumentList -ScriptBlock {
$DIR = "C:\Deployment\Office2013Uninstall"
Import-Module TroubleshootingPack
$DIAGOFFRemoveOff2013 = Get-TroubleshootingPack -Path "${DIR}\O15CTRRemove"
Invoke-TroubleshootingPack -Pack $DIAGOFFRemoveOff2013 -AnswerFile "${DIR}\DIAG_Off_RemoveOff2013.xml" -unattended
Get-Job | Wait-Job -Timeout 1200
Get-Job | Receive-Job
Get-Job | Remove-Job -Force
Start-Job -ArgumentList -ScriptBlock {
$DIR = "C:\Deployment\Office2013Uninstall"
Import-Module TroubleshootingPack
$DIAGOFFRemoveOff2013 = Get-TroubleshootingPack -Path "${DIR}\O15CTRRemove"
Invoke-TroubleshootingPack -Pack $DIAGOFFRemoveOff2013 -AnswerFile "${DIR}\DIAG_Off_RemoveOff2013.xml" -unattended
Get-Job | Wait-Job -Timeout 1200
Get-Job | Receive-Job
Get-Job | Remove-Job -Force
I am thinking that there is some kind of dialogue questions that I need to get into the answer file, but I have no idea how to do it.
Any help is appreciated!
Best regards,
Simon

Credit goes to MS for core script (its to long to post here).
Credit goes to the guy who wrote the cleaner script. Whoever packaged it and didn't build in silent switches gets zero points.
Please note that this will only work for C2R installs of Office 2013.
This is not true. There are scrub scripts specific to C2R as well as MSI.
I extracted the scrub vbs from O15CTRRemove.diagcab
This is what worked for me. Use 7-zip to extract the entire package to a directory. Then run "OffScrub_015msi.vbs all".

Importing Database Package into OWB changes position of parameters .. Nasty

Hi all,
Anyone else having the same problem ? Any solutions ? Or is this a bug.
When a package is imported from a DB schema, OWB kindly changes the order in which the parameters are listed.
The effect is that any mapping using the procedure or function will not have the correct parameters passed to.
For example.
DB_Test_proc
io_name_in in out varhar2,
o_clean_name_out out varchar2
After importing in OWB the parameter positions are reversed .... very nasty.
Anyone can help or do I raise a bug ?
Regards
Nick

Hi Borkur,
Dropping and re-importing the package would work well (works for another module) but this is a package whose procedures and functions are heavily referenced in several mappings and process flows (supports the custom job management). So, I would be forced to re-synchronize them all which I want to avoid. The other way would be to modify the package manually (only the signature is needed not the code since I will not deploy it from OWB, in fact, I deployed it from Oracle Designer !!!). But OWB Paris doesn't allow this. Once imported, always imported. You can modify imported tables, procedures, functions but not packages. Or is there a way ???
regards
Thomas

Create solutions in SharePoint 2013 with possible to run in SharePoint 2010

Hi,
I would like to create WebParts on SharePoint 2013 (in Visual Studio 2012) version but I would like to run them on SP 2010 too. So it would be great to have such compability back one solution under VS 2012. Is it possible to
make this one to not duplicate code for different versions?
Thanx for any info!
Regards
Kamil

Hi,
As Paul said, I suggest you develop your SharePoint project using visual studio 2010 for SharePoint 2010.
If you want to use this project in SharePoint 2013, we need convert it to the SharePoint 2013 project, the following articles for your reference:
Upgrade SharePoint 2010 Visual Studio Solution to SharePoint 2013
http://ranaictiu-technicalblog.blogspot.com/2013/10/upgrade-sharepoint-2010-visual-studio.html
Converting Multiple SharePoint 2010 Projects to SharePoint 2013
http://www.codeproject.com/Articles/522220/Converting-Multiple-SharePoint-Projects-to-Sh
Best Regards
Dennis Guo
TechNet Community Support

Deploy SharePoint 2010 Sandbox solution to SharePoint 2013

Hi All,
I have sand-box solution which is developed in Visual Studio 2010 for SharePoint 2010 ,And it is specially developed for branding the SharePoint 2010 site. Now I need
to add the sandbox solution to SharePoint 2013 Site.
Can any one help how can I do this.
Thanks, Quality Communication Provides Quality Work. http://siddiq-sharepoint2010.blogspot.in/ Siddiqali Mohammad .

Hi siddiqali,
According to your description, my understanding is that you want to deploy SharePoint 2010 Sandbox solution to SharePoint 2013.
Most of the wsp Solutions deployed in SharePoint 2010 should work fine in SharePoint 2013. This is because of the Support for both 14 Hive and 15 Hive directories that are Created in SharePoint 2013 by default.
Initially, when you deploy a SharePoint 2010 Solution it gets deployed to 14 Hive and not 15 Hive. To force the solution to install in 15 Hive you need to modify manifest.xml file of your solution and add addSharePointVersion=”15.0” attribute to it. The
Solutions can be forced to install in 15 hive. However, some of the files especially that refers to _layouts might not work. All SharePoint 2010 Solution files that refers to _layouts folder (i.e. Features, Layouts-files, Images, ControlTemplates)needs to
be updated, the best approach is to re-create the Solution in Visual Studio 2012.
More information, please refer to the link:
http://www.learningsharepoint.com/2013/03/24/deploy-sharepoint-2010-solutions-in-sharepoint-2013/
Here are some similar posts for you to take a look at:
http://www.threewill.com/2013/10/migrating-a-sharepoint-2010-solution-to-a-sharepoint-2013/
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/30fe4cb9-ea11-46d0-868d-4306d915b4db/how-to-convert-sp2010-wsp-to-sp2013?forum=sharepointdevelopment
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Import Solution Package (WSP) 2013 using VS 2012

Similar Messages

Maybe you are looking for