Maintain control of your Microsoft Office 365 email data
Post Reply
shm
Service Provider
Posts: 7
Liked: never
Joined: Dec 11, 2018 3:20 pm
Full Name: Stan
Location: Enschede
Contact:

Can not start restore session with API v2

Post by shm » Jan 14, 2019 12:31 pm

request to start restore session is denied.

Curl

Code: Select all

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer AQAAANCMnd8BFdERjHoAwE_Cl-sBAAAADal8W7X7s0m-lBEc2a67ZQAAAAACAAAAAAAQZgAAAAEAACAAAABUHeLg31wOn39CA9tpeO3bUdfOAGn3OcMkaaC5ybiT6gAAAAAOgAAAAAIAACAAAABcD20F5Gs1lNRwckXKMUdSZ1veMpb73VvxgMY_iheshbAAAAAThiyVi2ggCvNSFVPkcxCCSMq5gcIhaMUWD6TACgWwkz7Hra1NWcugrZG0JrqcdauJcl4ny6sZFv7q8-nqG-p5zT4KP1CoUeL_tSmWsiSQT0dy0JkrgDbYFARrQm0UARkIJZNL1v9HtrvmrQUidsKhjreo5wof9G84s1eMwVajSizjmUpObYRkUjeT_x4TrvSSS2-thuNJaf4Dqm4NG_59ZKUDIi78VoDBoiaNOmkX8UAAAAAecvT2WjpSv8qlcFrloRNA19Y2osPgkt_p9DRM7rBX2F8aBV7lBYywO0UQS9qE4IepUyFFktZ0PL-VIh_s74t1' -d '{"explore": {"datetime": "2019.01.12", "type": "vex"}}' 'https://192.168.1.132:4443/v2/Organizations/fb9d8dd6-d52f-4864-bff5-66a93d101878/action'
Request URL

Code: Select all

https://192.168.1.132:4443/v2/Organizations/fb9d8dd6-d52f-4864-bff5-66a93d101878/action
Response Body

Code: Select all

{
  "message": "Restore session cannot be created."
}
Response Code: 500
Response Headers

Code: Select all

{
  "x-firefox-spdy": "h2",
  "content-length": "55",
  "content-type": "application/json; charset=utf-8",
  "date": "Mon, 14 Jan 2019 12:27:35 GMT",
  "server": "Microsoft-HTTPAPI/2.0"
}

shm
Service Provider
Posts: 7
Liked: never
Joined: Dec 11, 2018 3:20 pm
Full Name: Stan
Location: Enschede
Contact:

Re: Can not start restore session with API v2

Post by shm » Jan 14, 2019 1:18 pm

Error log:

Code: Select all

14-1-2019 14:12:38   74 (3716)   Action: explore
14-1-2019 14:12:38   74 (3716) Action started (action: explore, data: organizations)
14-1-2019 14:12:38   74 (3716) Action failed (action: explore, data: organizations, error: Restore session cannot be created.)
14-1-2019 14:12:38   74 (3716) Error: Restore session cannot be created.
14-1-2019 14:12:38   74 (3716) Type: System.Exception
14-1-2019 14:12:38   74 (3716) Stack:
14-1-2019 14:12:38   74 (3716)    at Veeam.Core.Verifiers.Assert(Boolean b, String message, Object[] args)
   at Veeam.Archiver.REST.Clients.RestoreSessionClient.Create(Guid organizationId, DateTime pointInTime, RestoreSessionType type)
   at Veeam.Archiver.REST.RESTClients.RESTRestoreSessionClient.CreateInternal(DateTime pointInTime, Guid organizationId, IUriSource uriSource, RestoreSessionType type)
   at Veeam.Archiver.REST.RESTClients.RESTRestoreSessionClient.Create(RESTExploreOptions exploreOptions, Guid organizationId, IUriSource uriSource)
   at Veeam.Archiver.REST.Actions.OrganizationActions.Explore(JToken jsonOptions, OrganizationActionParameters parameters, IResponseBuilder responseBuilder, HttpConfiguration httpConfig)
   at Veeam.REST.Actions.ActionByNameExecutor`1.<>c__DisplayClass4_0.<Execute>b__0()
   at Veeam.REST.Actions.ActionExecutor.ExecuteActionImpl(Func`1 restAction, String actionName, IResponseBuilder responseBuilder, String dataName, Func`1 checkData)
   at Veeam.REST.Actions.ActionExecutor.Execute(Func`1 restAction, String actionName, HttpConfiguration httpConfig, IResponseBuilder responseBuilder, String dataName, Func`1 checkData)

vmniels
Veeam Software
Posts: 2125
Liked: 470 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Can not start restore session with API v2

Post by vmniels » Jan 14, 2019 1:22 pm 1 person likes this post

Did you install the Veeam Explorers correctly (as in run both MSI files)? Can you manually start a restore from the GUI via the Veeam Explorers (in your case Exchange one)?
VCP-DCV
Veeam Certified Architect (VMCA)
http://foonet.be

shm
Service Provider
Posts: 7
Liked: never
Joined: Dec 11, 2018 3:20 pm
Full Name: Stan
Location: Enschede
Contact:

Re: Can not start restore session with API v2

Post by shm » Jan 14, 2019 1:45 pm

I have checked on the server. It did not have the exchange explorer installed.
I was using the Explorer installed on a different server.

After installation of explorer and reboot of VBO365 server, the call results in 200.
Thank you this has solved my problem.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests