# Problem with scanner on new pc / ccg install

**URL:** <https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353>\
**Category:** General\
**Created:** [January 12, 2023, 8:57pm UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353 "2023-01-12T20:57:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rune](https://casparcgforum.org/letter_avatar_proxy/v4/letter/r/e68b1a/32.png) [@Rune](https://casparcgforum.org/u/Rune)\
**Post date:** [January 12, 2023, 8:57pm UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353/1 "2023-01-12T20:57:34Z")

</div>

Hi all,  
I feel pretty stupid about this, but…  
I’ve installed CCG server (casparcg-server-3e80053271ddd3bfe6bd751cee09e2ef1a74ae6a-windows) and scanner (casparcg-scanner-cedadbb4cfef4fa0cb17ec2320d0c0545aaed4a5-windows)

I have one file in media/, that plays out manually (play 1-1 in CCG console) but is not visible in either CCG client or SuperConductor.

Scanner seems to find the media file:

```auto
[2023-01-12T20:35:34.853Z] INFO (scanner/11400 on DESKTOP-ULSNMBI): request completed
    req: {
      "id": 3,
      "method": "GET",
      "url": "/db/_media/PAL_HD_1080P25_QT_ANIM_75_48KHZ?",
      "headers": {
        "accept": "application/json",
        "content-type": "application/json",
        "host": "localhost:8000",
        "connection": "close"
      },
      "remoteAddress": "::ffff:127.0.0.1",
      "remotePort": 50611
    }
    res: {
      "statusCode": 200,
      "header": "HTTP/1.1 200 OK\r\nX-Powered-By: Express\r\nContent-Type: application/json\r\nContent-Length: 190\r\nETag: W/\"be-ajBNJtPp8NZhgdLyB/c9kIg6OfI\"\r\nVary: Accept-Encoding\r\nDate: Thu, 12 Jan 2023 20:35:34 GMT\r\nConnection: close\r\n\r\n"
    }
    responseTime: 20
[2023-01-12T20:35:40.176Z] INFO (scanner/11400 on DESKTOP-ULSNMBI): request completed

```

stuff seems to be listening on port 8000 and 5250 according to netstat

Any idea what I am missing? I’ve never experienced this before.

---

<div class="post-metadata">

**Author:** ![Rune](https://casparcgforum.org/letter_avatar_proxy/v4/letter/r/e68b1a/32.png) [@Rune](https://casparcgforum.org/u/Rune)\
**Post date:** [January 13, 2023, 7:51am UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353/2 "2023-01-13T07:51:58Z")

</div>

I just installed 2.3.3 stable, and that is running as expected, so it seems to be related to the scanner version?

---

<div class="post-metadata">

**Author:** ![Ingo](https://casparcgforum.org/user_avatar/casparcgforum.org/ingo/32/1419_2.png) [@Ingo](https://casparcgforum.org/u/Ingo)\
**Post date:** [January 16, 2023, 8:22am UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353/3 "2023-01-16T08:22:31Z")

</div>

Hi Rune,

I’m not quite sure but it might be a problem to use a question mark in the file name.

Ingo

---

<div class="post-metadata">

**Author:** ![Rune](https://casparcgforum.org/letter_avatar_proxy/v4/letter/r/e68b1a/32.png) [@Rune](https://casparcgforum.org/u/Rune)\
**Post date:** [January 20, 2023, 1:00pm UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353/4 "2023-01-20T13:00:34Z")

</div>

Thanks, Ingo, but it’s a file from the default video pack and plays fine on 2.3.3 stable.  
I’m just going to go with 2.3.3 for the time being.

---

<div class="post-metadata">

**Author:** ![didikunz](https://casparcgforum.org/user_avatar/casparcgforum.org/didikunz/32/7_2.png) [@didikunz](https://casparcgforum.org/u/didikunz)\
**Post date:** [January 20, 2023, 7:56pm UTC](https://casparcgforum.org/t/problem-with-scanner-on-new-pc-ccg-install/5353/5 "2023-01-20T19:56:53Z")

</div>

> [@Ingo](#):
>
> I’m not quite sure but it might be a problem to use a question mark in the file name.

AFAIK the question mark is NOT a legal character in filenames. Sometimes it might work, but sometimes not. I would change the name anyway. That there is a question mark in the filename can have something to do with a wrong text encoding while moving files between different operating systems. I don’t think somebody did that intentionally.