Тинькофф банк код ошибки 1201

ну у вас же написано:

обратитесь в тинькофф, назовите им код ошибки и опишите ситуацию

https://github.com/1C-Company/DirectBank/blob/master/doc/common-section/tables.md#errors

1202    Недостаточно прав у пользователя    У пользователя нет прав использовать прямой обмен с сервисом

но пока я не смогу убедиться что ошибка на стороне 1С то и не с чего бежать в техподдержку 1С, больше похоже что банк..

(8) +100500

зы думаю в Тинькофф уже в теме и знают, что сделать — обратитесь в поддержку

(8) Была мысль такая, но что ему давать, в ЖР то ошибок нет, ответ при получении настроек из банка.

(9) В чате девушка отправляет в ТП 1С, т.к. ошибка в окошке 1С)

Эта ошибка на гитхабе у них(1С) описана в разделе ошибка аутентификации и авторизации, т.е. как бы намек на проблему на той стороне.

Раздел 12. Ошибки аутентификации и авторизации         

1201     Некорректные данные для аутентификации     Неверные имя пользователя/пароль или неправильный сертификат ключа электронной подписи

1202     Недостаточно прав у пользователя     У пользователя нет прав использовать прямой обмен с сервисом

1203     Доступ к сервису временно заблокирован     Доступ к сервису для данного пользователя заблокирован до <ХХ> ч по причине <Причина блокировки>

1204     Некорректный ОТР     Введен неверный одноразовый пароль для указанной сессии

1205     Услуга не доступна     Услуга не подключена на стороне банка. Обратитесь в обслуживающее подразделение Банка

Под пользователем, с которого логинитесь, какие доступы, если смотреть через Тинькофф?

StanLee

14 — 02.06.22 — 21:46

We have created a Windows Store app and are running into error code(s) 2003 and 1201 while trying to submit the app to the store. Apparently these errors are not documented in the documentation and there is pretty much absolutely nothing that we can find about these online. Hoping somebody have a knowledge about their resolution and is willing to share it here.

All replies

• I get same error. Did you update the UWP .NET CORE Platform to 5.3?? It might be the problem.

• Hi Sven,

  Can you describe your question with more details, like you develop UWP app or Windows 8.1? The error occurs in which step of publishing?

  How did you package your app? Only if we manage to reproduce the error, can we assist you better.

  Also you can contact Dev Center support through your developer account so that they may observe your app in back end.

  Please click «Submit an incident» on the right side of that page. Thank you.

  Best regards,

  Mattew Wu

  ---

  MSDN Community Support
  Please remember to click «Mark as Answer» the responses that resolved your issue, and to click «Unmark as Answer» if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to
  MSDN Support, feel free to contact MSDNFSF@microsoft.com.

• Hi Mattew,

  Here’s a bit more info.

  The error occurs after I submitted my App to the store. It almost immediately fails with the 1201 error. The problem has to do with the UWP package, because in the first submission I had only included a WP8.1 package and that submission was accepted in the
  store.

  This morning I tried again (as suggested above) with updating the .NET core nuget package, because i was still using 5.0.

  * update to version 5.3.0 was not possible because this is not supported in Visual Studio 2015

  * update to version 5.2.2 gave an error already when trying to upload the package:

  Package acceptance validation error: You cannot submit pre-compiled .NET Native packages. Please upload the Store appxupload file and try again. http://go.microsoft.com/fwlink/?LinkId=797528

  * update to version 5.1.0 resulted in the same 1201 error upon submitting the package to the store.

  I package my app via visual Studio 2015 Update 3, I ran the certification Kit 10.0.14393.33 each time with success.

  Best regards,

  Sven

• I am as well experiencing the same annoying problem.

  Last submission that worked:

  — was with «Microsoft.NETCore.UniversalWindowsPlatform» 5.2.2

  — was compiled with VS 2015

  — uploaded and accepted by the store on this Monday (Jan 30th, 7pm UTC)

  Today, (Feb 1st, 1am UTC) I uploaded a new version that was rejected just as Sven described. It was

  — built with «Microsoft.NETCore.UniversalWindowsPlatform» 5.3.0

  — compiled with VS 2017 (RC.3+26127.0)

  Let me quote the v5.3.0
  update news: «You can publish apps to the Windows Store with .NET Native 1.6 RC, starting today.»

  • Edited by

    Wednesday, February 1, 2017 12:19 PM

• Thanks to everyone who reported this issue.

  Unfortunately, we have discovered an issue in our Store ingestion system and are actively working on addressing it. In the meanwhile, please downgrade to the previous version of the NuGet package you were using (likely 5.2.2?) and you should still be able
  to submit apps to the Store. We really apologize for the inconvenience, and have updated the blog post to reflect this. We will be posting another update when the issue is resolved on our blog here:

  https://blogs.msdn.microsoft.com/dotnet/2017/01/30/announcing-net-core-net-native-and-nuget-updates-in-vs-2017-rc/

  Thanks,
  Unni
  Program Manager, Visual Studio team

  ---

  Unni Ravindranathan, Program Manager, Visual Studio and Blend This posting is provided «AS IS» with no warranties, and confers no rights.

• Just to provide an update here —

  We have resolved this issue with submissions to the Windows Store failing. You can now use the 5.3.0 version of the Microsoft.NETCore.UniversalWindowsPlatform package, and successfully build and submit apps to the Windows Store. Also, to confirm — you will
  need to use the latest Release Candidate builds of Visual Studio 2017 to use the 5.3.0 version of the package, and cannot use Visual Studio 2015. If you are using Visual Studio 2015, please continue to use the 5.2.2 version of the package.

  Please feel free to reach directly to me at unnir at Microsoft dot com, if you are still noticing issues. Our sincere apologies for this issue, and many thanks to everyone who reported it.

  Thanks,
  Unni

  ---

  Unni Ravindranathan, Program Manager, Visual Studio and Blend This posting is provided «AS IS» with no warranties, and confers no rights.

  • Edited by
    Unni Ravindranathan — MSFT
    Wednesday, February 8, 2017 6:21 PM
  • Proposed as answer by
    Mattew WuModerator
    Thursday, February 9, 2017 5:31 AM

• Dear Unni,

  I’m still having this problem, I already reinstall all my development environment with no success.
  Like Sven said, I’ve never had this problem before and I didn’t change nothing.
  My Microsoft.NETCore.UniversalWindowsPlatform is 5.0.0 and I have the same result in all versions of this reference. I can’t figure out what is happening and I really need this working.

  My current (preferred) environment:

  • VS Professional 2015 Update 1
  • VS Tools for UWA 14.0.24720.00
  • NuGet 3.3.0
  • Windows 10 SDK 10.0.26624
  • Windows 10 SDK 10.0.10586.15

  Please, help me.

• I have the same issue here. Configuration: VS2015 update 3 and the recommend version Microsoft.NETCore.UniversalWindowsPlatform: 5.2.2

• Hi Everyone,

  I saw Unni’s (microsoft employee) email address in a post on this thread so I emailed yesterday afternoon to report the newest problem we are all seeing.  They let me know this morning that we should retry submitting the apps since the issue has now
  been resolved.  I submitted mine again earlier and it’s still pre-processing, so I think that’s a good sign because it would fail pretty fast when the problem was happening.  

  • Proposed as answer by
    Sinime
    Friday, March 31, 2017 5:55 PM

• I’ve been having the same issue using VS2017 (version 15.0.0+26228.10) with UWP app using .NET Core v5.3.1 (also happens with v5.2.2).

  I emailed Unni and he said that they are still working on the problem. I tried re-submitting the app again just now, and it still fails with error code 1201. So I don’t think this is resolved yet.

  • Edited by
    Napster devs
    Friday, March 31, 2017 6:46 PM

• I have the same problem and error with visual studio 2015. Please, can I resolve it?

• Same for me. I ported my Windows 8x app to UWP in VS 2017 and then submitted it last night and got the 1201 error. I just tried resubmitting again and it quickly came back with the 1201 error.

• just submitted a UWP App made with VS2017 and Microsoft.NETCore.UniversalWindowsPlatform: 5.3.1
  but i continue to get the error 1201. Guys,
  that’s a shame. I can’t believe that all the submitting system is out of order for days.

  ---

  Moreno Borsalino

• I had the same issue, but it look like it has been resolved. I am in Certification process now.

• Few minute ago I submitted the same app but I continue to get the same error. Until now I don’t see any solution.

  ---

  Moreno Borsalino

• Few minute ago I submitted the same app but I continue to get the same error. Until now I don’t see any solution.

  ---

  Moreno Borsalino

  As of 1:30 PM EST (April 1st 2017) I am still getting this error. Tried with both 5.2.2 using VS2017 (15.0.0+26228.12) and the latest 5.3.1 .net Core. Originally thought it may be related to dev certificate that has expired and was updated but obviously
  this has nothing to do it with.

  • Edited by
    GorancoB
    Saturday, April 1, 2017 6:33 PM
    vs version used

• I’m had some 1201 error code.

  — built with «Microsoft.NETCore.UniversalWindowsPlatform» 5.3.1

  — compiled with VS 2017 (15.0.0+26228.10)

  wish quickly resolve this problem

• Hi Everyone,

  I saw Unni’s (microsoft employee) email address in a post on this thread so I emailed yesterday afternoon to report the newest problem we are all seeing.  They let me know this morning that we should retry submitting the apps since the issue has now
  been resolved.  I submitted mine again earlier and it’s still pre-processing, so I think that’s a good sign because it would fail pretty fast when the problem was happening.  

  Is there any new progress?

• Please see further respnses on this matter as of April 1st 2:30 PM EST with latest buld  .12 of VS 2017 and 5.3.1 of the UWP core it is still failing. 

• I got this error with VS2015 and .net core 5.2.3 and with VS2017 .net core 5.3.1
  Please can someone disable any check when submitting an App in the store so the submission process can continue to next steps ?

  ---

  Moreno Borsalino

• I have some good news for everyone:

  using :

  — built with «Microsoft.NETCore.UniversalWindowsPlatform» 5.3.0

  — compiled with VS 2017 (15.0.0+26228.10)

  Special attention was not 5.3.1

  This normal by pretreatment step

• I’m getting the same 1201 error.

  — built with Microsoft.NETCore.UniversalWindowsPlatforms 5.3.0 (also tried 5.3.1)

  — VS2017 (15.0.0+26228.12)

  ---

  none

• I’m getting the same 1201 error.

  — built with Microsoft.NETCore.UniversalWindowsPlatforms 5.3.0 (also tried 5.3.1)

  — VS2017 (15.0.0+26228.12)

  ---

  none

  Seems to working okay now. I’m using 26228.12 and 5.3.1

  ---

  none

• I’m using
  
  26228.12 and 5.3.1, but i’m still getting 1201 error.

• VS2015 + .NETCore 5.2.2 = it still fails with error code 1201.

• Thanks to everyone who reported this issue.

  Unfortunately, we have discovered an issue in our Store ingestion system and are actively working on addressing it. In the meanwhile, please downgrade to the previous version of the NuGet package you were using (likely 5.2.2?) and you should still be able
  to submit apps to the Store. We really apologize for the inconvenience, and have updated the blog post to reflect this. We will be posting another update when the issue is resolved on our blog here:

  https://blogs.msdn.microsoft.com/dotnet/2017/01/30/announcing-net-core-net-native-and-nuget-updates-in-vs-2017-rc/

  Thanks,
  Unni
  Program Manager, Visual Studio team

  ---

  Unni Ravindranathan, Program Manager, Visual Studio and Blend This posting is provided «AS IS» with no warranties, and confers no rights.

  MSFT — why don’t you TEST your shit before you release it?

  this means nothing less than: you cant publish apps build with VS2017 to the store.
  is this some kind of sick joke or am i dealing with non-professionals here?

  • Edited by
    wolfSYS
    Sunday, April 2, 2017 10:21 AM

• I’m having the same problem.

  Trying to upload a Windows 10 UWP app, built with Microsoft.NETCore.UniversalWindowsPlatform version 5.2.3 and Visual Studio 2015…

• Now I’trying to submit again with this configuration:

  VS2017
  26228.12 and 5.3.0

  Now the app is pre-certification step but respect before it take long time. Before I got error already after few seconds. I cross fingers
  and continue to wait. I will tell you more later.

  ---

  Moreno Borsalino

• Nearly two hours
  after the certification
  is
  ongoing.
  So far
  I haven’t
  gotten
  the error. It is another joke or finally the bug is fixed, at least for the my configuration. I continue to wait. More information later.

  ---

  Moreno Borsalino

• Pre-elaboration has been done without error. Now I am in step 2 : Certification.
  Maybe I defeated the monster

  ---

  Moreno Borsalino

• UWP, VS2015 and 5.2.3 still fails…

• yes, 5.3.0 is okay, i’m successed release new verison

• yes, 5.3.0 is okay, i’m successed release new verison

  You are lucky. I am waiting again. But 5.3.0 seams the only way to avoid the error

  ---

  Moreno Borsalino

• Nice to read that…. Same issue, i saw die .NETcore update but forgot… i did only visual studio and a SQLite UWP…

  First i tried msbuild cn CMD, issue!! from inside VS2017, the same…. 

  But it´s fucking cool to find the solution with the 1st BING result of «error 1201» nice…

  Thank you..  I´ll update the nuget now and publish my Flight :))

  ---

  Stephan Ertel — MCITP/MCSA —

• I am having the same problem, error 1201 on submission yesterday and today.

  I have tried the following two different versions, but both attempts have failed, see below.

  So using UWP v5.3.0 did NOT solve the problem for me.

  Microsoft.NETCore.UniversalWindowsPlatform v5.3.1
  Microsoft Visual Studio Community 2017  Version 15.0.26228.4 D15RTWSVC
  Microsoft .NET Framework   Version 4.6.01586
  NuGet Package Manager      4.0.0

  Microsoft.NETCore.UniversalWindowsPlatform v5.3.0
  Microsoft Visual Studio Community 2017  Version 15.0.26228.4 D15RTWSVC
  Microsoft .NET Framework   Version 4.6.01586
  NuGet Package Manager      4.0.0

• I am seeing the same issue submitting a UWP to the store.

• Same problem.

  5.3.0 (also tried 5.3.1) and latest VS 2017

  Find critical bug in latest release of my app and need to update it asap

  ---

  Eugene Akinshin

• Same Error here…waiting for a fix at Microsoft please

• The saga continues. After 2 days now I am in step 3: the application is going to be published. I continue to cross fingers…..and wait. My starting configuration was based on 5.3.0

  ---

  Moreno Borsalino

• I get the same problem here

• The issue is still there as of 5th of April 2017
  VS 2015 + 5.2.2

• Today i got the confirm the App is in the Store. With 5.3.0 I published with success. Now I wait the next update to check if I get the error again

  ---

  Moreno Borsalino

• The problem is from the Windows store and they have already solved it.

  You must tried to send the package you app again.

  Best regards!

• This issue is still alive apparently (31th of october 2017). Our context:

  — VS2015

  — NuGet package 5.1.0

  Can you please let know us what to do ?

  • Edited by
    LE CARDINAL Daniel
    Tuesday, October 31, 2017 9:40 AM

• We have the same issue. We are using

  VS 2017 Professional

  UWP Platform 6.2.0

  .NET Framework 4.7.03056

  It is almost a lost cause asking MSFT for help but still would like to scream … HELP if you can PLEASE.

  ---

  Khurram

• I have the same.. 

  UWP Platform: 6.1.5

  .Net Core 2.0

  Target and Minimum Platform: FCU

  @Khurram Isn’t  6.2.0 in preview as of now?

• When I migrated back to 6.0.8 it works again…

• I have the same issue. But I can’t build with version 6.0.8 (Error message: «Internal compiler error:
  Object reference not set to an instance of an object»). 

  My Visual Studio Version is: 15.7.5 (VS 2017)

  Has anyone an idea?

  • Edited by
    MaxOnTour
    Monday, July 30, 2018 9:13 AM

ну у вас же написано:

обратитесь в тинькофф, назовите им код ошибки и опишите ситуацию

https://github.com/1C-Company/DirectBank/blob/master/doc/common-section/tables.md#errors

1202    Недостаточно прав у пользователя    У пользователя нет прав использовать прямой обмен с сервисом

но пока я не смогу убедиться что ошибка на стороне 1С то и не с чего бежать в техподдержку 1С, больше похоже что банк..

(8) +100500

зы думаю в Тинькофф уже в теме и знают, что сделать — обратитесь в поддержку

(8) Была мысль такая, но что ему давать, в ЖР то ошибок нет, ответ при получении настроек из банка.

(9) В чате девушка отправляет в ТП 1С, т.к. ошибка в окошке 1С)

Эта ошибка на гитхабе у них(1С) описана в разделе ошибка аутентификации и авторизации, т.е. как бы намек на проблему на той стороне.

Раздел 12. Ошибки аутентификации и авторизации         

1201     Некорректные данные для аутентификации     Неверные имя пользователя/пароль или неправильный сертификат ключа электронной подписи

1202     Недостаточно прав у пользователя     У пользователя нет прав использовать прямой обмен с сервисом

1203     Доступ к сервису временно заблокирован     Доступ к сервису для данного пользователя заблокирован до <ХХ> ч по причине <Причина блокировки>

1204     Некорректный ОТР     Введен неверный одноразовый пароль для указанной сессии

1205     Услуга не доступна     Услуга не подключена на стороне банка. Обратитесь в обслуживающее подразделение Банка

Под пользователем, с которого логинитесь, какие доступы, если смотреть через Тинькофф?

StanLee

14 — 02.06.22 — 21:46