I have an Access web database (the out-of-the-box Project one) and plan to move to another Sharepoint site (a test server). I have done lots of googling and nothing comes up. Any pointers will be greatly appreciated.
Thanks.
After some trials and errors, I figured out how to do that. First open the Access web db in Access client. Then go to Publish & Save, where you should see an option Save As Local Database. Then open the local database, again go to Publish & Save, you can choose to Publish to Access Services. A pane will appear to let you enter the URL of Sharepoint server and site name. If you have customizations or lots of lookups, there's a good possibility it will not publish. If that's the case, you just need to fix all the errors reported.
I was able to move my Access 2016 app to a new Sharepoint Site by saving it as a .app and uploading it to the new site.
I found this link to Microsoft's site helpful: Create an Access app package
Related
i want to host a vb project from a sharepoint folder instead of having it locally installed.
I am still new at this, but I only need to host the files in the same folder on sharepoint right? And then whoever can just click the .exe file, correct?
Sorry if this is a dumb question!
Thanks in advance
As already mentioned in the comment SharePoint isn't meant to store or even display applications (.exe). What started as a security measure is now part of the philosophy of MS SharePoint. Here's a list of all filetypes SP13 will block by default.
Back to your question. There is a trick how you still can upload an .exe to SharePoint:
Store the application in a folder
Zip the folder
Upload the zipped folder to a document library
Display the library on the desired site
For the future..
As there is a "Silverlight Webpart" - develop silverlight application if you know from the beginning that you want to display them on SharePoint.
Another trick: Publish your application on a host server. Then use the "Site Viewer WebPart" and point it to your application
Last one, although I wouldn't suggest it.. You can develop a .wpf-application and simply upload it as the file-type isn't blocked. But to embed the resources is just a pain in the ass..
There are for sure many other ways to do this.. Those are just the most practical ones I know if you already developed the application. The best solution is of course to create your own WebPart..
Ok,
First of all, I want to make the disclaimer that aside from some HTML I have done very little programming in my lifetime. However, as necessity so often dictates, I am in dire need of some assistance with that very thing at this moment.
Our agency has a web site that is hosted by another entity, and that entity is forcing our hand in moving the content of that site onto one of our own servers. All content has been moved to the new server, and all database tables from the old database have been moved onto our internal SQL server. The site primarily consists of asp files, but there is one page that is aspx. The problem arises when taking the "old" database tables offline and testing the aspx page. Even though all instances of the IP address to the old SQL server have been changed to reflect the IP of the new SQL server, the aspx page insists on requiring the connection to the old database (the error indicates the tables are offline, thus pointing to the old SQL server). Everything else works as it should, and the "Web Application" has been designated as such in IIS.
I know I am missing something somewhere... but I just can't put my finger on it. Any ideas would be greatly appreciated. I'm starting to wonder if the reference to the old IP address is compiled in a file somewhere that I just can't find.
Thanks
Ok guys, I found my solution. For programmers, this solution probably would have been a no-brainer, but for others maybe not so much.
I have to give a pat on the back to "Creator" for pointing me in the direction of the project file. I wasn't sure that it was still available, but thankfully the programmer who designed this application somewhere a little over ten years ago was nice enough to leave it in the web directory with everything else.
What I wound up doing was as follows:
Opened the project file in Visual Studio 2010 and converted the project from 2003 to 2010.
Added the connection strings into the web.config to the new SQL server.
Right clicked on each item and excluded all of the old pieces to the application (in Solution Explorer) that were no longer needed.
Right clicked on the project and navigated to Package/Publish Settings > Package/Publish SQL and chose to "Import from Web.config".
Saved the project, then right clicked and "Converted to Web Application".
Right clicked and performed a "Build". I'm guessing this re-wrote the dll file.
Copied the directory and needed files back over to the web server and converted the directory in IIS to a Web Application.
Sat back and marveled at my success.
Thank you guys for pointing me the right direction!
Dashboard designer error:
The url is not available,does not reference a sharepoint site, or you
do not have permission to connect
This is happening to the site collections under one web application only in the whole Farm. Other web applications are working fine and I can open site collections through dashboard designer.
Any suggestions????
Unattended acc is all set, Site feature is activated, site collection is added to trusted location. On database side, app pool acc has db owner access to web app db. PPS is db owner there as well.
I think this indicates to a deployment issue on this app. Maybe something went wrong when deploying webparts, the assemblies couldnt be registered or were not copied correctly. It could also be a specific access restriction issue in SharePoint or in the file system that SharePoint relies on.
Without any log information it is hard to say what is really the problem - but - have a look at windows event log for any further indications, the general log files that sharepoint/asp.net write or also consider using monitoring tools that can tell you more details on what is happening here.
I recently wrote a blog on top deployment mistakes in SharePoint. I highlight exactly these deployment mistakes in more details: Link
Andi
This is my first time trying to edit a sharepoint file. It is used as a list of links in an iframe on a web site on another server. But this has nothing to do with the problem. I have been asked to modify the list of links and I just want to get to it and do it. But however one does this, it does not seem very intuative to me.
Let me tell you the steps I have taken and how things go wrong and maybe I can get some advice. The sharepoint file is on a server that I log into remotely. I run the "Sharepoint 2010 Central Administration". On the page that comes up, I click on "Manage web applications" under "Application Management".
From there, I see the page I want to edit. But when I click on the name of the item (which appears in red text) the area is hilighted but nothing happens. In the ribbon menu at the top of the page there is a drop down entitled "Site Actions" but there is no option there to "edit". Please advice.
I was given a username and password to "log in" because I was told I need that. The idea was that maybe I need a special admin account to see the missing menu options to edit a page. But at first I could not use it to log on to the server where the sharepoint system is. Then I found that I could try to use it to log onto the "Sharepoint 2010 Central Administration" program. But this did not work.
Then I tried to see if there was anything I could so from the desktop computer. I found "Microsoft SharePoint Workspace 2010"
I tried this and it looked promising"
http://i67.photobucket.com/albums/h292/Athono/SSO/SSO3_zpse15402e2.jpg
But then eventhough I could see the file name, I could not edit the file:
http://i67.photobucket.com/albums/h292/Athono/SSO/SSO4_zpsca7d0f71.jpg
I went back to the server and tried a few other things. I tried to switch my account in the Central Adminstration to this special account that someone suggested had more privledges but it did not work. The error said "Error: Access Denied". I tried putting the web page in the address bar and that just brought up the page without any way of editing it.
Please advise.
Central Administration is not meant for content editting. That is the core of SharePoint with all kind of configuration options.
You have to create a web application for content editting and create a site collection there. In that site collection you can edit the page, add webparts, etc. In your case you can try a Publishing Portal template for your site collection and add a content editor webpart. In that content editor webpart you can put HTML for your iframe.
I am trying to save an Excel 2010 file to a Sahrepoint 2010 document library but keep getting the error:
"You can't open this location using this program. Please try a different location"
Googling this suggests enabling "Desktop Experience" on the server which I have done. All Excel services are activated.
Has anyone come across this and been able to resolve successfully? I am wondering if this is more security related but the security set-up looks fine.
Any suggestions?
Thanks
I think that there are potentially a couple of things that could solve this problem depending on your set-up.
You are right that a lot of internet advice is to enable desktop experience, but if you are not running on the server or if you have already done this then one of the suggestions below could help.
This is only for dev environments however.
If you are running on the server and trying to use your app as admin then configuring IE ESC to turn off enhanced security for Admins should help
If you are running off server and have the issue and do not want to turn off IE ESC (on the server) for users then you need to enable a mechanism to allow auto-logon, either through integrated security (i.e. you are part of the domain), accessing through an anon web-site port on your SharePoint app (set-up anon web access in SharePoint) or set up and store a WebDav link and use that as the open/save URL.
My (unconfirmed) theory is that there is some auto-login going on in the background that hinders a streamlined office integration. Most of the time, SharePoint will be set up with Kerberos (not NTLM) or be in anon mode so enabling desktop experience if running on the server will be the best first step to try.
Hope this helps.
The problem is that the full path to the file is too long.
I had this problem with a PowerPoint presentation. The full path to the file was over 275 characters. When I shortened the file name to bring the full path under 250 characters, I was able to open the file normally.