Gorgo.Live.ToString()

Mariusz, Gorzoch tech Blog

Resources found for language(s) ‘en-us’ but no resources found for default language

leave a comment »

If you encounter above problem then :

assuming your default language is “no”

By default language I understand that “Package.appxmanifest” says that your application “Default language” is “no” as also when you edit definition of your project “.csproj” file then it contain “no” inside “DefaultLangage” node (=for all projects in your solution). Please notice especially content of “.csproj” file <- it is set during creation of the project and you have no way of changing that from visual studio

in order to get rid of that problem you need to:

1. if you have “strings” folder (default location of all text resources) then inside you have to have subfolder “no”

2. if you have “images folder (default location of all images) then inside you have to have subfolder “no”

if you don’t have one of above then you will get warning as above.

Advertisements

Written by Mariusz Gorzoch

9 June 2014 at 15:22

Posted in Windows8.1, XAML

530 User cannot log in, home directory inaccessible

leave a comment »

I’ve was setting up today standard FTP (the one with comes with the installation) server on Windows 2012 R2 and after setting up the users and ensuring that we keep them isolated :

image

we started to get error message as stated in the title of this post.

Home directory of my FTP was = “c:\ftp”

Name of the user “MyUser”

Based on the documentation above setting should try to establish home directory for the user under : “c\ftp\MyUser”. Unfortunately apparently there was something wrong here.

I’ve dig for a while and finally started “ProcessMonitor”. What he show’s me that actually FTP service is looking for home directory under location “c:\ftp\LocalUser\MyUser”. After moving my user folder under “LocalUser” I was able to login without any problems.

Written by Mariusz Gorzoch

27 March 2014 at 15:28

Posted in Bez kategorii

HRESULT E_FAIL has been returned from a call to a COM component–continued

with one comment

It did happened again. Today I got again error “Error HRESULT E_FAIL has been returned from a call to a COM component”. This time I’ve decided to use FileMon (http://technet.microsoft.com/en-us/sysinternals/bb896645) and see if he is not pointing to something with my app doesn’t have access to. What pop-up from that tool is that the app was trying to access that folder :

C:\ProgramData\Microsoft Team Foundation\4.0\Cache

and it end-up with “Access denied”.

I’ve added account used to run app pool to above folder with full permission. Restarted app pool/app and when it went up my error disappeared.

So it, looks that this was permission problem.

Written by Mariusz Gorzoch

21 March 2014 at 10:36

Posted in Bez kategorii

HRESULT E_FAIL has been returned from a call to a COM component

leave a comment »

I have a site hosting application with retrieve some data from TFS 2012 thru TFS API. It was working fine till someone restart. From that point I’ve started to get bellow error:

Error HRESULT E_FAIL has been returned from a call to a COM component.
  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:

[COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.]
   Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.DataStoreNative.UpdateMetadata(IntPtr handle, Object rowset, String dbstamp, UInt32& changes) +0
   Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.Datastore.UpdateMetadata(Object rowset, String dbstamp) +57
   Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.EndBackendCall(BackendCallData data) +275
   Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.RefreshCacheInternal(BackendCallData& data) +204
   Microsoft.TeamFoundation.WorkItemTracking.Client.WorkI
temStore.InitializeInternal() +565

I’m still looking for the solution, but what seems to work is:

– add user hosting web site to local admin on the machine

– add user hosting web site to project admins from with you retrieve data

– open team web access (TWA) on user hosting web site on your local machine

– open team web access (TWA) on user hosting web site on the server hosting the solution

This makes web site to work again. Some of above steps are for sure not necessary, but I need above problem to occur again to eliminate some of them. I’ll keep updating that post till I find what exactly is needed to fix above.

Once the web site is back again, then you can undo all above steps and the site will keep working even if you restart IIS.

Written by Mariusz Gorzoch

20 March 2014 at 13:04

Posted in TFS2012

Tagged with

Error HRESULT E_FAIL has been returned from a call to a COM component

leave a comment »

Recently I’ve develop MVC app to expose our TFS to our external customers thru really simplify interface (=Team web access is great, but let’s honest for no IT user it is to far complicated). After testing period on my box and ensuring that all security setup is ok (=we don’t want to show to our customers projects with do not concern them) I’ve deployed that app to one of our DMZ servers. Initially I’ve used one of standard TFS account to host it (the account used to host TFS web services). At that point everything was working fine, but of course that was temporary solution as on the end I preferred to use dedicated account. Unfortunately as soon I get such a account and grant proper access I’ve started to get error as below:

Error HRESULT E_FAIL has been returned from a call to a COM component.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
Exception Details: System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Resolution:

Just take your account and log with it on the server. That as I found is needed in order to create some temporary folder required by TFS API. Once I’ve did that and restarted IIS app pool hosting my app everything started to work correctly.

Written by Mariusz Gorzoch

3 March 2014 at 09:00

Posted in TFS

Tagged with

Method TryGetRowSet not found

with one comment

Today I come across below error when trying to use TFS API on the machine where SDK is not installed at all.

Method not found: ‘Boolean Microsoft.TeamFoundation.WorkItemTracking.Proxy.IWorkItemRowSets.TryGetRowSet(System.String, Microsoft.TeamFoundation.WorkItemTracking.Proxy.IRowSet ByRef)’.

System.MissingMethodException: Method not found: ‘Boolean Microsoft.TeamFoundation.WorkItemTracking.Proxy.IWorkItemRowSets.TryGetRowSet(System.String, Microsoft.TeamFoundation.WorkItemTracking.Proxy.IRowSet ByRef)’.

My solution was build on the dedicated build server and then deployed to destination server thru WebDeploy.

I’ve look around for the solution for a while and then come to the post:

http://blogs.msdn.com/b/bharry/archive/2013/02/13/10392771.aspx 

where someone pointed that Microsoft did a very bad think with update 2 for Visual Studio 2012. What it happened to be is that they adjusted version of the library “Microsoft.TeamFoundation.WorkItemTracking.Proxy.dll” to 11.0.60315.1, but they change it only in GAC and not in the official visual studio folder “C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0”.

So, it work in the way that :

“C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0” points that version of “Microsoft.TeamFoundation.WorkItemTracking.Proxy.dll” is “11.0.50727.1” where in reality our apps are looking into the GAC and using version “11.0.60315.1”.

In order to solve that problem you need to go to GAC folder  “C:\Windows\assembly\GAC_MSIL\Microsoft.TeamFoundation.WorkItemTracking.Proxy\11.0.0.0__b03f5f7f11d50a3a” (you can just use windows console) and copy our proxy library from there to your project and explicitly reference it.

Doing above solve problem in my case

Written by Mariusz Gorzoch

27 February 2014 at 10:20

Posted in Bez kategorii

A device attached to the system is not functioning

with 2 comments

or if you prefer the full message:

Error Message:

A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)

Stack Trace:
A device attached to the system is not functioning.
 

Our team get it when we were trying to certificate our Win8 app against Microsoft store. Before I get into detail’s let me give you some background:

Link to the app :   
http://apps.microsoft.com/windows/nb-no/app/ntf-befaring/aab4ce14-d341-4fd6-a1f2-4bc51670df7f   
   
Application was built with use of :  
Visual Studio 2012 Ultimate   
Windows 8.1  
   
We are targeting:  
Windows 8 , x64, x86, ARM devices  
   
Our app uses:  
Camera   
      
We did so far 7 releases of the app and recently we had to introduce one emergency change into the app. That extra change was connected with removing automatic deletion of the reports (those with you can see on the main screen of the app) in case of some special conditions. That change was really simple one and should not affect at all stability of the app. Unfortunately even the release 7 went without any problem than the current release (=release 7 + some really simple change) cannot go thru certification process at all. According to the reports with we were getting from Microsoft testers our app crashes almost on the first screen (and if not there, then on the second screen). The thing is : that we cannot reproduce that at all and by this I mean:  
   
1.      We have tried our app on our corporate laptops “Latitude E6420”  
a.       Windows 8 x64 version of our app  
b.      Windows 8 x86 version of our app  
c.       Windows 8.1 x64 version of our app  
d.      Windows 8.1 x86 version of our app  
2.      We have tried our app on ASUS Vivo Tab RT (ARM version of our app)  
3.      Lenovo ultra-book : http://www.x-kom.pl/p/171366-ultrabook-13-3-lenovo-ibm-yoga-13-i5-3337u-8gb-128ssd-win8-pomaranczowy.html   
4.      Samsung device : http://www.tabletmaniak.pl/77329/test-samsung-ativ-smart-pc-500t/   
5.      Our app is used by numbers of users in Norway (they are using release 7 of the app)  
6.      Our app was tested by our colleagues in Holte-Norway   
   
and no one on our site report to us such a problem.

We were blind and we run out of ideas…and then one team member suggested that maybe we should try to build our solution based on Windows 8 (=not windows 8.1). He was the only one in our team who didn’t upgrade his machine yet. We tried that, and guess what : on the next day our app went thru Microsoft tests without any problem.

So, if you have similar problem then ensure that if you are using Visual Studio 2012 to build your app for Windows store, then you use Windows 8 and not Windows 8.1. Most probably this is some kind of bug on the Microsoft site, and maybe at the time when you read that this will be not relevant at all…but for now, it is… and we wasted around 2weeks to sort it out.

Written by Mariusz Gorzoch

6 February 2014 at 08:24