I am using Sharepoint Designer 2007. I cannot add new workflow or amend existing workflow. I am using Windows Server 2008 R2. I have tried the following post. But I cannot get the directory specified.
Other users can access the workflow, but it happens only for me.
Tried This Link
Did anyone have this issue.
Try to update your office 2007 with the latest Microsoft patches. I remember having this problem before but don't remember how I fixed it! :(
Related
Is following scenario possible?
We have got TFS 2013 installed as a standard single server. This server has got the SQL db.
We have got SharePoint 2013 installed on another machine.
Now we want to integrate TFS 2013 with SharePoint 2013 along with SSRS and SSAS for reports, etc.
Please guide whether this is possible or we need to install TFS via Advanced mode again?
No problem, you can integrate your existing TFS single server deployment with your external SharePoint server assuming you have the necessary permissions.
MSDN: Verify your SharePoint installation
https://msdn.microsoft.com/library/dd578601(v=vs.120).aspx
MSDN: Set up remote SharePoint
https://msdn.microsoft.com/library/hh548140(v=vs.120).aspx
Cheers
Adding SSRS and SSAS is relatively simple too and can be on the same server as TFS or a different one.
MSDN: Add a report server
https://msdn.microsoft.com/en-gb/library/dn148128.aspx
Martin Hinshelwood has a couple of useful blog posts on this subject too:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
*sorry for the multiple answers, new account and SO doesn't trust me to post 5 links yet! :)
We are currently using TFS 2010 and have a Team site of SharePoint 2007. We are currently not using the Team site (we tried out a few things but at the moment its no problem to just remove it).
But we want to use the Team site and thought that we might as well upgrade it to 2010 before starting to use it. Its probably easier to upgrade from a pretty clean install than doing it later.
So.. Is it best to upgrade our site.. or should we maybe install a new SharePoint 2010 on the side and then switch over to that?
Any suggestions on which approach i should take. What is easiest (I don't know if I need to install anything special for Team site than other SharePoint sites)
PS. I am a newbie when it comes to SharePoint but can get some more experienced help if needed.
Easiest way would be to install a new Sharepoint 2010 instance somewhere and point TFS to that. To set it up you need to install SP 2010, then install the SP TFS Extensions off the TFS Install DVD, then fire up TFS Admin console and use it to configure the SP site. More detailed instructions can be found here: http://blog.hinshelwood.com/integrate-sharepoint-2010-with-team-foundation-server-2010/
Once you've got it configured it will auto-create Team Portals for any new Team Projects. If you wish to create Portals for pre-existing Team Projects there is a manual step you need to take that is described here: http://blogs.msdn.com/b/greggboer/archive/2010/02/24/creating-sharepoint-portals-reports-and-upgrading-reports-for-an-existing-team-project.aspx
Figured I'd throw this out here because in-house because in-house ITS and myself can't figure it out at all.
I have some Access 2007 front-end forms connected to lists in Sharepoint 2010. I updated the columns in a few of the lists in Sharepoint. On some workstations, the lists that were updated cannot be opened in Access anymore. However, they can still be opened directly from the Sharepoint web portal.
Does anyone have any idea what might be going on? Does Access have some sort of hidden cache of the structure of Sharepoint lists? We've tried all the obvious such as deleting and relinking and refreshing the culprit lists. All the computers in question are running the same version of Access and the same version of Windows.
Figured I would post what happened just for the record.
We are using Sharepoint Server 2010 and Access 2007. The problem was being caused by miscommunication between the two versions. We temporarily fixed it by installing Sharepoint Designer on all the workstations that needed the Sharepoint app, as this updated some of the Office 2007 files to Office 2010 and allowed compatibility with Sharepoint 2010.
Unfortunately, each time Microsoft rolled out an update to Office 2007, it broke the compatibility again, and after one update I was not able to fix it again. I have since moved to a MySQL/PHP platform and never plan on looking at Sharepoint again as a database platform.
I'm new to SharePoint and I'm creating a public website using SharePoint Server 2007.
I want to create solution or installer of my SharePoint website to copy it to another server other then my local machine.
Anyone helps me out to solve this problem.
Thanks.
You could have a look at SharePoint Installer. Very useful to create installer .exe from a SharePoint Solution. Especially useful if you use WSPBuilder.
With these 2 tools, you can create a setup project in no time at all (2 steps).
Assuming you know SharePoint, I'd advise looking at the SharePoint extension for Visual Studio at Microsoft downloads
How to fix this error in SharePoint:
"The list cannot be displayed in
Datasheet view. A datasheet component
compatible with Windows SharePoint
Services is not installed, your
browser does not support ActiveX
controls, or support for ActiveX
controls
It started to days ago, for apparently no reason. ActiveX is enabled on this site and I had everything working fine so far. Not sure what went wrong.
Thanks,
... from IE check out your Internet Options, and look under 'Programs'->'Manage Add-Ons'
When I had this problem it was because an add-on was missing or disabled... * thinks * "Microsoft Office List 12.0" or something.
I was getting the below in SharePoint 2010.
The Standard View of your list is being displayed because your browser
does not support running ActiveX controls.
Turns out the site (master page) was being rendered in IE9 mode and the datasheet supports only up to IE8.
The datasheet mode can be used temporarily by switching the Document mode and the User agent string both to IE 8, or permanently by using the meta tag X-UA-Compatible IE=8.
This is known issue and you have to install the hotfix provided by Microsoft.
The issue is addressed in the below specified link along with the URL for the hotfix.
http://www.himmeltech.com/blog/fix-for-datasheet-view-issue-error-in-sharepoint-2010/
Let me know whether the suggested solution fixes your issue
Please install below data connectivity component to resolve this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
This link helped me and it worked fine. Our environment was Windows 7 64bit and MS office 64bit as well, after installing this connectivity tools, user had a option edit the data sheet view in sharepoint.
I ran into the same issue after updating to Office 365 but remaining with IE 11 and Sharepoint 2010.
Issue:
using a 64-bit version of Office with a 32-bit version of IE
Reference: Technet
Resolution: Installed 2007 Office System Driver: Data
Connectivity Components
Seems like a client/browser problem.. do you have Microsoft Office installed? Did you change security settings in Internet Explorer?
My environment is SP2010 enterprise and after trying several solutions, I realized that the user that could not see the views in Datasheet style was because did not have installed "Microsoft Access" that is required when you are using views in datasheet style. So the solution for me was to upgrade that specific user from Office Standard to Office Professional
For me, I performed the following and it worked for me:
Open Control Panel and open Programs and Features
Find your instance of Microsoft Office and select it
Click change at the top
On the dialog that comes up, click Add or Remove Features and then continue
Make sure Microsoft Access Web Datasheet Component is installed under Office Tools/Microsoft SharePoint Foundation Support
Even if it is showing as installed, click Continue.
Let everything install, close any office programs out, then try again
These steps worked for me.