I am trying to create table and page Navision through visual studio code. but I am finding an error in this process. Can anyone help me?
Error: Could not open the specified startup page. Please check that the server configuration key PublicWebBaseUrl has been properly set.
I'm using Navision 2018.
I had the same error. You need to set the PublicWebBaseUrl property. You can do this in two places:
Edit the config file of the nav service you are trying to connect to
In the server administrator app the same property is under Client
Services tab called "Web Client Base Url".
Here it is in the Server Administration
You have to do the following 3 Steps:
Set the PublicWebBaseUrl property. Edit the config file of your service or use the Administration-App (there you set the "Web Client Base Url" under Client Services). You set it to HTTP://<Servername>:<Port>/<Instancename> (depending on your configuration, but Port should be 8080).
Restart the Service (obviously)
Restart Visual Studio Code. Yes, that is a not very intuitive, but a really crucial step.
After that, you should be able to publish to the Server without problems.
Related
I am setting up ColdFusion 2018 Application server with IIS 10. But getting too many redirects issue.
I have tried from square one.. Below are the things I did.
Installed CF 2018 developer
Configure IIS (Windows 10) with CF 2018 using wsconfig.
Created a simple “index.cfm” and tried to access. This page contains just cfset and cfoutput.
got 404 error.
updated “enable 32-bit applications” to false in IIS application pool
404 error resolved, but getting “Too Many redirects issue”
enabled developer tools in IE and checked.
getting 302 status code and it seems index.cfm is redirecting to itself.
Not sure what to do now? Is there anything I missed in setting up IIS with CF 2018 server?
You can resolve this error by making sure that the two required components of IIS are installed on your system. Namely:
ISAPI Extensions
IIS Metabase and IIS 6 configuration compatibility.
First, start the program called Windows Features. You will find Windows Features under Control Panel –> Programs and Features.
When the Windows Features starts, navigate through the features hierarchy under Internet Information Services and select the two features:
(a) ISAPI extensions and
(b) IIS Metabase and IIS 6 configuration compatibility.
Configuring IIS for ColdFusion:
You will have to run the Web Server Configuration Tool that comes with ColdFusion to configure IIS so that all .CFM files are mapped to be handled by ColdFusion.
The following text is directly from the ColdFusion installation guide:
1)Start the Web Server Configuration Tool by selecting Start > Programs > Adobe > ColdFusion 9 > Web Server Configuration Tool.
2)Click Add.
3)In the Server pop-up menu, select the host name and the server or cluster name to configure. In the ColdFusion server configuration, the server name is always coldfusion. Clustering support is not available on the server configuration.
Note: The server or cluster does not have to reside on the web server computer.
4)In the Web Server Properties area, select IIS and specify the website. For IIS, you typically specify All.
5)Select the Configure web server for ColdFusion applications option, and click OK.
Note: Omitting the previous step causes your web server to serve ColdFusion source code.
6)Copy the CFIDE and cfdocs directories from cf_root/wwwroot to your web server root directory. In addition, copy your application’s CFM pages from cf_root/wwwroot to your web server root directory. In the multiserver configuration, these files are under the jrun_root/servers/cfusion/cfusion-ear/cfusion-war directory.
if you face too many redirects then just enable 32-bit applications to true.
refer this link:
https://community.adobe.com/t5/coldfusion/strange-iis-redirect-issues-leads-to-jakarta-isapi-redirect-dll/td-p/4239297?page=1
I try to deploy my Word web add-on that created by Visual Studio 2017 using the Slideloading method.
When I upload the manifest file the message it gives to me seems fine saying:
Get started with your sample add-in!
Your sample add-in loaded successfully. Go to the HOME tab and click 'Show Taskpane' button to get started.
but when I go to use it, it fails saying:
Add-in Error Sorry, but we can't start this app because it isn't set up properly.
Although I followed the sideloading method well and changed the source location default value to: <SourceLocation DefaultValue="https://localhost:44300/App/Home/Home.html" />
Besides this method worked well by OfficeApp manifest.
If you created your add-in using Visual Studio and just want to test it, you can run/load the add-in simply by using F5 (Start) within the Visual Studio project. When you press F5 to start the project, Visual Studio will automatically host the add-in on your local IIS server and will open Word with the Show Taskpane button visible in the Home tab. The Word add-in quickstart describes this process in more detail. (Note: if you're using Visual Studio to run the add-in like I've described here, you shouldn't modify the localhost port number within the DefaultValue attribute of the SourceLocation element in the manifest.)
If you created your add-in using Visual Studio but want to be able to run it by using the Sideloading technique (i.e., without using Visual Studio), then you'll need to deploy the web application portion of the add-in to a web server. In your post, you say that you've specified https://localhost:44300/App/Home/Home.html as the initial page of your add-in. If you navigate to that URL using a web browser, does the page load successfully (with no certificate errors)? If not, that could indicate a problem with your web app -- for example, perhaps there is no web server running at localhost:44300, or perhaps the web server is running but there is no such path as App/Home/Home.html, or perhaps the web server is running and that is a valid path but the add-in web app isn't SSL-secured.
How can I add an external TFS Connection to TFS 2017 to allow it to connect to TFS 2013?
I navigated to http://tfsserver:8080/tfs/collection/team_project_name/_admin/_services?_a=resources and clicked New Service Endpoint. I selected External TFS
When I go to verify the connection after entering all the relevant information, I get the below error.
Failed to query service endpoint api: http://tfsserver:8080/tfs/collection/_apis/projects. Error Message: The remote server returned an error: (401) Unauthorized..
Here is a screenshot of the error.
The odd thing is that if I make a GET request to http://tfsserver:8080/tfs/collection/_apis/projects without any authentication I get a 200 OK response back with project information.
I have configured basic authentication per the tfs cli guide. How can I verify that basic authentication is configured correctly? When I try to login with tfx, I get the following screen.
I have the following extensions installed on the TFS 2017 instance.
Package Management
Release Management Utility tasks
TFS artifacts for Release Management
I am using Microsoft Visual Studio Team Foundation Server Version 15.105.25910.0
According to the screenshot, you are using TFS artifacts for Release Management extension to connect to another TFS instance.
Make sure the things below:
Make sure the collection URL you enter is correct. In your screenshot, the URL you enter is ended with "_home".
Make sure Basic Auth is enabled on TFS server.
Seems you are using the extension TFS artifacts for Release Management which provides a service endpoint to connect to an external TFS or VS Team Services Collection.
After test with TFS2013, I could reproduce your issue and got the same error information. The solution please see below:
Since you are connecting to TFS2013, it works with basic
authentication only. You’ll need to enable basic authentication
support for the TFS Server which handling TFS2013.
Also please make sure the username to connect to the external TFS
collection are with Domain in front of. Then will get a green
verfifed status.
(I am very new to deploying in a dedicated server.)
I have access to Windows Server 2012 through as Remote Login.
I have to deploy my html, js files to the server and then access my html page through a URL.
I am not sure where should I keep my files in the server, launch the server and then access my page through a URL.
In my local server in my machine, I kept the files in
C:\inetpub\wwwroot
And I gave access to others to my page through :
http://myIPaddress/mypage.html
Please suggest where should I keep my code and how can I launch the server.
If anyone can point me to a documentation, even that would be great.
Thank you.
First create web app on the server,
then you can choose any destintion folder for the project.
Follow this documentation
https://msdn.microsoft.com/en-us/library/vstudio/dd394698(v=vs.100).aspx
We need to enable IIS first before deploying our files in Windows Server 2012.
I went through the following document I found in Microsoft website. It was very helpful.
https://technet.microsoft.com/en-us/library/hh831515.aspx
I developed a sample application in visual studio 2010. I created an Empty SharePoint Project and gave the local site url for debugging. Checked "Deploy as Farm" as the trust level of the SharePoint solution. Added a visual webpart and also a class to the solution. I am able to build and successfully run the application using visual studio. In my local machine am using SharePoint foundation 2010 to debug the SharePoint application.
Now i want to deploy this application in the SharePoint server 2010 which is in a virtual machine.
1. I copied the .wsp file of the application i created to the virtual machine.
2. From the central administrator in the VM I created a web application and the site collection.
3. Then using Site Actions -> Site Settings -> Solution(Galleries), choose the .wsp file for uploading. it showed a "Warning: You should only activate this solution if you trust this solution. An activated solution can read, modify and delete your data. " and the activate button is disabled.
Then I tried to do same in my local machine on a different site collection. Here Activate button is enabled but when clicked it threw exception
Server Error in '/' Application.
This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'aee60282-765d-4c9f-b67a-5981f18a6d3b' failed validation, file manifest.xml, line 10, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'.
What could be this error?
The "TemplateFiles" element refers to items that will be copied onto the web server. This is allowed for farm solutions (which are deployed via CentralAdmin), but is not allowed for sandboxed solutions (which are deployed via the Solution Gallery).
When you deploy your wsp with visual studio, you deploy it as farm solution.
When you deploy your wsp from site settings into solution galery, you deploy it as user solution (sandbox solution) with some limitations :
first, avoid using out of the box visual webparts, it's prohibited !
Deploy your wsp by writing powershell script.
A good starting point here :
patrickboom.wordpress.com/2010/05/31/using-powershell-to-deploy-sharepoint-solutions-wsp-2/
Le_Fredo is correct here, when attempting to deploy a WSP file into the site collection directly under the site settings, you won't be able to. I found this article from microsoft to be extermely helpful
http://technet.microsoft.com/en-us/library/ff607688(v=office.14).aspx