The only time the Product Owner would be named in a user story is if you are building a product that is designed for Product Owners.
I need to write some requirements affecting directly to the product but not exactly to any user, but necessary to achieve the product.
Will users of the product really see no value at all from the requirement? If that is true, why are you wasting time on it?
Even non-functional requirements can be written in the sense of a user:
As a user of the product I want it to be responsive even under heavy load so that I get a good experience
As a user of the product I want to be sure that in the event of a hardware failure I do not lose any of my data so that I do not have to waste time re-entering it
As a marketing executive I want to see statistics on the use of the product so that I can quickly make decisions about marketing campaigns
Try and avoid making technical tasks in to user stories. For example:
As a Product Owner I want a database to be created so that we can build the product
Instead, wrap these requirements into a real user requirement as sub-tasks.
As a user I want to be able to login to the product so that I can access its features
This is the first story the team is doing and to achieve it they might have sub-tasks that include: create database schema, build database, setup database server, setup application server, create authentication framework etc.