Release Management DACPAC deploy store procedures

Hi
i have TFS Build and Release Management, i have component DACPAC database deployer but it does not deploy store procedures or views. the store procedures changes not see in database. can I deploy Store Procedures and views?
thank for your help
steve

Hi Steve,
Thanks for your post.
Please manually publish your DACPAC file, the store procedure and views can be published to your SQL Server database successfully? You need ensure manually publish the DACPAC file can works fine, then run it in your release template and check the result
again.
For more information about deploy database using DACPAC Database Deployer tool in release template, please refer to this article:
http://www.incyclesoftware.com/2014/03/deploying-databases-release-management/.
Or you can use the Database Deployer – Execute Script tool to run your stored procedure file, please refer to the information in this post:
https://social.msdn.microsoft.com/Forums/en-US/24119b72-0b05-48c5-bdea-188f95067aeb/pass-parameters-to-a-sql-script-using-database-deployer-execute-script-from-release-management?forum=tfsbuild.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Release Management vNext deployment succeeds without deploying the DSC to the target.

All of a sudden, a couple of weeks ago, our vNext releases stopped working.
The log in the release management client says that the release has been deployed successfully, but nothing has actually happened on the target server. The log looks like this (which is bad)...
Copying recursively from \\xxxxx.co.nz\Public\Share\Development\Builds\DispatchService_MAIN\DispatchService_MAIN_1.1.7.0\DispatchService\_PublishedWebsites\DispatchService to C:\Windows\DtlDownloads\DispatchService Component succeeded.
That's all it says. No error, no nothing.
It used to look like this (which was good)...
Copying recursively from \\xxx.co.nz\Public\Share\Development\Builds\SosService_MAIN\SosService_MAIN_1.1.32.0\SOSWindowsService to C:\Windows\DtlDownloads\SosServices succeeded.
Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
An LCM method call arrived from computer BDWEB10 with user sid S-1-5-21-3667390900-813461161-666584507-16981.
[BDWEB10]: LCM: [ Start Set ]
[BDWEB10]: LCM: [ Start Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Test ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ End Test ] [[bStopService]StopTheService] in 0.0000 seconds.
[BDWEB10]: LCM: [ Start Set ] [[bStopService]StopTheService]
[BDWEB10]: [[bStopService]StopTheService] Stopping service SosServiceDevReviewPci
[BDWEB10]: LCM: [ End Set ] [[bStopService]StopTheService] in 0.1400 seconds.
[BDWEB10]: LCM: [ End Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Resource ] [[File]CopyDeploymentBits]
[BDWEB10]: LCM: [ Start Test ] [[File]CopyDeploymentBits]
etc etc
I have tried many things, and have discovered some clues, but have filed to find a solution.
It seems that it is successfully creating the .mof file on the "Deploy using PS/DSC Server" but then it deletes the .mof file and does not try to do a Start-DscConfiguration with the .mof file.
This is very frustrating, as we have sunk an awful lot of time and money into Microsoft Release Manager.
Does anyone have any ideas?

Hi Leighton,
Thanks for your post.
You’re using TFS 2013 Update 4 and Release Management 2013 Update 4?
Do you mean that the files be copied to C:\Windows\DtlDownloads\DispatchServices folder on target machine as expect, but no file be executed to perform the deploy?
You said the release template works fine a couple of weeks ago, do you know which changes happened on this release template after that week?
Only this current one release template cannot works? Or if you create a new release template to run DSC deploy, it will receive the same result too?
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Release Management schedule deployment

Hi
How do i can schedule execute deployment at a specified Date/time before i approve step?
thanks for your help
steve

Hi Steve,
Thanks for your reply.
After you approved the first stage, the second stage will be run automatically? Don’t specify the release target stage in your build definition.
If you also want to schedule the second stage after approved the first stage, as far as I know there’s no default way to do this. You can create a second schedule build definition to trigger second release target stage separately.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

RE: List Archive and Release Management

Hi back.
>> what procedures do people use to manage the development, testing
and release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forté SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forté SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Under Forte 2 we used to export all projects, then import them into a make
repository, then produce an app. Due to the time involved importing &
exporting, and errors resulting from importing projects out of order, we
switched to making copies of the dev repository and producing apps from
that. For us, it used to take 2+ hours to export/import, as opposed to 5
minutes for copying repository files. Unfortunately, we have found that
unless we force-compile prior to deploying, we will get errors when
attempting to compile partitions.
Our current procedure:
Shut down dev repos
Copy to make env
make a workspace that includes all projects
force-compile
update
integrate
make a new workspace for each app to make
make each app
export code
remove unused workspaces
clean repos
-----Original Message-----
From: Peter Sham (HTHK - Assistant Manager - Software Development, IITB)
[mailto:[email protected]]
Sent: Wednesday, July 21, 1999 3:31 AM
To: John Pianezze; Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi,
We, like what you've explained, keep different releases of our application
in different workspaces. However, when the release is getting larger, this
"check-out-every-components-then-overwrite-by-import" procedure get tougher.
Sometimes, it even creates garbage in the repository which corrupts my
workspace.
So, I have an alternative proposal on this procedure ( though I haven't
really test on this idea ) which is to create a new repository for each new
release.
What do you think?
Regards,
Peter Sham.
-----Original Message-----
From: John Pianezze [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 3:44 PM
To: Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi back.
what procedures do people use to manage the development, testingand release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's
ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every
application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new
repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their
stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forti SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and
checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forti SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Unable to Create Website using "Create Web Site" action component in Release Management

Hi Team,
I am trying to use Release Management to Deploy my Website along with DB in staging servers.
I have set-up 2 Staging Servers SIT & UAT Both 2012 Servers with IIS 8.5 Configured.
Defined Release Path and Release template.
Deployment Sequence is something like this :
Deployment Sequence - Server Name - Create Folder - XCopy - Create Website - Configure Website
Build is successful, drops the output to Output folder and RM gets initiated with it's work.
It creates folders as mentioned in the "Create Folder" activity.
It copies the whole content from _PublishedWebsites to the mentioned location.
It gets stuck with the "Create Website" step.
Initially I have provided details as follows :
AppPoolName
IsPreloadEnabled
IsAutoStart
SiteName FabrikamSIT
PortNumber 80
PhysicalPath c:\FabrikamRM\WebSite\SIT
Later, I tried providing
AppPoolName DefaultAppPool
IsPreloadEnabled 1
IsAutoStart 1
SiteName FabrikamSIT
PortNumber 80
PhysicalPath c:\FabrikamRM\WebSite\SIT
Then also no luck.
Deployment gets rejected and the error that you can see when you hover the mouse is :
Task failed with the exit code -2146232576".
No much info available with this eror code in net also.
Any help in getting this simple site created is highly appreciated.
Thanking you in advance,
Regards,
TFS Queries

Hi,
For the deployment sequence, you might need add the action of "create application pool" before creating a website.
Another method is check whether the build output can be deployed manually. If yes, then you can trobleshoot the problem in your deployment sequence and parameters. You can create the website manually and deploy your build output to the website. If you have
any other concerns about the deployment, you can also open a new thread in IIS forum for a better response.
If the issue persists, please elaborate more details about your scenario with sceenshots.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Release Management fails to locate log file

Hi,
I'm using Visual Studio Release Management to deploy MSI packages.
When I try to "View Log" I get the following error:
There was an error while reading the log: Could not find file 'C:\Users\zzzzzz\AppData\Local\Temp\RM\T\RM\xxxxxx\201503051135578722385-6\__Installer__.log'.
And the step reports Success when it should have reported an error (The MSI returns an error).
Any idea why the log is not generated?
Thanks,
Gilad

Hi Gilad,
You can check whether you can find the log in the path. If the log not exist, you can do a new release and check the log after doployment.
I'd like to know the error details about MSI. If the deployment succeed, then the release can be taken as successful.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to load and define Java Store Procedures using Consolidator Manager??

Hi,
I am trying to create a store procedure with a very easy example and I can not succeed. i am a bit new with OLite and I will appreciate any help from your side. I am quite lost now regarding of using java with OLite and it is becoming quite urgent for me. Thanks a lot in advanced.
Those are the steps that I follow:
- Creating the java class
I create the java file MYUPPER.java with next code :
public class MYUPPER {
public static String doUpper( String p_text )
return p_text.toUpperCase();
I compile it and I create the jar file:
C:\>javac MYUPPER.java
C:\>jar cf MYUPPER.jar MYUPPER.class
- This is an abstract of my java code using the API:
( m_cm is ConsolidatorManager)
// Create the java resource
m_cm.createStoredProc( "MYUPPER.jar", "MYUPPER", "doUpper", "doUpper");
// Add it to the publication
m_cm.addJavaResource( "PMTS", "MYUPPER" );
- After running that code I do not receive any exception and checking into the repository looks ok:
a) From the Mobile Server I can see the Java Ressource MYUPPER for that publication
b) I can see the entries in C$Resouces and in C$Pub_Objects as well
*** ON THE CLIENT:
Then I go to the client device a Windows XP labtop where I did install the jre 5.0 and I added the bin path to the system variable PATH.
- I get a POL-8000 error when synchronizing (could not start the Java Visrtual Machine)
- Anyway, I can see the MYUPPER.class file deployed in the same directory than the databases are.
- I have also tried next from msql:
c:\>msql system/manager@jdbc:polite:tomeu_conscli
Oracle Lite MSQL Version 10.3.0.2.0
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Connected to: Oracle Lite ORDBMS
Database Name: CONSCLI (Read Write)
Database Version: 10.3.0.2.0
Auto Commit: off
Driver Name: oracle.lite.poljdbc.POLJDBCDriver (OLite 4.0)
SQL> select * from c$resources;
PUB_NAME | DB_NAME | RESOURCE_NAME | RESOURCE_TYPE | RESOURCE_DATA
PMTS | pmts | MYUPPER | JAVA CLASS | -¦¦¥ 1
1 row(s) returned
SQL>
SQL> exit
Disconnected from CONSCLI
c:\>msql system/*****@jdbc:polite:tomeu_pmts
Oracle Lite MSQL Version 10.3.0.2.0
Copyright (c) 1997, 2008, Oracle. All rights reserved.
Connected to: Oracle Lite ORDBMS
Database Name: PMTS (Read Write)
Database Version: 10.3.0.2.0
Auto Commit: off
Driver Name: oracle.lite.poljdbc.POLJDBCDriver (OLite 4.0)
SQL> select doUpper('fhjdjf') from dual;
[POL-8035] no such attribute or method
SQL> create table sp (id number(1) primary key );
Table created
SQL> alter table sp attach java source "MYUPPER" in '.';
[POL-8028] error in calling a Java method
SQL> commit;
Commit complete
SQL> select sp.doUpper('fhjdjf') from dual;
[POL-8035] no such attribute or method
Lost... :(
Tomeu

sorry to bother, similar like above, i tried many times on my computer to load a simple image in java application.. here's my code:
import java.awt.*;
import java.awt.event.*;
import java.awt.image.*;
import java.io.*;
import java.net.*;
import javax.swing.*;
public class View extends JFrame {
     private URL imageURL;
     private File file;
     private Image sourceImage;
     private String name, title, message;
     private int width, height;
    public static void main(String[] args) {
        System.out.println( "Hello Eros!!!" );
        View img = new View();
    public View() {
         name = "D:/shared/inputpic.gif";
         file = new File( name );
        Toolkit toolkit = Toolkit.getDefaultToolkit();
        try {
            imageURL = new URL("http://www.google.com.my/images/logo_sm.gif" );
        } catch (MalformedURLException e) {
        if ( file == null ) {
            sourceImage = Toolkit.getDefaultToolkit().getImage( name );
            System.out.println( file );
        } else {
            sourceImage = toolkit.getImage( imageURL );
            System.out.println( file );
        width = sourceImage.getWidth( this );
        height = sourceImage.getHeight( this );
        System.out.println( "Pixel = " + width + "x" + height );
        if ( width * height == 1 ) {
            title = "Greetings"; // Shown in title bar of dialog box.
            if ( file == null ) {
                message = "Unable to load the file " + name;
            } else {
                message = "Unable to load the link " + imageURL;
            JOptionPane.showMessageDialog(null, message, title, JOptionPane.INFORMATION_MESSAGE);
}could anyone test this n give my the reason i couldnt even load the image

Is it possible to do Continuous deployment for azure cloud services(website,web and worker roles) using VSO Release management?

Hi,
I am trying to do continuous deployment using visual studio online and release management for Azure cloud services. But not able to find the way to do it(with the help of different blogs, those are describing using VM only).
I tried using Release management visual studio extension also. But no Luck.
Please help me if it is possible to do continuous deployment using release management.
Thanks,
Phani

Hi,
Please refer to the following Forum Thread with similar question which has been answered. Let us know if this helps.
https://social.msdn.microsoft.com/Forums/en-US/9d8322f6-36e5-4cca-a982-d420d34d2072/realease-management-deployment-to-azure-websites-webworker-roles?forum=tfsbuild
Regards,
Nithin Rathnakar

Version control, build, deploy and release management of eBS applications?

Hi All
I am setting up a standard configuration management, build & deployment automation and change & release management process for all types of applications including Oracle eBS, Informatica, Siebel, Cognos, Java etc. As you know, SCM for Java and .Net types of applications are very matured, but not for other types of applications such as Oracle eBS.
Can you give me some hint or point me to some documents on how to manage Oracle eBS applications from SCM's perspective? For example,
1. How to version control eBS artifacts? e.g. what kind of eBS artifacts need to be version controlled?
2. How to build eBS artifacts and then deploy to a new environment? How to move an eBS application from one environment (DEV) to test environment?
3. How to manage changes?
We have a standard SCM tool called RTC from IBM, which has version control, build and change control functions.
Thanks
Jirong

hujirong wrote:
Hi All
I am setting up a standard configuration management, build & deployment automation and change & release management process for all types of applications including Oracle eBS, Informatica, Siebel, Cognos, Java etc. As you know, SCM for Java and .Net types of applications are very matured, but not for other types of applications such as Oracle eBS.
Can you give me some hint or point me to some documents on how to manage Oracle eBS applications from SCM's perspective? For example,
1. How to version control eBS artifacts? e.g. what kind of eBS artifacts need to be version controlled?
2. How to build eBS artifacts and then deploy to a new environment? How to move an eBS application from one environment (DEV) to test environment?
3. How to manage changes?
We have a standard SCM tool called RTC from IBM, which has version control, build and change control functions.
Thanks
JirongPlease do not create duplicate threads -- Software Configuration Management of Oracle eBS

Release Management slow to tell TFS that a deployment was successful.

This is an example of the slowness from one of my projects:
A build is queued > MSBuild starts within ten seconds > the build is complete within 35 seconds > I see "Creating the release and waiting for deployment results" within 50 seconds from the build status page > The build deploys to the
first deployment stage, Release Management is done, there is nothing left to do
within 60 seconds > The build status page is "waiting for deployment result..." for 5-7 minutes > Build status changes to "Build succeeded".
Does anybody know why the build takes 1 minute to build and deploy, but the "Build status" page doesn't update until 5 minutes later?
I am using TFS 2013.4, RM 2013.4, and Agent-based releases. My template is "ReleaseTfvcTemplate.12.xaml"
Edit: Also, this Release Template seems to ignore "Release Target Stage". I set "Release Target Stage" to "Development Staging" (my second stage) and it still went to "Development" (my first stage). I did not have this
problem with the 11.1 template. Should I use that instead?

I am going to change the verbosity of all the logs to the highest setting and get back with you.
However, I wanted to add some additional information to the problem before I do:
We are using CI and gated check-ins.
If I set "Release Build" to False, then the build completes in 30 seconds.
If I set "Release Build" to True, then the build completes in 30 seconds. Within 60 seconds I can usually check Release Management and see that the build is past the "Deploy" stage and in the "Validation" stage. Checking the
deployment directory confirms that it has deployed. Up until recently the build summary would show that build as a success almost immediately... now it hangs for 5 minutes.
Sometimes the build summary shows a failure due to a Release Exception DESPITE seeing that the release was successfully deployed in Release Management.
This is a huge problem because we use gated check-ins. This happens whether a check-in triggers the build or it's a manually triggered.
Screenshot 1 of build configuration:
Screenshot 2:

Deploy EAR file to OC4J from PL/SQL Store Procedure

Hi
Can you deploy an EAR File from PL/SQL Store Procedure?
are there any API'S to achieve that?
Thanks.

Customer has an IAS 10.1.3 Environment with multiple OC4J's for different projects.
We would like to allow each Project Team to be able to perform deployment on their own.
Problem is, that we want to be able to control which OC4J Container each project team can deploy to and restrict them from creating into other containers.
Although IAS 10.1.3 does allow you to define different users and groups, it doesnt allow you to restrict a user/group into one specific OC4J.
This is a big problem for customer and in the quest of searching some Creative Solutions, we wanted to try and create a simple Web UI (i.e, in APEX) that will allow customer to
upload new EAR (or WAR) file and it will deploy it to their container automatically.
to achieve this, we need to find (easy) way to deploy files from PL/SQL.
we can always use external pl/sql procedure that run a Shell Script which does this,
but customer is searching for a more "direct" way to do this.
any suggestions on this issue?

Release Management : Release template and deployment sequence per Server

Hello,
IS it possible to have a Deployment Sequence per Environment and not only per server ?
So if i add a new server on a same environnement , i don't have to copy and paste all the activities already configured .
Regards,
Issou
issou

Hi Issou,
Thanks for your post.
Yes, you can use the Tag feature to do that in Release Management, please refer to the helpful information in this article:
http://www.incyclesoftware.com/2014/02/new-feature-release-management-visual-studio-update-2-server-tags/.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Release Management - How to bring testing calls in the Release Pipeline

Dear Team
I had set up a new application release path using RM Client. The release pipeline contains deploying a new web site with IIS.
Using the release template - able to trigger build and deployment happens.
Question #1. In the Build log, the Quality tag is NOT assigned? What is the procedure to assign a quality tag?
In the deployment in QA Environment - launch also testing done - call automated tests from VSTS Coded UI like smoke suite, functional suite for execution and share results
Question #2: Is there any existing services call available or new component need to be developed.
Thanks in advance.

Hi VikramGopu,
I'd like to know the TFS version you're using. For your questions, please check the replies as below:
1. Build quality will not be assigned to a build result unless you choose the values manually. To get the TFS build result assigned a build quality, you can check the links below for more information:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/030a9cc7-4c91-4132-a9fa-0fbcf119218d/tfs2010-team-build-automatically-update-build-quality?forum=tfsbuild
http://stackoverflow.com/questions/19730128/tfs2010-automatically-set-build-quality
2. You can run the coded UI test by using Visual Studio locally or Microsoft Test Manager. If you want to run coded UI test in TFS build, you have to run the build service interactively. To run test duing the build/deployment process, you
can use command tools in Release Management to call mstest to run the tests. Whether you need to create a new component depends on your requirements. You can also refer to this
blog about run tests with Release Management.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a
href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

Front-End Service Starup Error: Store procedure to GET progress vector failed.

Hi,
We have a two front end servers in our Lync deployment and I'm getting an interesting error message on one of the servers when the "Lync Server Front-End Service" is starting up. All the services on that server will eventually start but I'm pretty
sure it's affecting users in some way.
Here is the error message in the Event Viewer:
Log Name:      Lync Server
Source:        LS User Services
Date:          2013-09-17 8:00:32 AM
Event ID:      32194
Task Category: (1006)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BGC-VAN-LYNC2.domain.ca
Description:
Store procedure to GET progress vector failed.
Execution Error: 0x00000000(ERROR_SUCCESS).
Native Error: 8144.
Error Details: [# [Microsoft][SQL Server Native Client 11.0][SQL Server]Procedure or function SyncReplicationGetProgressVector has too many arguments specified. #].
Cause: This may indicate a problem with connectivity to local database or some unknown product issue.
Resolution:
Ensure that connectivity to local database is proper. If the error persists, please contact product support with server traces.
Event Xml:
<Event xmlns=>
<System>
    <Provider Name="LS User Services" />
    <EventID Qualifiers="50158">32194</EventID>
    <Level>2</Level>
    <Task>1006</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-17T15:00:32.000000000Z" />
    <EventRecordID>16971</EventRecordID>
    <Channel>Lync Server</Channel>
    <Computer>BGC-VAN-LYNC2.domain.ca</Computer>
    <Security />
</System>
<EventData>
    <Data>0x00000000(ERROR_SUCCESS)</Data>
    <Data>8144</Data>
    <Data>[# [Microsoft][SQL Server Native Client 11.0][SQL Server]Procedure or function SyncReplicationGetProgressVector has too many arguments specified. #]</Data>
</EventData>
</Event>
The error happens 15 times every minute, following with this event:
Name:      Lync Server
Source:        LS User Services
Date:          2013-09-17 8:23:46 AM
Event ID:      32189
Task Category: (1006)
Level:         Information
Keywords:      Classic
User:          N/A
Description:
The following Fabric service for routing groups have been closed:
{F515134C-71B7-52FD-B0C3-6A9DB39CF750}
{8A5D6B36-2A01-53DB-BC4E-3286C05E0836}
{B35AAFC9-F6BF-5FFE-8C31-4AA5C36B2065}
{69223418-78DC-5066-81A8-78E05914EC7B}
{80414C96-1137-5DDC-8387-C3EA7A54B078}
{641E6ABD-B862-55A1-B1B1-C83BC92D2F85}
{1EA68EA4-77F7-5CFC-B781-0093CBC18403}
{2FDE333D-FF7F-5D6A-B85B-93ADC1EAC12A}
{A43BBA3A-8963-51C4-BD7A-19E1EC3DDFDB}
{D3F4532F-61C8-5072-9B3B-3E2CCF15442F}
{4449243E-5E96-56AC-AB6B-C5E785543542}
{58B30261-65B6-5F6A-BC50-60F85782D052}
{DB4B76B0-2510-5BF8-A7B1-8B37BD3AA7B9}
{917CC217-966B-56AC-A912-97BA64BA13EB}
Anyone knows what this is about and how to resolve this?
Thanks,
VH.

Hi,
Please try to reset registrar state:
http://tsoorad.blogspot.in/2013/04/lync-2013-ee-pool-wont-start.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Kent Huang
TechNet Community Support

Release management with Azure and Visual Studio Online (Cloud TFS)

What strategy would you use to manage the releasing of versioned software to Azure cloud services (web and worker roles)? We are not looking for continuous integration. We are using Visual Studio 2013 and Visual Studio Online (Cloud TFS).
At one point, we were releasing straight from Visual Studio using the Azure Cloud Project Publish tool. This is really bad practice in my opinion as you can never be sure what you are really releasing. Additionally, there is no automated control on the labeling
or branching of code, or the running of unit tests and code analysis checks.
Next, we employed Release builds on Visual Studio Online. Before deployment, one would edit the appropriate Build Definition (whether it be for Test or Production by and filling in the code label (under the "Get Version" build property) that is to
be released. This would then get the appropriate code (by the label specified), build it, and release it to whatever cloud service is specified in the targeted Cloud Project profile (this is using the AzureContinuousDeployment.11.xaml template).
There is still a degree of manual intervention involved. Also, the fact that a version of code is built every time before it is released is not ideal (as far as I understand it would be better if it was packaged once).
Microsoft Release Management tools
look ideal for the job, but are not supported with Visual Studio Online.
Is there a better way of handling our releases?

/waves hand.. These are not the tools you seek. You are looking for continuous integration.
Although CI has the word continuous in there, it does not mean "all the time, every checkin". It can easily refer only to those bits you want to release - -and the way to tell the system which bits you want released is to merge them to a Releases
branch.
If you do this, not only do you get all the joy of controlled CI, but you guarantee what you release is exactly what is controlled in your SCM - under the Releases branch, preferably tagged or otherwise noted as a particular release. That means you can also
rollback to a previous release by simply reverting to a previous release in your SCM!
Of course you don't have to let it happen automatically, you can set it up to build 'continually' and then remove the check on the SCM to see if any changes have been committed. You can replace this with the manual build button.

Release Management DACPAC deploy store procedures

Similar Messages

Maybe you are looking for