# SDKERR\_WRONG\_USAGE when trying to request recording permission

**URL:** <https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312>\
**Category:** Windows\
**Created:** [July 9, 2024, 2:30pm UTC](https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312 "2024-07-09T14:30:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bharat.bhadresha](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bharat.bhadresha/32/45714_2.png) [@bharat.bhadresha](https://devforum.zoom.us/u/bharat.bhadresha)\
**Post date:** [July 9, 2024, 2:30pm UTC](https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312/1 "2024-07-09T14:30:28Z")

</div>

**Description**  
SDKERR\_WRONG\_USAGE when calling `RequestLocalRecordingPrivilege` from `MEETING_STATUS_INMEETING` state.

**Which Windows Meeting SDK version?**  
6.1.1

**To Reproduce(If applicable)**  
Code snippet

```cpp
void MeetingEvent::onMeetingStatusChanged(MeetingStatus status, int iResult = 0) {

	switch (status)
	{
	case MEETING_STATUS_INMEETING:
	{
		cout << "In Meeting" << endl;
		if (SDKInterface::getInstance()->canIStartLocalRecording() == true) {
			cout << "Can start local recording" << endl;
		}
		else {
			cout << "Cannot start local recording" << endl;
		}
		IMeetingRecordingController* recordingController = SDKInterface::getInstance()->getRecordingController();
		recordingController->SetEvent(new RecordingEvent());
		SDKError res = recordingController->RequestLocalRecordingPrivilege();
		cout << "RequestLocalRecordingPrivilege: " << res << endl;

```

**Console output**

![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/f/b/fb505d59c3bd32e13550ad6b5ae1287014221cf8.png)

**Device (please complete the following information):**

- Device: Dell G15
- OS: Windows 10

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [July 10, 2024, 7:10am UTC](https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312/2 "2024-07-10T07:10:05Z")

</div>

@bharat.bhadresha

I’ve just written a sample for this, and updated it to 6.1.1.

It works when i try to prompt the host for local recording.

Do note that if local recording is disabled at meeting, user or account level, this prompt for permission to do local recording won’t work

> **[Zoom\_MeetingSDK\_Windows\_RawDataDemos/LocalRecording at master ·...](https://github.com/tanchunsiong/Zoom_MeetingSDK_Windows_RawDataDemos/tree/master/LocalRecording)**
>
> Consolidation of 1 Solution with multiple raw data projects - tanchunsiong/Zoom\_MeetingSDK\_Windows\_RawDataDemos

---

<div class="post-metadata">

**Author:** ![bharat.bhadresha](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bharat.bhadresha/32/45714_2.png) [@bharat.bhadresha](https://devforum.zoom.us/u/bharat.bhadresha)\
**Post date:** [July 11, 2024, 8:39am UTC](https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312/3 "2024-07-11T08:39:20Z")

</div>

The local recording permission was the issue. Its working now.

I would like to raise a request to implement proper error messages.  
SDKERR\_WRONG\_USAGE doesn’t explain anything, In web sdk its properly written that the local record permission is not present.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [August 10, 2024, 6:39pm UTC](https://devforum.zoom.us/t/sdkerr-wrong-usage-when-trying-to-request-recording-permission/113312/4 "2024-08-10T18:39:22Z")

</div>

Closed on August 10, 2024, 6:39pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.