I have 2 issues going on with TFS.
We have 2 active directory roles set up for TFS and Visual Studio 2015: ADMINS and USERS. And we have one main Team Project.
We recently hired two contractors and added them to our USERS role. But what we have noticed is that on their machines, as soon as they start to edit the files, it shows as [lock, edit] where everyone else shows just [edit]. The primary difference that we know of is they have Windows 10 where the other developers are on Windows 7. I have been trying to troubleshoot this for the past week with no success. Any suggestions on what I can look at/query to find this? This isn't stopping us, but still having to workaround it.
Then mid morning one of these contractors was trying to edit some Shared Datasets. And now he keeps getting "Access to path [filepath] is denied" but so far it looks to only be happening on *.rsd and *.rds. He was able to create a Dataset, commit it to TFS. But then is unable to edit it. But he can then delete and commit the deletion to TFS. This is completely stopping him for working on these, so this is more of an issue currently.
I saw a post about checking the local file properties to see if it is read only. We did try to change the readonly setting. The file updated but it won't show in TFS Pending Changes or allow him to Undo the change. We currently have 3 solution with a ssrs project. He gets the same issue in all. I had another developer who is in the USERS role validate that she can edit.
Any suggestions on how I can trouble shoot these items is appreciated.
For the [lock, edit] issue, if the user select lock type (e.g Check in- ... Check Out-...) when Check Out for Edit... then it will show as [lock, edit].
For the "Access to path [filepath] is denied" issue, seems it's related to permission settings on your local machine or AD. So, please check if the user has the correct permission to access the the shared path/files. For the specific files, make sure they are not read-only.
To troubleshoot that, just try below things:
Try the contractor's account on other clients, (e.g on Windows 7) to
check if it has the same issue.
Try move the user from USERS role, then add the user separately
in TFS and give the corresponding permissions, then check if it has
the same issue.
Check Security and Version Control settings and make sure no
restrics.
Related
I recently downloaded Web2Project after going through the reviews. Installation was a breeze and the application is neatly aligned. I was able to create the users, assign permissions, create companies etc.
However when I am trying to create a project , despite filling all the fields in the screen the page just refreshes back without giving any error message or creating a project.
I am looking to see if there is a way to troubleshoot what is going on with the page. I tried exploring to create an account in Web2Project support forums but not able to create an account through the available media and hence seeking technical assistance through Stackoverflow.
Web2Project New Installation
Web2Project Code (Just installed on WAMP Server) -- Projects Module
After filling all the fields in the Project Screen, the project should be created.
But the screen just refreshes without creating the project. No errors shown. When I go to Project List page nothing is created.
I was facing same problem. Took a lot of work until realized that the cause was the field PROJECT_ID of the table PROJECTS was not created with the auto increment definition. I just seted up this property and the problem was solved.
How did i discover the cause of the problem? In the SYSTEM ADMIN module, access the SYSTEM CONFIGURATION page, and then set the value of the field DEBUG LEVEL to 1, and check the field SHOW DEBUG MESSAGES. This will allow the web2project to log into C:\Windows\Temp\PHP72x64_errors.log (in case of my instalation) the error.
Good luck!
I'm facing the same problem and took a lot time to solved until I came here.
Goto the table project immediately, found no auto_increment in project_id field. Put it on, it worked!
And hoping current web2Project maintainer will fix this in their installer.
Thank you!
I have been working on a submission form for two of our employees' to enter tax data. It is an InfoPath 2010 form, which is connecting to an Access 2010 accdb. The purpose of the form is to pull related data from two source tables (one from the old dB that was used, and the other from APX which houses additional information) to prefill as many fields as possible. Everything works fine when running it from my computer, or directly off our server. The problem I am running into now, is that our two users have access to the files, can open them with InfoPath Filler, but upon opening, they get the "InfoPath cannot connect to the data source...". The funny thing is, is that last week, they were able to connect and submit data with no problem (then one day I came back from lunch and it no longer worked). How I had to originally set them up was to create a certificate, make the forms full trust, added both user ID's as being able to have read write access. When I run the form from my desktop it works without a hitch. I even tried remapping to a mdb to see if it was a version issue. The dB is stored on a shared domain, \testdomain\, for arguments sake. Then they access the form via the same directory. Just to note, SharePoint is not connected in any way. All the searches I have done have yielded no solutions. I am thinking it is a networking issue, and have a meeting with the network admin in a few hours. But, what I can't figure out, is how it worked before, and not now. Does anyone have any suggestions or thoughts on what could be causing this? Just to clarify, I can run the same xsn form they run, from the same server location, without having the issue they do. I truly appreciate anything anyone might be able to offer!
Ok, finally figured out what was causing the problem (totally feel dumb). Apparently the servers used randomly get backed up, and when they do, the permissions get overwritten. If anyone else runs into this, review the access permissions for the directory and all the files. Thanks Nathan for your advice!
I’ve got a small problem. We’re using the ”Folder Redirection” feature (as a GPO) in windows server 2008R2 and that’s working as expected for all the users. It’s configured to ”Grant the user exclusive rights to documents”, for security reason. We don’t want to give every administrator right to look into other people’s home folder. As an example, a user (let’s call the user for User1) gets the following ACLs on the folder on the server:
CREATOR OWNER (group)
SYSTEM (group)
User1 (account)
This is as expected and no problem there. But now to the problem, when an administrator gets her/his home folder configured by windows, it’s getting:
CREATOR OWNER (group)
SYSTEM (group)
Administrators (group)
As a result all administrators can access each other’s home folders without a problem and this we would like to prevent. I've like to get the administrators own account as the owner of the folder, like it is with all normal users.
An administrator in our environment is a member of a group called “ADMIN” which got “Enterprise Admins” and a few other things in it.
Do anyone have the same problem? I’ve be grateful for any tips and tricks.
After some more digging, I’ve come across the problem. Our problem lies within an application that we use (own crafted application that communicate with AD). So this wouldn’t be a problem for anyone else, hopefully.
I'm creating an Access 2010 database and would like some clarification when it comes to concurrency and security. What I would like is upon starting the app only a menu form to be displayed with several buttons including a login button. Most buttons would be disabled until after the user logs in at which point based on their permission group; Viewer(Deafault), Worker, Editor, Admin.
Also, Admin should be the only one to be able to see the access database while the others are restricted to seeing the forms only.
I was just testing the default concurrency implementation but saving my database to a shared network and having myself and a co-worker try to access it. Found out if one accessed the database it locked it from others, and if we both tried at the same time it became read-only.
So I'm just looking for tips on how to start this.
For an Access database all users must have as a minimum read, write and modify permissions on the folder in which the database resides. This is because MS Access creates a lock file and if the second user does not have permissions to modify the lock file, the cannot get access to the database. Delete permissions may also be useful, to remove the lockfile when they are the last person out.
We have an access database on a file share that has permissions for everyone in the department to access. The problem i am having is that when multiple users try accessing the database at the same time they are unable to do this. One user can open the database fine but when another user tries to simultaneously, they double click the file icon, get an hour glass for a split second and nothing happens after. We are using Server 2003 as our domain controller. All permissions have been verified on both a domain level and in the access database under tools-options-advanced and setting relevent permissions to shared and no locks. Do you know what could be causing this issue with a "dead link" when user try to open the file simulateneously?
Any help is greatly appreciated.
Thanks.
Ignore the naysayers - Access is perfectly fine for a small number of users. Either you have the default Access settings to open dbs exclusive which will lock out other users or there is some weird network problem.
EDIT
- noticed you already have default shared access
- is record-level locking on?
- also try giving user full control of the shared network folder (Access needs read/write/create/delete to be able to create and delete the ldb file)
This issue occasionally happens to Access databases for almost no apparent reason. Of the suggested responses by Microsoft, you are already doing the second (opening from within Access) but I believe the first provides somewhat of the answer you are looking for.
In the target of the shortcut, include
the path of MSAccess.exe
According to Microsoft Help and Support
When you say share permissions, do the users have full permissions? Full permissions are needed because the share file (.ldb) must be created and deleted.
I am just recently experiencing the same issues, only one person can open the database. We only have 3 people accessing the same database through shorcuts on our desktop.
Now according to Microsoft we need to include the database path in our shortcut, I will tried that. They acknowledge this problem.
MS Access is not worth the trouble in a multi-user setup.
Your time is better spent converting the database over to a server-based RDBMS such as SQL server while you still have hair.
Believe me, you will have to do it sooner or later anyway! Sorry for the bad news.