AX POS Error: Step 4: Creating Device Token failed
The error is because the CPOS wasn't able to hit the AX '7' database. The CPOS uses a single AxDB database, in my case in the 'all in one' server, which the CPOS needs to have access to.
The environment was the AX 7 Update 1 using upgraded data from the AX 7 RTW release.
The Update 1 data changed in regards to some setup information. Event Viewer gave me some information into this essentially saying that the axruntimeuser wasn't able to access the DB. This, among other things, led me to believe the channel database setup was wrong.
To reconfigure the channel database 'connection string', you'll need the connection string (duh). I used Visual Studios Server explorer to create a connection to the database with the AxDB database for the CPOS, then clicked 'Properties'. The connection string will be right there. (Figure 1)
Paste this value into the appropriate connection string (Figure 2). Mine was the 'Default' one. Run the 1070 job (I think that's the channel job... if not, run that one).
You'll need to cycle the Retail Server application pool also (Figure 3 below).
There were a few other random settings I had to change from RTW configs to update 1 but the above was the main one. I think there were only 3-4 other places.
Hopefully this helps someone else jump past this issue!
与本文相关的文章
- 更新后 Dynamics 365 财务和运营字段丢失 / Dynamics 365 Finance and Operations field missing after update
- D365商业对 Adyen支付和服务连接器的考虑进行修改 / D365 Commerce making changes to Adyen payment and service connector considerations
- Solved: D365 Fields automatically populating on form errantly – Due to a Chrome addin/已解决:D365 字段自动错误地填充到表单上——由 Chrome 插件引发
- D365全屏模式,适用于现代POS(MPOS)/ D365 Full screen mode for Modern POS (MPOS)
- Dynamics 365 / AX 2012 现代/企业版POS’速度扫描’功能 / Dynamics 365/AX 2012 Modern/Enterprise POS ‘Speed Scanning’ feature
- Microsoft 365、Dynamics 365、Office 365 品牌和术语 / Microsoft 365 vs Dynamics 365 vs Office 365 terminology and branding (hopefully) explained