How can I go about obtaining the latest WSDL files from a CRM4 deployment?
Currently we have a deployment in place on a hosted solution where there are two WSDL files available via Settings > Customization > Download Web Service Description Files
From this location there are two files available:
- CrmService.asmx
- MetadataService.asmx
If I attempt to click on these files then it opens web URLs as follows:
- http://be-crm4.domain.co.uk/MSCrmServices/2007/CrmServiceWsdl.aspx
- http://be-crm4.domain.co.uk/MSCrmServices/2007/MetadataService.asmx?WSDL
However upon looking at the visual studio C# coded connector tool that interacts with the current CRM instance that a previous developer has done I can see that he has reference to 3 WSDL.
CrmService
CRMMetaService
CrmDiscoveryService
The Discovery service URL is as follows:
- http://be-sql-live01/MSCRMServices/2007/AD/CrmDiscoveryService.asmx
We are currently in the process of moving our server to another server and I am testing the webservice component of this but as there have been changes I want to regenerate the WSDL files.
How can I save the wsdl files from the browser? How can I find the discovery URL of the webservices as only 2 of these seem to be appearing
I know it's a bit late but maybe someone will find this helpfull.
On on-permise instane using AD the address for discovery service is:
http[s]://<hostname>[:port]/mscrmservices/2007/AD/CrmDiscoveryService.asmx
On IFD instance:
http[s]://<hostname>[:port]/mscrmservices/2007/IFD/CrmDiscoveryService.asmx
You can get WSDL by adding ?WSDL on the end of webservice address for example:
http[s]://<hostname>[:port]/mscrmservices/2007/AD/CrmDiscoveryService.asmx?WSDL
Related
I have an existing deployed ASP.NET MVC3 application using Entity Framework 4.1 and .NET 4 that I need to copy onto a new server. Problem is I have little or no documentation about how the deployed environment was configured. On the up side I do administrator access to the deployment environment and full access to the source code to the application.
So starting from bare metal I have:
Fresh install of Windows Server 2012, SQL Server 2014 Enterprise
Installed MVC 3 and Tools via Web Platform Installer
Copied entire website from existing deployment to its own folder under C:\inetpub
Added website under IIS and started it with the App Pool configured as
Browse to website and it returns the default.htm page in the root folder. This is not expected behaviour as it should serve up the default controller view.
Check to see that I can access a html file elsewhere within the website eg. http://myhost.com:443/SomeDir/test.htm and it serves that up
See if it will hit a route I know exists eg. http://myhost.com:443/Auth/NewLogin and I get
Various readings indicate that occasionally this is caused by "UrlRoutingModule-4.0" not being installed in modules. It wasn't so I added same server wide and ensure it was present for the website (Made no difference):
There is also mention of ensuring runAllManagedModulesForAllRequests="true" was present in the web.config which it is
UPDATE
.NET is installed:
So before I post a "Failed Request Trace" can anyone give me any suggestions on how I proceed to get MVC working in this environment?
I have read may SO posts and Googled but nothing seems to work.
I'm struggling with finding a good way not to check my secret passwords into my web.config.production type files (the ones that get transformed when Web Deploy publish is done). my workflow is that my team checks in and out of github and then when we are ready to do a production deployment, we have a custom web.config.deployment configuration that has all our real passwords in it. The problem is that all developers see those passwords.
I'm looking for suggestions for how to not have to put those passwords into our github repository with as a little friction as possible. That is, now, we have to rdp into our web server and manually change those passwords. Azure let's you set them in the azure portal, but we are not using azure.
One option is to store these app settings\connection strings in IIS. Then they will be applied to the web.config at start up and only members with access to your IIS administration can access them.
See these post:
http://forum.winhost.com/threads/setup-the-connection-string-in-web-config.7592/
http://technet.microsoft.com/en-us/library/cc753224(v=ws.10).aspx
app settings – Specify name/value pairs that will be loaded by your web application on start up. For .NET sites, these settings will be injected into your .NET configuration AppSettings at runtime, overriding existing settings.
connection strings – View connection strings for linked resources. For .NET sites, these connection strings will be injected into your .NET configuration connectionStrings settings at runtime, overriding existing entries where the key equals the linked database name.
I have a solution that contains multiple integration test projects and one web application project. each integration project connects to the web application when running the tests. I would like for each test project to access the website with its own database connection. I have been trying to use the web deploy functionality built into visual studio. However I have been unable to figure out what I need to add to either the deployment package that is created and/or the post build event for the test projects to declare the binding port for the website when deployed. For example, I want integration project A to create and access the website located at http://localhost:83 and integration project B to create and access the website located at http://localhost:82. Could someone please explain:
Is there anything I need to do the deployment package ?
What do I need to add to my post-build events for my integration projects when deploying the package, so that the website is created at the correct port when building the project?
Update:
I'm wanting to deploy the same site to two different locations on my machine so that I can run both sets of integration tests at the same time.
Update 2:
I have researched the web deploy tool and it allows you to specify parameters that modify what is deployed when you call it from the command line. However I have found the documentation very confusing. http://technet.microsoft.com/en-us/library/dd568968(WS.10).aspx
Update 3:
I expect these to be two different websites, each pointing to there own database. If possible I would like a single package that can be deployed using msdeploy. Which will then be called in a post build event from each of the integration test projects. I would like to specify the connection string and deployment location from the post build script of the integration project.
you can try with webdev.server included in visual studio. VisualStudio use this for start a webserver when you debug. With this you can start a webserver in the desire port (if the port is not used currently).
I made a bat file for change some options.
check it.
::Begin of bat file
cd C:\Program Files\Common Files\microsoft shared\DevServer\10.0\
WebDev.WebServer40.exe /port:80 /path:"C:\PATHTOYOURWEBPROJECT" /vpath:"/NAMEOFYOURWEBPROJECT"
::End of bat file
You can acces in: http://localhost:80
I use the webserver40, but if you don't have net.4 or vs2010 you can try to find webserver[ xx version].exe
I hope that this will be helpful, and sorry for my broken english.
First off, you're approaching this the wrong way.
> I would like for each test project to access the website with its
own database connection.
Who is creating the DB connection? Your web site or the test project? For rest of your question to make sense, I presume its the web site (otherwise, Project A and Project B cannot share a connection out of the box).
If your website is making the connection, unless you're caching or having a static connection, there will be a new connection made as each request runs your your site on a new thread. Another simpler alternative is to take a query param and initiate a new connection based on that. If you seed it off the caller, you can also use it for more detailed logging.
Web Deployment projects are meant for deploying to integration servers, so that means you cannot access them by http://localhost... but the full FQDN of the server.
Most importantly, http://localhost:82/myApp and http://localhost:83/myApp are two different sites (unless you redirect from one of them to another one which in itself can cause additional issues) running the same codebase.
Having said that, you would then need to deploy your website twice and then all you need is to change the config/settings entry in Project A and B to point to these to different sites.
Hope this makes sense.
You can define virtual host configuration.
Refer this guide for more information.
http://docs.jboss.org/jbossas/guides/webguide/r2/en/html/ch07.html
How can I simultaneously access my .db4o database from the Visual Studio's Object Manager Enterprise (OME) db4o plugin and from my application?
I'm starting out with db4o, integrating it with an ASP.NET MVC application. I have a two-layer repository access pattern set up using StructureMap for IoC and I keep getting DatabaseFileLockedException erros in VS when debugging while using OME.
When you want to access a db4o database file from multiple applications at the same time, you need the client-server-mode. So, either your application or a special "db-server only" application has to open the file as server, then both your application and the OME should be able to connect to this server.
The documentation has an example for this.
I never used OME, so I have no idea how to configure it there.
I am trying to create a custom workflow in ms crm 4 so that when a task is completed it will take some of the attributes of the task and add an entry in project server on a timesheet. I am able to access the project server web services (PSI) and create a time sheet entry from a c# console app and I can do other custom workflows in crm not related to project server. When using the Project Server web services (PSI) I have to reference and include 3 office project dll's but I am unsure how to get those registered in CRM when i do the custom workflow plugin registration. Any thoughts would be helpful.
Thanks
In my experience, you're either going to have to deploy those DLL's to the Server\bin directory or merge them with your DLL using something like ILMerge and register it all as one big chunk.