So am trying to open work items in Excel on my machine (TFS 2010 and Excel 2007) and I received original error from Excel
TF80070: Team Foundation encountered an error while performing the operation.
I found instructions on how to turn on diagnostics to find the underlying cause which is the error in the title
TF249051: No URL can be found that corresponds to the following server name
I cannot find anywhere in Excel that I can tweak the settings. How can I resolve this issue?
So the solution I found (after disabling and re-enabling the addin inside Excel and also removing the addin from inside Excel and re-adding it) was to go to the Team menu in Excel and click New List. It prompted me to connect to my collection which I did and then opened up a query (My Tasks). I guess somehow it didn't know exactly what to connect to although the complete error message I got from the diagnostic trace included the correct tfs server name and default collection name.
Related
In order to create an indipendent runtime file.accdr out of a file.accdb, I've downloaded AccessDeveloperExtensions.exe and AccessRuntime.exe and installed them.
Update:
See article Here is the Google Translater .
Update end.
Opening Access 2007 I could create the install package for creating the file.accdr out of the file.accdb.
The problem I get is that an important function does not work anymore. It's the export of a report, wherelse the export of a table still works.
Opening Access I get the following message:
you don't have a source code control program (such as Microsoft Visual Source Safe) installed on
your machine. The source code control commands are therefore not available
I click on OK and Access opens my db.
My db is based on a table, a form, a report and a query. Exporting the report worked in the past, but doesn't work anymore. The message shown is the following:
Impossible to complete output operation. Assure that there are no syntax errors. If the syntax is
correct, reinstall Microsoft Office Accept...
(I've translated the text from Italian).
Now is there another, easier way from reinstalling the hole thing? Because after reinstalling Access I will also have the need of creating databases.accdr and so I have reinstall runtime.exe and DeveloperExtensions again, what would result in the same problems I had before.
Somebody could help?
I have a MS Access Database Frontend that contains a large body of macros, queries, and custom VBA code. This frontend connects through linked tables to our backend access database. In order to allow multiple users to use the database we publish an ACCDE version. For some reason macros are not being included in this published version. Normally you can't see the code but the module names are always listed. This is completely blank, no macros, no vba, and auto exec fails to call a few custom functions as well. VBA code is simply not included.
I've tried:
Compiling the VBA Code -> Works without errors and publishing still doesn't include macros
Saving my frontend as a new file and then publishing
Compact and Repair
Different OS/Different Version of Access/Different Computer
I'm not seeing any errors when publishing, all my references are there, there's no reason for this to be failing as far as I can tell. The only indication that this happened is opening the ACCDE version and getting an error about auto_exec being unable to locate my function.
Ideally I'd like to not have to restore a version and lose changes that I've made.
My VBA Project seems to be corrupted. When I try to open a module I get a "Module name 'xxxx' is misspelled or relates to a module that doesn't exist". This all seemed to happen after a run time error inferring a corruption had taken place. I have tried to open Access in decompile mode and then open the data base, but still no luck...though I'm not sure how you tell its in decompile mode. I'd desperately like to get some code out that I've been working on for a couple of days.... I can open the tables and queries, so it seems its just the VBA project.
Any ideas? is there a way of accessing the modules outside of the data base?
I work with Access daily, and this situation is unlike anything I've ever seen Access do:
I created a database tool in Access for a report I run at work. The other day I was using it, and Access abruptly closed itself down. I went to reopen the tool, and I got an error saying "Microsoft Access has stopped working. A problem has caused the program to stop working correctly. Windows will close the program and notify you when a solution is available."
A few minutes later it prompts me to create a backup, which also does the same thing when I try to open it...
...unless...
I open Access itself and search for the original tool. Then it opens just fine.
I have tried repairing this database, and nothing works. It simply won't let me open this tool unless I go through Access first.
Does anyone have any ideas on this? What gives???
(Windows 7 Enterprise Edition, MS Access 2007)
A few things I would try
1) Create an entirely new DB, and import all of the objects from the problematic database. Any corrupt objects will show as an error during that process. You may get lucky and the new DB can simply be the new production DB.
2) Hold down the Shift key as Access is loading to bypass any startup code.
The problem is likely in the VBA link, which the new DB shell will fix.
I created an Access front end for a SQL DB on my PC for use throughout my company. I am using a file ODBC connection and putting both the ODBC file and the Access file on a shared network drive.
When I load the access file, for some reason it seems to default to using my windows login credentials and pulls in the data perfectly. When a user attempts to open the file, they receive an error message saying "ODBC --call failed.". I can open the Linked Table Manager for them and check 'ask for new location' then specify the ODBC file and it all works fine...however it doesn't seem to save anything. I get the error each time someone other then myself opens this file.
Any idea what could be wrong? I am not an Access guy by trade, it just seems to be the tool we need for the moment.
--EDIT: For Clarification I am using a file ODBC connection
--Edit 2--
Riddle me this. So I have been troubleshooting this issue and I came across something interesting. I was logged in as one of my users and did the following:
Create a new access file that references a file ODBC connection on the desktop.
Create 3-4 linked tables in the access file, using the ODBC file on the desktop.
Save and close the access file.
Re-Open said file.... and I get an ODBC connection error! Right after everything was fine in a fresh file!
Anyone ever experience this?
i assume you didn't install the ODBC correctly on each users PC.
you should create the ODBC-definition. You can create the relevant statements directly in the registry, see this branch
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
if you give the same name as on your developer machine, then it works. that's how i do it with my client applications that i develop on my machine and then install it at client site
After beating my head against the wall having this same issue, I finally discovered I had a checkbox on the Access form that defaulted to NULL. Since I put the backend into SQL, the checkbox fields cannot be NULL but the 'ODBC Call Failed' message did not help. I finally tried to add a record directly on the table via Access and it gave more information. I set all the checkboxes to default to zero and it resolved the problem!
Well, I was able to narrow the issue a bit. Access for some reason keeps trying to use Windows Credentials instead of the username in my ODBC file. I can't find a way around it, but I was able to resolve the issue by creating logins on my SQL Server for the windows users that need access.
I am not incredibly happy about needing to manage more logins, but that's what i did to resolve this issue.
I don't mean to resurrect the dead, but I had this same error stem from a different issue.
I was using an ODBC connection. When running the file using the 'Design' run button it worked fine. When I tried using the Navigation Pane and double clicking on it, the error would happen.
The structure of my query was the problem; I was porting a SQL server query over and the single quote ' parameter passing was not well received in Access. Changing these over to double quotes " made it work.