Strange error while restoring a group

I wanted to try to use the save group feature. I get a strange error like this :

"Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item".

 

The program is called Tweeten. At my knowledge it's a desktop bridge app that you can install from the Windows Store. I wanted to group this software with the Facebook store app. I can both group Facebook and Tweeten manually and I do net get any error when saving the group.

 

I get this error when I try to restore the group. It point to Tweeten app. When I click the ok button, Facebook app come up. 

 

Maybe the Groupy save group cannot work on some type of store app?

 

Martin

17,603 views 11 replies
Reply #1 Top

Hello,

Sorry for a late reply. I was trying to test out Tweeten. But seem my twitter account have some problem hence I can't test it. Anyway I've hilite you problem to our CM support group for help.

Reply #2 Top

Okay. I get my tweeten working.

From what I understand you try to group tweeten with Facebook store app which open in a browser?. In my case I opened facebook in my Firefox. 

Okay I see the problem. In my case if I have firefox running. and I open that saved tweeten facebook group. It will only open tweeten but no firefox. but if you open when firefox not running. It will opened up tweeten with firefox but that firefox will only open up to the last closed windows state.

So basically the saved group worked. Just that the web site open is not saved.

Will hilite that problem to our CM support Team for help.

Note: Tested with Opera + Tweeten combo. Same result.

+1 Loading…
Reply #3 Top

I used Facebook from the Windows Store. Not the web one. But cool to see ya got the same results on you side :)

Reply #4 Top

Both are MS Store apps?

Reply #5 Top

its grouped okay on my system provided that both apps from microsoft app store. if Web version it will not work.

Reply #6 Top

Tweeten win app, in my case grouped with  Nextgen reader win app, works ok here. Can be grouped with no problem and when I recall the group, it opens ok.

Reply #7 Top

Could you post what has been saved to the groupy file please.

It is saved here : C:\Users\<YOURUSERNAME>\AppData\Roaming\Groupy

Reply #8 Top

Quoting Neil, reply 7

Could you post what has been saved to the groupy file please.

It is saved here : C:\Users\<YOURUSERNAME>\AppData\Roaming\Groupy

 

Yes they are both Windows Store applications

[GroupyEntry1]
OwnerProcess=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
RunElevated=0
NoPatternMatching=0
CommandLine=
WorkingDirectory=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app
Target=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
MatchingClass=Chrome_WidgetWin_1
[GroupyEntry2]
OwnerProcess=Facebook.Facebook_8xx8rvfyw5nnt!App
RunElevated=0
NoPatternMatching=1
Target=Facebook.Facebook_8xx8rvfyw5nnt!App
MatchingClass=ApplicationFrameWindow
[Group]
GroupCount=2
GroupLeft=801
GroupTop=303
GroupRight=3237
GroupBottom=1968
GroupMax=0

Hope this helps

Reply #9 Top

Hello,

I have very similar list as yours. The only thing I can see different is that my facebook listed first and Tweeten second. And on mine both open without a problem. Maybe you can try that try to open facebook first than add tweeten onto facebook to create the group and save.

Here my list for your reference.

[GroupyEntry1]
OwnerProcess=Facebook.Facebook_8xx8rvfyw5nnt!App
RunElevated=0
NoPatternMatching=1
Target=Facebook.Facebook_8xx8rvfyw5nnt!App
MatchingClass=ApplicationFrameWindow
[GroupyEntry2]
OwnerProcess=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
RunElevated=0
NoPatternMatching=0
CommandLine=
WorkingDirectory=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app
Target=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
MatchingClass=Chrome_WidgetWin_1
[Group]
GroupCount=2
GroupLeft=392
GroupTop=138
GroupRight=1432
GroupBottom=876
GroupMax=0

Reply #10 Top

Quoting basj, reply 9

Hello,

I have very similar list as yours. The only thing I can see different is that my facebook listed first and Tweeten second. And on mine both open without a problem. Maybe you can try that try to open facebook first than add tweeten onto facebook to create the group and save.

Here my list for your reference.

[GroupyEntry1]
OwnerProcess=Facebook.Facebook_8xx8rvfyw5nnt!App
RunElevated=0
NoPatternMatching=1
Target=Facebook.Facebook_8xx8rvfyw5nnt!App
MatchingClass=ApplicationFrameWindow
[GroupyEntry2]
OwnerProcess=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
RunElevated=0
NoPatternMatching=0
CommandLine=
WorkingDirectory=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app
Target=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
MatchingClass=Chrome_WidgetWin_1
[Group]
GroupCount=2
GroupLeft=392
GroupTop=138
GroupRight=1432
GroupBottom=876
GroupMax=0

Have the same config as yours, same error. That's weird. Must be something inside my system. Here is my file :

[GroupyEntry1]
OwnerProcess=Facebook.Facebook_8xx8rvfyw5nnt!App
RunElevated=0
NoPatternMatching=1
Target=Facebook.Facebook_8xx8rvfyw5nnt!App
MatchingClass=ApplicationFrameWindow
[GroupyEntry2]
OwnerProcess=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
RunElevated=0
NoPatternMatching=0
CommandLine=
WorkingDirectory=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app
Target=C:\Program Files\WindowsApps\7632Mehedi.335522E7F7308_4.3.3.0_x64__vswa6tq66xa2g\app\Tweeten.exe
MatchingClass=Chrome_WidgetWin_1
[Group]
GroupCount=2
GroupLeft=444
GroupTop=330
GroupRight=2880
GroupBottom=2007
GroupMax=0

 

Reply #11 Top

I have been able to reproduce the problem with Tweeten not launching correctly and showing an error message instead and am investigating it further.

UPDATE : This is now fixed for an upcoming release.  Thanks for reporting this issue.